Cisco Reader Comment Card
General Information
1
Years of networking experience
2
I have these network types:
Other:
LAN
Backbone
3
I have these Cisco products:
Other: Specify model(s)
Switches
Routers
4
I perform these types of tasks:
Network Management
H/W Install and/or Maintenance
Other:
S/W Config
5
I use these types of documentation:
Command Reference
Other:
H/W Install
Quick Reference
S/W Config
Online Help
6
I access this information through:
% Printed docs
7
Which method do you prefer?
8
I use the following three product features the most:
Years of experience with Cisco products
H/W Config
Release Notes
% Cisco Connection Online (CCO)
% Other:
WAN
% CD-ROM
Document Information
Document Title: Cisco MGX 8230 Installation and Configuration
Part Number: 78-10616-01
S/W Release: 1.0
On a scale of 1–5 (5 being the best) please let us know how we rate in the following areas:
The document was written at my
technical level of understanding.
The information was accurate.
The document was complete.
The information I wanted was easy to find.
The information was well organized.
The information I found was useful to my job.
Please comment on our lowest score(s):
Mailing Information
Company Name
Contact Name
Date
Job Title
Mailing Address
City
State/Province
ZIP/Postal Code
Country
Phone (
Extension
Fax (
)
)
E-mail
Can we contact you further concerning our documentation?
Yes
No
You can also send us your comments by e-mail to [email protected], or fax your comments to us at
(408) 527-8089.
FIRST-CLASS MAIL
PERMIT NO. 4631
SAN JOSE CA
BUSINESS REPLY MAIL
POSTAGE WILL BE PAID BY ADDRESSEE
ATTN DOCUMENT RESOURCE CONNECTION
CISCO SYSTEMS INC
170 WEST TASMAN DRIVE
SAN JOSE CA 95134-9883
NO POSTAGE
NECESSARY
IF MAILED
IN THE
UNITED STATES
Cisco MGX 8230
Installation and Configuration
Release 1.0
June 2000
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
Customer Order Number: DOC-7810616
Text Part Number: 78-10616-01
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.
Modifying the equipment without Cisco’s written authorization may result in the equipment no longer complying with FCC requirements for Class A or
Class B digital devices. In that event, your right to use the equipment may be limited by FCC regulations, and you may be required to correct any
interference to radio or television communications at your own expense.
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 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.
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 PARTICULAR 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.
Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC,
the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered
Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy
logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet
Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer,
NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ReyMaster,
ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN,
Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the
Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the
Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch,
FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar,
StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All
other trademarks mentioned in this document 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. (0005R)
Cisco MGX 8230 Installation and Configuration
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
C O N T E N T S
Preface
xv
Audience
xv
Organization
xvi
Conventions
xvi
Related Documentation
xvii
Accessing Electronic Documentation
Contacting Cisco
CHA PTER
1
xviii
MGX 8230 Overview
MGX 8230
xviii
1-1
1-1
Main Features
1-3
Standards-Based Conversion to ATM
MGX 8230 Physical Description
1-4
MGX 8230 Chassis/Enclosure
MGX 8230 Power System
Cooling System
1-6
1-7
1-8
MGX 8230 Architecture
Cell Bus
1-4
1-6
Optional AC Power Supply
DC-Powered MGX 8230
1-4
1-9
1-10
MGX 8230 Processor and Service Modules
1-12
MGX 8230 Processor Switch Module (PXM1)
Clocking Options
1-14
Management Interfaces
1-14
System Environment Monitoring
Alarm Circuit and Indicators
1-14
1-14
Physical Layer OC-3c/STM-1 Interface
ATM Layer
1-12
1-15
1-15
PXM1 User Interface Back Card
MGX 8230 OC-3 Uplink Back Card
OC-12 Uplink Back Card
1-17
SMFIR-1-622 Back Card
1-18
1-16
1-16
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
iii
Contents
MGX-FRSM-2T3E3 Front Card
BNC-2T3 Back Card
1-21
BNC-2E3 Back Card
1-22
1-19
ATM Universal Service Module
AUSM/B Front Card
1-22
1-23
AUSM/B Back Cards
1-25
Frame Service Module Features
FRSM Models
1-27
1-29
FRSM Redundancy
1-31
Circuit Emulation Service Module 8T1E1
Structured Data Transfer
1-31
Unstructured Data Transfer
CESM Models
1-31
1-31
1-32
Redundancy Architecture
1-34
MGX 8230 Management
1-35
Service Resource Module
1-35
General Installation Requirements for the MGX-SRM-3T3/B
Bulk Distribution and Redundancy Support
Statistics and Command Line Interface
Alarm and Error Handling
CHA PTER
2
Installation
1-35
1-35
1-38
1-38
2-1
Preparing for Installation
Safety
2-1
2-1
Maintaining Safety with Electricity
Warnings and Cautions
2-3
Translated Safety Warnings
2-3
Warning Definition
2-3
Product Disposal Warning
2-4
Lightning Activity Warning
2-5
Jewelry Removal Warning
2-6
Power Supply Warning
2-7
Power Supply Disconnection Warning
Power Disconnection Warning
2-9
Grounded Equipment Warning
2-10
Installation Warning
2-2
2-8
2-10
Cisco MGX 8230 Installation and Configuration
iv
Release 1.0, Part Number 78-10616-01, June 2000
Contents
Class 1 Laser Product Warning
Site Preparation
2-11
2-12
Parts Checklist
2-12
Card Slot Locations
Site Requirements
2-12
2-13
Seismic Considerations
Power and Grounding
2-14
2-14
AC Power Circuit Breakers
2-14
DC Power Circuit Breakers
2-14
Electrical Power for AC Units
2-14
Electrical Power for a DC-Powered MGX 8230
Bonding and Grounding
2-15
Telecommunications Requirements
Installing an MGX 8230
2-15
2-15
2-16
Installing Processor and Service Modules
Using the Electrostatic Wrist Strap
2-16
2-16
Removing and Installing the Front Cards
2-17
Removing and Installing the Back Cards
2-18
Rack Mounting the MGX 8230
2-19
Co-Locating Cisco Units in the Same Rack
Rack-Mount Positions
2-19
2-19
Rack Mounting Procedures
2-22
Connecting Power for DC Systems
2-23
Connecting Power for AC Systems
2-27
Installing AC Power Supply Modules in the AC Power Supply Tray
Making the Connections to the AC Power Supply Module(s)
Cable Management
2-31
Configuring the MGX 8230 as an MGX Feeder
3
Configuring the MGX 8230
MGX 8230 Overview
Main Features
2-28
2-30
Powering up the MGX 8230
CHA PTER
2-28
2-32
3-1
3-1
3-2
Standards-Based Conversion to ATM
MGX 8230 Management
3-3
3-4
Statistics and Command Line Interface
3-4
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
v
Contents
Alarm and Error Handling
3-4
MGX 8230 Processor and Service Modules
3-4
MGX 8230 MGX Feeder to MGX Functional Overview
MGX 8230 and MGX 8850 Relationship
3-7
MGX 8230 and MGX 8850 Command Line Interface
MGX 8230 and MGX 8250 User Interface Access
MGX 8230 and MGX 8850 Error Messages
Message Structure
3-6
3-7
3-8
3-9
3-9
Configuring an MGX 8230 MGX Feeder
3-10
Making the PXM-UI Interface Connections
Attaching a Control Console
3-11
Making External Clock Connections
Alarm Output Connection
Initial MGX 8230 Bring-Up
3-10
3-11
3-11
3-11
Bringing Up an MGX 8230-PXM With No Run-time Firmware
Configuring Node-Level Parameters
3-14
Downloading Firmware to a Service Module
MGX 8230 CLI Configuration of a Feeder
Configuring the OC-3 Uplink
3-17
3-18
3-18
CiscoView Configuration of a Feeder
Selecting an MGX 8230
3-20
3-21
Specifying the Feeder Application
3-21
Activating a Physical Line for the Uplink
3-22
Configuring Logical Interfaces for the Feeder
Configuring the Line as a Feeder Trunk
Adding Service Module Connections
Connections on a Feeder
3-12
3-22
3-23
3-24
3-24
Sequence of Configuration Tasks
Rules for Adding Connections
3-25
3-25
Rules for Adding a DAX Connection
3-25
Rules for Adding Three-Segment Connections
Redundancy Support by the MGX-SRM-3T3/B
3-26
3-27
Configuring Redundancy Through the Redundancy Bus
ATM Universal Service Module Connections
3-27
3-28
Using the CLI to Configure the Card, Lines, and Ports
3-28
Cisco MGX 8230 Installation and Configuration
vi
Release 1.0, Part Number 78-10616-01, June 2000
Contents
Using the CLI to Configure Inverse Multiplexing
3-30
Adding and Configuring Connections on the AUSM/B
Adding the Middle Segment of the Connection
Frame Relay Service Module Connections
3-31
3-35
3-35
Very High Speed Frame Service Modules
3-36
Eight-Port Channelized and Unchannelized Frame Service Module
Frame Service Module Features
MGX-FRSM-2CT3 Features
3-36
3-37
MGX-FRSM-2T3E3 Features
3-37
MGX-FRSM-HS2 Features
3-38
Eight-Port FRSM Features
3-38
Frame Relay-to-ATM Network Interworking
3-38
Congestion Indication for NIW Connections
3-39
Frame Relay-to-ATM Service Interworking
Frame Forwarding
3-39
3-41
ATM Frame-to-User Network Interface
Configuring Frame Relay Service
Adding a Frame Relay Connection
3-41
3-41
3-44
Establishing the Middle Segment of the Frame Relay Connection
Circuit Emulation Service Module Connections
Structured Data Transfer
Unstructured Data Transfer
3-47
3-48
3-48
Adding and Modifying CESM Connections
4
Maintenance
3-46
3-47
Configuring Service on an 8-Port CESM
CHA PTER
3-36
3-49
4-1
Removing and Replacing the Fan Tray Assembly
4-1
Removing and Replacing an AC Power Supply Module
Removing and Replacing a DC Power Entry Module
4-3
4-6
Removing and Replacing Processor and Service Modules
4-7
Changing a Single-Height Card Slot into a Double-Height Card Slot
Backplane Fuse Replacement
4-10
Bit Error Rate Testing (BERT) Through an MGX-SRM-3T3
Pattern Test Options
Loopback Test Options
4-7
4-11
4-14
4-15
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
vii
Contents
APPENDIX
A
Technical Specifications
A-1
MGX 8230 Enclosure, Power, and Performance Specifications
MGX 8230 Processor Switching Module Specifications
AUSM/B-8T1E1 Interface Characteristics
FRSM-2CT3 Specifications
FRSM-2CT3 Framer
A-3
A-5
A-8
A-9
FRSM-2CT3 Line Alarms
FRSM-2T3E3 Specifications
FRSM-2T3E3 T3 Line
T3 Framer Level
A-1
A-9
A-10
A-10
A-11
FRSM-2T3E3 E3 Line
E3 Framer Level
A-11
A-11
FRSM-2T3E3 Line Alarms
A-12
Statistics and Counter Specifications
FRSM-HS2 Specifications
A-12
A-12
Counters and Statistics for FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2
FRSM-8T1 Specification
A-16
FRSM-8E1 Specification
A-19
Circuit Emulation Service Module for T1 Operation
A-23
Circuit Emulation Service Module for E1 Operation
A-24
Physical and Electrical Characteristics for Cards
Electromagnetic Compatibility
Conformance
SONET/SDH
A-28
Frame Relay
A-28
A-28
A-29
Environmental
B
A-26
A-27
Circuit Emulations Service
APPENDIX
A-25
A-27
ATM UNI
Safety
A-13
A-29
Cable Specifications
T3 Trunk Cabling
B-1
B-1
Frame Relay Cabling
T1 Cabling
B-2
E1 Cabling
B-3
B-2
Cisco MGX 8230 Installation and Configuration
viii
Release 1.0, Part Number 78-10616-01, June 2000
Contents
SMB Connector
HSSI Port Connectors
DC Power Cabling
B-4
AC Power Cabling
B-5
Control and Clock Cabling
B-3
B-3
B-5
Maintenance and Control Ports
External Clock Input Cabling
T1 Clock Cabling
External Alarm Cabling
B-5
B-6
B-6
B-7
GLOSSARY
INDEX
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
ix
Contents
Cisco MGX 8230 Installation and Configuration
x
Release 1.0, Part Number 78-10616-01, June 2000
F I G U R E S
Figure 1-1
MGX 8230 with Door Attached
Figure 1-2
MGX 8230 Dimensions
Figure 1-3
MGX 8230 Card Cage, Front View
1-5
Figure 1-4
MGX 8230 Card Cage, Rear View
1-6
Figure 1-5
AC Power Supply Module, Rear View
Figure 1-6
MGX 8230 DC Power Entry Module
Figure 1-7
MGX 8230 Fan Tray Assembly
Figure 1-8
MGX 8230 Architecture Simple Block Diagram
Figure 1-9
Cell Bus Distribution
Figure 1-10
MGX 8230 PXM1
Figure 1-11
PXM1 User Interface Back Card
Figure 1-12
Four-Port OC-3 Uplink Back Card
Figure 1-13
OC-12 Long Reach Back Card
Figure 1-14
Intermediate Reach OC-12 Back Card
Figure 1-15
MGX-FRSM-2T3E3
Figure 1-16
BNC-2T3
1-21
Figure 1-17
BNC-2E3
1-22
Figure 1-18
AUSM/B-8T1E1 Front Card
Figure 1-19
Standard RJ-48 Back Card for the MGX-AUSM/B-8T1
Figure 1-20
Standard RJ-48 and SMB Back Cards for the MGX-AUSM/B-8E1
Figure 1-21
FRSM Front Cards
1-30
Figure 1-22
CESM Front Cards
1-33
Figure 1-23
MGX-SRM-3T3/B Card Set
Figure 2-1
Front Card Insertion/Extractor Lever
2-17
Figure 2-2
MGX 8230 Mounting Rail Positions
2-20
Figure 2-3
MGX 8230 Chassis with Rear Mounting Brackets for 19-Inch Rack
Figure 2-4
MGX 8230 Chassis Front View with 19-Inch Mid-Mounting Bracket
Figure 2-5
Front View of MGX 8230 with 23-Inch Mid-Mounting Brackets
Figure 2-6
Rear View of MGX 8230 with Two DC PEMs
Figure 2-7
Rear View of MGX 8230 with 1 DC PEM
Figure 2-8
DC Power Entry Module, Rear View
1-2
1-2
1-7
1-8
1-9
1-10
1-11
1-13
1-16
1-17
1-18
1-19
1-20
1-24
1-26
1-27
1-37
2-21
2-21
2-23
2-24
2-24
2-25
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
xi
Figures
Figure 2-9
Polarities at MGX 8230 PEM Pluggable Terminal Block
Figure 2-10
Pluggable Terminal Block on MGX 8230 PEM
Figure 2-11
Optional 1200 Watt AC Power Supply Module, Rear View
Figure 2-12
Rear View of MGX 8230 with Two Optional AC Power Supply Modules
Figure 2-13
Rear View of MGX 8230 with One AC Power Supply Module
Figure 2-14
Cable Management System on Rack-Mount MGX 8230
Figure 3-1
MGX 8230
Figure 3-2
MGX 8230 MGX Feeder Application
Figure 3-3
Typical MGX 8230 as MGX Feeder Application
Figure 3-4
PXM-UI Faceplate
Figure 3-5
MGX 8230 MGX Feeder Application
Figure 3-6
Frame Relay Connection Through an MGX 8230/MGX/BPX Network
Figure 3-7
MGX 8230/MGX/BPX Network with NIW Connections
3-38
Figure 3-8
MGX 8230/MGX/BPX Network with SIW Connections
3-39
Figure 4-1
Fan Tray Assembly
Figure 4-2
Fan Tray Assembly in MGX 8230 Chassis
Figure 4-3
AC Power Supply Module, Rear View
Figure 4-4
MGX 8230 with Two AC Power Modules Installed
Figure 4-5
DC Power Entry Module
Figure 4-6
MGX 8230 Slot Numbering
Figure 4-7
Center Guide Module, Slot Divider
Figure 4-8
Front View of an MGX 8230 Card Cage
Figure 4-9
Backplane Fuses
Figure B-1
RJ-48 Connectors
2-25
2-26
2-27
2-29
2-30
2-31
3-2
3-2
3-6
3-11
3-14
3-26
4-2
4-3
4-4
4-4
4-6
4-7
4-8
4-9
4-11
B-3
Cisco MGX 8230 Installation and Configuration
xii
Release 1.0, Part Number 78-10616-01, June 2000
T A B L E S
Table 1-1
Cell Bus Distribution
Table 1-2
Eight-Port AUSM/B LED Indicators
Table 1-3
LED Indicators for 8-Port CESM
Table 3-1
MGX 8230 Feeder Connection Endpoints
Table 4-1
Pattern Test for AX-FRSM-8T1, AX-CESM-8T1, and MGX-FRSM-2CT3
Table 4-2
Loopback Test for AX-FRSM-8T1, AX-CESM-8T1, and MGX-FRSM-2CT3
Table 4-3
Pattern Test for AX-FRSM-8E1 and AX-CESM-8E1
Table 4-4
Loopback Test for AX-FRSM-8E1 and AX-CESM-8E1
Table 4-5
Pattern Test for MGX-AUSM-8T1
Table 4-6
Loopback Test for MGX-AUSM-8T1
Table 4-7
Pattern Test for MGX-AUSM-8E1
Table 4-8
Loopback Test for MGX-AUSM-8E1
Table A-1
Enclosure and Electrical Characteristics
Table A-2
PXM Specifications
Table A-3
Physical Characteristics of the AUSM/B-8T1E1
Table A-4
T1 Interface Characteristics
A-6
Table A-5
E1 Interface Characteristics
A-6
Table A-6
ATM Interface Characteristics
Table A-7
AUSM/B-8T1E1 Statistics and Counters
Table A-8
Frame Relay Interface Standards
Table A-9
FRSM-2CT3 Front Card Physical Characteristics
Table A-10
FRSM-2CT3 Line Level
Table A-11
Frame Relay Interface Standards
Table A-12
FRSM-2T3E3 Front Card Physical Characteristics
Table A-13
T3 Line Level
A-10
Table A-14
E3 Line Level
A-11
Table A-15
Frame Relay Interface Standards
Table A-16
FRSM-HS2 Physical Characteristics
Table A-17
FRSM-HS2 Line Characteristics
Table A-18
Counters per Line
Table A-19
Service-Related Statistics
1-11
1-25
1-34
3-7
4-12
4-13
4-13
4-13
4-13
4-13
4-13
4-14
A-2
A-3
A-5
A-7
A-7
A-8
A-8
A-9
A-10
A-10
A-12
A-12
A-13
A-13
A-14
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
xiii
Tables
Table A-20
ATM Cell-Related Statistics
Table A-21
Diagnostic-Related Statistics
Table A-22
Troubleshooting Statistics
Table A-23
General Card Specifications
Table A-24
Frame Relay Service With T1 Lines
Table A-25
System Interface
Table A-26
List of Counters
Table A-27
General Card Specifications
Table A-28
Frame Relay Service With E1 Lines
Table A-29
System Interface
Table A-30
List of Counters
Table A-31
CESM 8T1 Card Information
A-23
Table A-32
CESM 8E1 Card Set Details
A-24
Table A-33
Physical Characteristics and Power Consumption by Card
Table A-34
Electromagnetic Compatibility and Immunity
Table B-1
Trunk Cables
Table B-2
T3 Connector Pin Assignments
Table B-3
RJ-48C T1/E1 Connector Pin Assignments
Table B-4
E1 Trunk/Circuit Line Cabling Specification
Table B-5
E1 Connector Pin Assignments (unbalanced)
Table B-6
Pinouts for SCSI-II Connector
Table B-7
DC Power Wiring
B-4
Table B-8
AC Power Cables
B-5
Table B-9
Maintenance and Control Port Cabling
Table B-10
RJ-45 Maintenance and Control Port Pin Assignments
Table B-11
7T1 Clock Cabling
Table B-12
External Alarm Cabling
Table B-13
Network Alarm Pin Assignments
A-15
A-15
A-16
A-16
A-16
A-18
A-18
A-19
A-20
A-21
A-22
A-25
A-26
B-1
B-1
B-2
B-3
B-3
B-4
B-5
B-5
B-6
B-7
B-7
Cisco MGX 8230 Installation and Configuration
xiv
Release 1.0, Part Number 78-10616-01, June 2000
Preface
This hardware installation guide describes the physical installation of the MGX 8230. The MGX 8230
is a 12-slot chassis, built on the MGX 8850 architecture, that is used as a feeder to a BPX/IGX network.
This preface contains the following sections:
•
Audience
•
Purpose
•
Organization
•
Conventions
•
Related Documentation
•
Accessing Electronic Documentation
•
Contacting Cisco
Audience
This publication is intended for the person who will do the physical installation of the MGX 8230. The
MGX 8230 is typically collocated and rack-mounted with either an IGX 8400 or BPX 8850 series
switch. The MGX 8230 installer should be familiar with electronic circuitry and wiring practices and
have experience as an electronic or electromechanical technician, as well as with the Cisco IGX/BPX
switches.
Note
Warning
This Cisco MGX 8250 Installation and Configuration covers the Installation and
Configuration for the equipment. The Command Reference and Error Codes for the MGX
8230 are described in the section “Related Documentation."
Installation of the equipment should be performed by trained service personnel.
Cisco MGX 8250 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
xv
Preface
Organization
Organization
This document is organized into the following chapters and appendices:
Chapter 1
MGX 8230 Overview
Provides an overview, including a physical description, of the MGX 8230
and its application as a feeder to the IGX switch.
Chapter 2
Installation
Provides the procedures for rack mounting and connecting power to the
MGX 8230.
Chapter 3
Configuring the MGX 8230
Provides the procedures for configuring the MGX 8230 as a feeder to the
IGX switch.
Chapter 4
Maintenance
Provides the removal and replacement procedures for MGX 8230
subassemblies.
Appendix A
Technical Specifications
Lists the relevant specifications for the MGX 8230.
Appendix B
Cable Specifications
Provides information about the cables and connectors used with
MGX 8230.
Glossary
Provides definitions of the terms and acronyms that are relevant to the
Service Expansion Shelf.
Conventions
This publication uses the following conventions to convey instructions and information.
Command descriptions use these conventions:
•
Commands and keywords are in boldface.
•
Arguments for which you supply values are in italic font.
•
Elements in square brackets ([ ]) are optional.
•
Alternative but required keywords are grouped in braces ({ }) and are separated by vertical bars ( | ).
Examples use these conventions:
•
Terminal sessions and information the system displays are in screen font.
•
Information you enter is in boldface screen font.
•
Nonprinting characters, such as passwords, are in angle brackets (< >).
•
Default responses to system prompts are in square brackets ([ ]).
Cisco MGX 8250 Installation and Configuration
xvi
Release 1.0, Part Number 78-10616-01, June 2000
Preface
Related Documentation
Note
Caution
Warning
Means reader take note. Notes contain helpful suggestions or references to materials not
contained in this manual.
Means reader be careful. In this situation, you might do something that could result in
equipment damage or loss of data.
This warning symbol means danger. You are in a situation that could cause bodily injury.
Before you work on any equipment, you must be aware of the hazards involved with
electrical circuitry and familiar with standard practices for preventing accidents.
Related Documentation
The following Cisco publications contain information necessary for the understanding the installation
and the operation of the MGX 8230 as a feeder to the BPX/MGX. Since the MGX 8230 is built using
the MGX 8800 series architecture, and uses the MGX 8800 command line interface, the MGX 8800
series documentation is also listed here.
•
The IGX 8400 series switch documentation set for Release 9.3, including:
– Cisco IGX 8400 Series Installation and Configuration—Provides a detailed description of
installing and configuring an IGX 8400 series switch. (Note that the July 1999 release of this
document contains an appendix that describes configuring an MGX 8230 as a feeder for the
IGX.)
– Cisco IGX 8400 Series Reference—Provides a general reference for the IGX 8400 series switch
and the services it provides.
•
The BPX 8600 series switch documentation set for release 9.3, including:
– Cisco BPX 8600 Series Installation and Configuration—Provides a detailed description of
installing and configuring a BPX 8600 series switch.
– Cisco BPX 8600 Series Reference—Provides a general reference for the BPX 8600 series
switch and the services it provides.
•
The MGX 8250 switch documentation set for release 1, including:
– Cisco MGX 8250 Installation and Configuration—Provides a detailed description of the PXM
processor cards used in both the MGX 8250 and MGX 8230.
– Cisco MGX 8230 Command Reference—Provides a detailed description of the command line
interface command set used by the MGX 8230.
•
Cisco WAN Switching Command Reference—Provides detailed information about the WAN
command line interface and the commands used to configure BPX and IGX switches.
•
Cisco WAN Switching SuperUser Command Reference—Provides detailed information about the
WAN switching superuser commands.
•
Cisco WAN Manager Documentation for Release 9.2—Provides information about using the Cisco
WAN Manager (formerly known as StrataView Plus) network management system.
•
CiscoView for the MGX 8850—Provides general information about using CiscoView, which can be
used to configure either MGX 8850 or MGX 8230 processor and service modules.
Cisco MGX 8250 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
xvii
Preface
Accessing Electronic Documentation
Accessing Electronic Documentation
Cisco documentation and additional literature are available in a CD-ROM package, which ships with
your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated
monthly. Therefore, it might be more current than printed documentation. To order additional copies of
the Documentation CD-ROM, contact your local sales representative or call customer service. The
CD-ROM package is available as a single package or as an annual subscription. You can also access
Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com,
or http://www-europe.cisco.com.
Contacting Cisco
If you are reading Cisco product documentation on the World Wide Web, you can submit comments
electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback
form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments on
our documentation.
Cisco MGX 8250 Installation and Configuration
xviii
Release 1.0, Part Number 78-10616-01, June 2000
CH A P T E R
1
MGX 8230 Overview
The chapter introduces and describes the MGX 8230.
This chapter includes the following sections:
•
MGX 8230 Physical Description
•
MGX 8230 Processor and Service Modules
•
MGX 8230 Management
•
Redundancy Architecture
MGX 8230
The MGX 8230 is a 12-slot chassis with horizontally mounted processor modules, service modules,
SRM modules, and back cards. Built with the MGX 8850/8250 architecture, the MGX 8230 accepts the
same double-height and single-height service modules as the MGX 8250, with a few exceptions. The
MGX 8230 does not support the route processor module (RPM), or the Voice Interface Service Module
(VISM) of the MGX 8250.
Figure 1-1 shows the MGX 8230 with its door attached. Note that there are light pipes in the door that
display the status of the processor models (PXMs). Figure 1-2 is a conceptual drawing of an MGX 8230
showing the dimensions and the slot numbering. The slot numbering is as it appears from the front of
the MGX 8230; slots 8 and 9 refer to back card slots only.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-1
Chapter 1
MGX 8230 Overview
MGX 8230
MGX 8230 with Door Attached
Figure 1-2
MGX 8230 Dimensions
F
A
N
7 RU
(12.25 in.,
31.1 cm.)
T
R
A
Y
7
SRM 1
SRM 2
14
6
SM 5
SM 6
13
5
SM 3
SM 4
12
4
SM 1
SM 2
11
3
ASXM
10
2
PXM 2
9
1
PXM 1
8
1 RU
(1.75 in.,
4.5 cm.)
Optional AC power tray
38375
23823
Figure 1-1
23.5 in.,
(59.7 cm.)
17.72 in.
(45 cm.)
Cisco MGX 8230 Installation and Configuration
1-2
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230
Note
Even though the card slots in an MGX 8230 are horizontal and would more appropriately
be called single-width and double-width, this manual still refers to the card slots, and the
processor and service modules, as single-height and double-height. This is for consistency
because the PXM and service module cards are a subset of the MGX 8850 cards that are
installed vertically in an MGX 8850 chassis.
Main Features
Release 1.0 of MGX 8230 feeder includes:
•
PXM1 with 4-port OC-3c ATM port.
– MMF and SMF IR back cards are supported.
– PXM1 ports are used as feeder trunks only.
– Core redundancy for PXM1.
– Environmental monitoring.
•
ATM, Frame Relay, and Circuit Emulation service modules.
– AUSM-8T1/E1/B with RJ48-T1/E1 and SMB E1 back card with UNI and IMA support.
– FRSM-8T1/E1 with RJ48-T1/E1 and SMB E1 back cards.
– FRSM-2T3E3 with BNC-2T3/E3 back cards.
– FRSM-HS2 with 2 port HSSI back card.
– FRSM-2CT3 with BNC-2T3 back card.
– CESM-8T1/E1 with RJ48-T1/E1 and SMB E1 back cards.
•
1:1 redundancy for T3/E3 cards.
•
1:1 redundancy for T1/E1 service modules.
•
Graceful upgrade.
•
1000 connections per card, 4000 connections per shelf
The Service Resource Module-3T3 (MGX-SRM-3T3/B) can support up to 80 T1 interfaces over its
three T3 lines and provide 1:N redundancy for the T1 and E1 cards.
The MGX 8230 backplane supports a minimum of 1.2 Gbps of non-blocking switching and has a
high-end limit of 21 Gbps with the PXM1. Individual line rates can range from DS0 through OC-3.
The MGX 8230 can also support a wide range of services over narrowband and mid-band user
interfaces. It maps all the service traffic to and from ATM circuits based on standardized interworking
methods.
The MGX 8230 supports up to 80 channelized or non-channelized T1 and E1 interfaces on a single
IP + TM multiservice gateway. These interfaces support:
•
Frame Relay UNI and NNI
•
ATM UNI, NNI, and FUNI
•
Frame Relay-to-ATM network interworking
•
Frame Relay-to-ATM service interworking
•
Circuit emulation services
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-3
Chapter 1
MGX 8230 Overview
MGX 8230 Physical Description
Frame-based services on T3 and E3 high-speed lines are also supported.
The MGX 8230 also supports Inverse Multiplexing for ATM (IMA) to provide ATM connectivity below
T3 or E3 rates via the AUSM-8T1/E1.
The modular, software-based system architecture enables it to support new features through
downloadable software upgrades or new hardware modules.
Standards-Based Conversion to ATM
The MGX 8230 converts all user-information into 53-byte ATM cells by using the appropriate ATM
Adaptation Layer (AAL) for transport over the ATM backbone network. The individual service modules
segment and reassemble (SAR) cells to eliminate system bottlenecks. The following list shows the
applicable AAL for each service:
•
Circuit emulation services uses AAL1.
•
Frame Relay-to-ATM network interworking uses AAL5 and Frame Relay Service Specific
Convergence Sub-layer (FR-SSCS).
•
Frame Relay-to-ATM service interworking uses both transparent and translation modes to map
Frame Relay to native ATM AAL5.
•
Frame Forwarding uses AAL5.
Appendix A, “Technical Specifications” lists all the relevant specifications and conformance
information for the MGX 8230.
MGX 8230 Physical Description
This section includes:
•
MGX 8230 Chassis/Enclosure
•
MGX 8230 Power System
•
Cooling System
•
MGX 8230 Architecture
•
Cell Bus
MGX 8230 Chassis/Enclosure
The MGX 8230 can be either rack mounted in a 19-inch rack, or fitted with side panels to be a
free-standing box, referred to as a stand-alone MGX 8230. An optional mounting bracket kit is available
for mounting in 23-inch racks. The overall dimensions for the chassis are:
Depth
23.5 inches (excluding cable management)
Width
19.00 inches (including front rack-mounting flanges)
Height
12.25 inches (excluding optional AC Power Tray)
Height
14.00 inches (including optional AC Power Tray)
Cisco MGX 8230 Installation and Configuration
1-4
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Physical Description
The MGX 8230 chassis has two dedicated slots for the PXM1 (slots 1 and 2), two dedicated slots for
SRM modules only (slots 7 and 14—no other Service Modules can be used in these two slots), and eight
single-height slots (four double-height slots) for service modules, as shown in Figure 1-2. One
additional feature available only on the MGX 8230 chassis is the ability to convert individual single
height slots into double height slots.
The slots are numbered 1 to 7 on the left half of the chassis. The slots on the right side of the chassis
are numbered 8 to 14. Since front slots 1 and 2 are always double-height for PXM1 processor modules,
slots 8 and 9 only refer to the back card slots that correspond to the two lower single-height slots on the
left side of the chassis as seen from the rear. When a double-height front card is plugged in, the left slot
number is used. The back cards are numbered according to the front card numbering scheme, with the
exception of slots 8 and 9 as noted above.
When converting single height slots into double height slots the conversion must start from the bottom
and be contiguous. For example, before you can convert slot 4 into double height, slot 3 must be
converted first as shown in Figure 1-2.
Figure 1-3 is a front view of an empty MGX 8230 chassis and Figure 1-4 is a rear view.
MGX 8230 Card Cage, Front View
26268
Figure 1-3
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-5
Chapter 1
MGX 8230 Overview
MGX 8230 Physical Description
MGX 8230 Card Cage, Rear View
26269
Figure 1-4
MGX 8230 Power System
The MGX 8230 power system is designed with distributed power architecture centered around a
-48 VDC bus on the system backplane. The -48 VDC bus accepts redundant DC power from either a
-42 to -56 VDC source via optional DC power entry modules (PEMs) or from a 100 to 120 or a 200 to
240 VAC source via the optional AC Power Supply Tray. The MGX 8230 backplane distributes power
via connectors on the - 48 VDC bus to each hot-pluggable processor or service module. Each card
incorporates on-board DC-DC converters to convert the -48 VDC from the distribution bus voltage to
the voltages required on the card.
Optional AC Power Supply
For an AC-powered MGX 8230, an optional AC power supply tray is attached to the bottom of the MGX
8230 card cage at the factory. The AC power supply tray is one rack-unit high, and can hold up to two
AC Power Supply modules. Each AC Power Supply module can provide up to 1,200W at -48VDC and
has its own AC power cord and power switch. Figure 1-5 shows the rear view of an optional AC Power
Supply module. The power supplies can be configured as 1+1 redundant. If no redundancy is desired,
an AC tray with one AC power supply and one AC power cord can also be ordered.
Cisco MGX 8230 Installation and Configuration
1-6
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Physical Description
AC Power Supply Module, Rear View
23818
Figure 1-5
AC DC
Each AC Power Supply Module incorporates the following features:
•
1 rack unit high
•
An output capacity of 1200 Watts at -48 VDC
•
O-ring diode
•
EMI filtering
•
Cooling fan
•
Power switch
•
DC and AC status LEDs
DC-Powered MGX 8230
For DC systems, a DC Power Entry module (PEM) is required for each DC source of central office
power -42 to -56VDC. The MGX 8230 can support two DC power sources and has rear panel slots for
two DC PEMS. Figure 1-6 illustrates a DC PEM.
The DC PEMs incorporate the following features:
•
Hot swappable
•
O-ring diode
•
EMI filtering
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-7
Chapter 1
MGX 8230 Overview
MGX 8230 Physical Description
MGX 8230 DC Power Entry Module
17275
Figure 1-6
OFF
TB1
48 VDC
30A
3
2
1
Cooling System
The MGX 8230 incorporates a fan tray assembly (with eight fans) located on the left side of the card
cage to pull ambient cooling air into the system through openings between front card faceplates, over
the boards in the card cage, and out through air exhaust openings on the left side of unit. Figure 1-7 is
an illustration of the MGX 8230 fan tray assembly.
The cooling system incorporates the following design features:
•
-48 VDC fans with rotation sensing
•
N+1 fan redundancy
•
Hot pluggable (if done quickly) Fan Tray Assembly
•
Noise level < 65 dBA
Cisco MGX 8230 Installation and Configuration
1-8
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Physical Description
MGX 8230 Fan Tray Assembly
17274
Figure 1-7
MGX 8230 Architecture
The MGX 8230 architecture is built around the switching fabric on the processor switching module
(PXM1), the backplane, and the service modules. Figure 1-8 is a very simple block diagram of the MGX
8230 architecture.
The main functions of the MGX 8230 backplane are to connect cards together, terminate critical signals
properly, provide -48 VDC power to all cards, and set ID numbers for each slot. In addition, the MGX
8230 backplane interconnects both front cards and back cards together via pass-through connectors. A
software readable ID on the backplane is available for software to identify that the chassis is an MGX
8230.
The cell bus controllers (CBCs) are application specific integrated circuits (ASICs) and provide the
interface between the switching fabric and the service modules.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-9
Chapter 1
MGX 8230 Overview
MGX 8230 Physical Description
Figure 1-8
MGX 8230 Architecture Simple Block Diagram
MGX 8230-PXM
front card
PXM-UI
back card
Processor
Maintenance and
control ports
LAN ports
T1/E1 clocks
Alarm outputs
PXM
uplink
back card
OC-3, OC-12,or
T3/E3 daughter card
CBC
Cell buses
to and from
service modules
CBC
MGX 8230 midplane
38377
Shared
memory
switch
OC-3, OC-12,or
T3/E3 feeder link
Cell Bus
The MGX 8230 cell bus (CB) provides high-speed interface between the switch fabric and the service
modules.
Figure 1-9 shows the overall cell bus distribution of MGX 8230 backplane and Table 1-1 lists the
specific cell bus allocation to each slot with respect to master and slave cell bus ports.
Each PXM1 supports eight master cell buses and one slave cell bus connected to the backplane. The
service modules have two slave cell bus ports, one from each PXM1. The master cell bus ports are CB0
to CB7 and the PXM1 slave ports are referred to as 7S and 8S in Table 1.
A cell bus comprises the group of signals used to transfer data between the PXM and a service module.
CB 0, 6, 1, 2, 4, and 3 are dedicated service modules, CB5 supports physical slot 6. CB7 supports
physical slot 13 as well as the alternate PXM1’s slave port.
There is a connection on cell bus 7 to the alternate PXM1. A PXM1 is able to communicate with the
other PXM1 using the slave cell bus port on that card. Slots 8 and 9 only refer to back card slots.
Cisco MGX 8230 Installation and Configuration
1-10
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Physical Description
Figure 1-9
Cell Bus Distribution
Left side of chassis
Right side of chassis
7
14
6
13
5
12
4
11
3
10
9
1
PXM
8
38376
CB2
CB4
CB3
CB7
PXM
CB0
CB6
CB1
CB5
2
Table 1-1
Cell Bus Distribution
Left Side Chassis
Right Side Chassis
Physical Slot #
1
2
3
4
5
6
7
10
11
12
13
14
Slot ID Address
1s
2s
9
A
B
C
D
9
A
B
C
D
CB0_A/B
x
CB1_A/B
x
CB2_A/B
x
CB3_A/B
x
CB4_A/B
x
CB5_A/B
x
CB6_A/B
x
CB7_A
CB7_B
x
x
x
x
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-11
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
MGX 8230 Processor and Service Modules
The MGX 8230 supports the following processor and service modules:
Note
•
MGX 8230 Processor Switch Module (PXM1)
•
ATM Universal Service Module
•
Frame Service Module Features
•
Circuit Emulation Service Module 8T1E1
•
Service Resource Module (SRM-3T3)
The MGX 8230 does not support the Route Processor Module (RPM) or the Voice
Interface Service Module (VISM) of the MGX 8850/8250.
MGX 8230 Processor Switch Module (PXM1)
The MGX 8230 Processor Switch Module (PXM1) performs shelf control and shared-memory
switching functions. It also serves as a data processing and ATM interface card. The PXM1 processor
module for the MGX 8230 is identical to the PXM1 for the MGX 8250.
Primarily, the MGX 8230 PXM1 controls the switch and provides 1.2 Gbps of non-blocking, shared
memory ATM switching and ATM trunking up to OC-12 speed. In addition, the PXM features:
•
A 4.0-Gigabyte hard disk drive that holds software, firmware for all the cards, and a substantial
amount of other information.
•
Environmental monitoring (cabinet temperature, fan speed, and power supply voltages).
•
Hot swappable, 1:1 redundancy.
Figure 1-10 is an illustration of a PXM1, in vertical orientation although the card is mounted
horizontally in an MGX 8230 chassis. The specifications for the PXM1 are listed in Appendix A,
Technical Specifications.
The PXM1 and its two types of back cards make up the required control card set. The following are
model numbers of cards supported by the MGX 8230 for this release:
•
PXM1-4-155, PXM1-1-622, and PXM1-2-T3E3
•
PXM-UI (user interface back card)
•
MGX-MMF-4-155 (uplink back card)
•
MGX-SMFIR-4-155 (uplink back card)
•
MGX-SMFLR-4-155 (uplink back card)
•
MGX-BNC-2-T3 (uplink back card)
•
MGX-BNC-2-E3 (uplink back card)
•
MGX-SMFIR-2R-1-622 (uplink back card)
•
MGX-SMFLR-1-622 (uplink back card)
Cisco MGX 8230 Installation and Configuration
1-12
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
26745
Figure 1-10 MGX 8230 PXM1
The M1 switch has 1.2 Gbps non-blocking, shared-memory ATM switching and ATM trunking up to
OC-12 speed.
The MGX 8230 supports hot insertion and removal of the PXM1 module, as well as 1:1 hot standby
redundancy for high availability. The active and redundant PXM1 modules reside in slots 1 and 2.
The PXM1 (see MGX 8230 Architecture Simple Block Diagram) also provides the following interfaces
and indicators:
•
Four LED indicators (card status, critical/major/minor network alarms, LAN control port activity
detect, and DC power status)
•
Up to four LED indicators for Uplink port, depending on the number of uplink ports supported.
•
Support for two back cards: User Interface and Uplink
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-13
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Clocking Options
The PXM1 supports primary and secondary network synchronization and switchover. Synchronization
source can be derived from:
•
T1/E1 BITS input (the E1 BITS input will accept either E1 data signal or E1 synchronization
signal)
•
Recovered clock from any uplink port
•
Internal Stratum 4 oscillator
It is anticipated that an optional Stratum 3 clock module will be available in a future release. This
module will reside on the same slot as the PXM-UI back card.
Management Interfaces
The following functions are supported by the UI card:
•
User and management interface to an ASCII terminal or workstation
•
Network synchronization for the shelf
•
Central office compatible major/minor alarm interface
System Environment Monitoring
The following environmental parameters are monitored by the PXM1:
•
-48 VAC power supply status
•
5V and 3.3V onboard power status
•
Cooling fan revolution
•
Enclosure temperature
Minor and major alarms will be generated when one or more environmental parameters are out of range.
Alarm Circuit and Indicators
PXM1 provides connectors for external audio and visual alarms. The interface can either be always
open or always closed. Major and minor alarms are controlled separately. An alarm cutoff button is
accessible from the front. A history LED is set when the alarm cutoff button is pressed. The history LED
can be cleared by pressing the history clear button on the faceplate.
The PXM1 provides the following indicators:
•
System Status Active/Standby/Fail/standby update (green/yellow/red/flashing yellow)
•
Critical alarm (blue)
•
Major alarm (red)
•
Minor alarm (yellow)
•
DC OK A (green = OK, red = not OK)
•
DC OK B (green = OK, red = not OK)
•
ACO (green)
•
History (green)
Cisco MGX 8230 Installation and Configuration
1-14
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
•
Port activity (active and clear = green, remote alarm = yellow, local alarm = red)
•
LAN activity (flashing green)
PXM1 provides three types of non-volatile storage:
•
Flash: This is used to store boot code for the processor. The boot code can be upgraded in the field
by a software download.
•
Hard drive: The PXM1 hard drive is a 2.5-inch, 4.0 -Gbyte IDE drive. Configuration information
and code for the PXM and service modules are stored on the drive, and can be updated during
system operation or by user download.
•
Battery backed up RAM: The BRAM is used to store bookkeeping information for the card.
Information stored includes:
– Identifiers such as board hardware revision, serial number, and PCB part number
– MAC address of the PXM
– Hard drive parameters such as number of heads and cylinder size
The BRAM also acts as a temporary cache. If for any reason the hard drive fails, information logged
immediately before the failure can be stored in the BRAM for further analysis.
Physical Layer OC-3c/STM-1 Interface
The OC-3c/STM-1 interface provides the feeder trunk uplink with:
•
Four OC-3c/STM-1 (155.520 Mbps) ports
•
Trunk or port interface mode
•
Cell transfer rate of 353,208 cells per second
•
Compliance with SONET standards (Bellcore GR-253-CORE and ANSI T1.105)
•
Compliance with SDH standards (ITU-T G.707, G.957, and G.958)
•
1:1 PXM1 redundancy
•
SONET APS
•
Linear APS
ATM Layer
The ATM layer is configurable for trunk and public or private UNI applications. It is conformant to
ATM Forum UNI Specification V3.0, 3.1, ITU-T I.361 and I.432 specifications, and it supports virtual
circuit connections (VCCs) and virtual path connections (VPCs) per ATM Forum UNI Specification
V3.1 and ITU-T I.371.
The ATM layer supports the following maximum connections:
•
32,000 connections per card
•
4096 UNI connections per card
The virtual path identifier (VPI)/virtual channel identifier (VCI) range for VCCs and VPCs is per UNI
Specification 3.1.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-15
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
PXM1 User Interface Back Card
The PXM1 User Interface card (PXM-UI) provides the MGX 8230 with the several user- interface ports.
It mates with an PXM1 through the backplane and is installed in a back card slot (slot 8 or 9). As seen
from the back of the MGX 8230, the PXM-UI will plug into the slot that is on the right side of its
corresponding PXM1. The user-interface ports provide the following functions:
•
User and management interface to an ASCII terminal or workstation
•
Network synchronization for the shelf
•
Central office-compatible major/minor alarm interface
Figure 1-11 illustrates an PXM-UI as it would be oriented for plugging into MGX 8230 back card slot
8 or 9. From right to left, the PXM UI has the following physical connectors and interfaces:
•
RJ-45 T1 clock input—BITS clock source
•
RJ-45 Maintenance port—RJ-45 connector, EIA/TIA 232, DTE mode, asynchronous
interface, 19200 bits per second, 1 start bit, 1 stop bit, no parity bits.
•
RJ-45 Control port—EIA/TIA 232, DTE mode, asynchronous interface, 9600 bits per second,
1 start, 1 stop, no parity.
•
RJ-45 LAN port—10BaseT, 802.3 Ethernet
•
SMB connector E1 clock input—BITS clock source
•
DB-15 female connector for alarm outputs
Figure 1-11 PXM1 User Interface Back Card
Maintenance
port
C
P
T1
M
P
C
L
O
C
K
L
A
N
A
L
A
R
M
E1 clock
source
PXM-UI
E1 CLOCK
Alarm
outputs
T1 clock
26261
LAN port
Control
port
The specifications for the UI interface card are listed in Appendix A, Technical Specifications.
MGX 8230 OC-3 Uplink Back Card
The MGX 8230 Uplink back card, which mates with a corresponding PXM1 through the backplane,
provides the feeder trunk to the MGX switch. This uplink back card can provide either a multi-mode or
single-mode fiber OC-3 interface:
•
MGX-MMF-4-155 (multi-mode fiber uplink back card)
•
MGX-SMFIR-4-155 (single-mode fiber intermediate reach uplink back card)
•
MGX-LMFLR-4-155 (single-mode fiber long reach uplink back card)
Cisco MGX 8230 Installation and Configuration
1-16
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Figure 1-12 shows an a 4-port MMF back card (MMF-4-155) in the orientation that the card will be
inserted into an MGX 8230 backslot. MGX 8230 applications will also use an SMFIR-4-155 and an
SMFLR-4-155 back card. From the back of the MGX 8230, the uplink back card is on the left side of
the corresponding PXM1. The ports are numbered from right to left from 1 to 4 as shown and has SC
connectors. The specifications for these cards are listed in Appendix A, Technical Specifications.
MMF-4-155
ENABLED
RX
SIGNAL
P
O
R
T
1
TX
RX
SIGNAL
P
O
R
T
2
TX
RX
SIGNAL
P
O
R
T
3
TX
RX
SIGNAL
P
O
R
T
4
TX
26262
Figure 1-12 Four-Port OC-3 Uplink Back Card
OC-12 Uplink Back Card
An illustration of the long-reach OC-12 card appears in Figure 1-13. For specifications on this card,
refer to Appendix A, “Technical Specifications” Note that Automatic Protection Switching (APS)
requires the “B” model—an SMFLR-1-622/B.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-17
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Figure 1-13 OC-12 Long Reach Back Card
SMFLR-1-622
ENABLED
SIGNAL
RX
12210
TX
SMFIR-1-622 Back Card
The intermediate reach OC-12 back card appears in Figure 1-14. For specifications on this card, refer
to Appendix A, “Technical Specifications” Note that Automatic Protection Switching (APS) requires
the “B” model—an SMFIR-1-622/B.
Cisco MGX 8230 Installation and Configuration
1-18
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Figure 1-14 Intermediate Reach OC-12 Back Card
SMFLR-1-622
ENABLED
SIGNAL
RX
12210
TX
MGX-FRSM-2T3E3 Front Card
Figure 1-15 shows the MGX-FRSM-2T3E3 front card. Refer to Appendix A, “Technical
Specifications.” for detailed information on this card.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-19
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Figure 1-15 MGX-FRSM-2T3E3
CLEI Code Label
ACT
STBY
FAIL
PORT 1
FRSM
2T3E3
22170
PORT 2
Front Card
Cisco MGX 8230 Installation and Configuration
1-20
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
BNC-2T3 Back Card
An illustration of the two-port T3 back card appears in Figure 1-16. For card specifications, refer to
Appendix A, “Technical Specifications.”
Figure 1-16 BNC-2T3
BNC-2T3
SIGNAL
RX
PORT 1
TX
SIGNAL
RX
PORT 2
12209
TX
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-21
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
BNC-2E3 Back Card
Two versions of the BNC-2E3 card are available. The BNC-2E3A applies to Australia only, and the
BNC-2E3 applies to all other sites that require E3 lines on the PXM uplink card. An illustration of the
two-port E3 back card appears in Figure 1-17. For specifications on this card, refer to Appendix A,
“Technical Specifications.”
Figure 1-17 BNC-2E3
BNC-2T3
SIGNAL
RX
PORT 1
TX
SIGNAL
RX
PORT 2
12209
TX
ATM Universal Service Module
The 8-port ATM Universal Service Module (AUSM/B-8T1E1) is a multi-purpose card set with eight T1
or E1 lines that can be used in either an MGX 8230 IP + ATM multiservice gateway or an MGX 8250
switch.
ATM Inverse Multiplexing (IMA) N x T1 and N x E1 trunking that complies with ATM Forum v3.0,
v3.1: IMA supports inverse multiplexed trunks at maximum rates of 12 Mbps for T1 or 16 Mbps for E1
between the MGX 8230 and other equipment. Consequently, AUSM IMA supports inverse multiplexed
trunks between BPX 8620/IGX 8400 series network nodes through local or remote MGX 8230 shelves.
Cisco MGX 8230 Installation and Configuration
1-22
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
•
ATM UNI card with high port density: with AUSMs in all 10 MGX 8230 service module slots, an
MGX 8230 can support up to 80 individual T1 or E1 lines. In UNI/NNI mode, an individual card
set can support 1000 data connections and 16 management connections.
•
UNI/NNI access to CPE or other networks: this application provides access over a UNI to
IMA-based CPE or an NNI to another ATM network.
•
NNI/NNI access to CPEs: this application supports ATM ports over a single T1 or E1 line and IMA
ports over multiple T1 or E1 lines (connected to IMA-based CPE).
•
Classes of service: CBR, VBR, ABR, and UBR with per-VC queuing on ingress and multiple
class-of-service queues on egress.
•
Statistics collection.
•
Support for VP connections.
•
Network synchronization by using a line as a clock source.
•
Support for BERT functionality with loopback pattern generation/verification on individual lines.
•
1:1 redundancy through a Y-cable for E1 operation using an SMB-8E1 back card.
•
Automatic card-restore.
•
SNMP and TFTP to support card and connection management
•
Resource partitions for individual network control applications, such as a Multiprotocol Label
Switching (MPLS) controller.
AUSM/B Front Card
The AUSM/B front card oversees all major functions of the ATM interface. It contains firmware for both
the T1 and the E1 line interfaces and downloads from the PXM1 the appropriate code when it recognizes
the back card type. For specifications of the AUSM/B, refer to Appendix A, Technical Specifications.
Figure 1-18 illustrates the front panel of an AUSM/B front card. This faceplate will be rotated
90 degrees to the left when it is installed in a front card slot of an MGX 8230.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-23
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Figure 1-18 AUSM/B-8T1E1 Front Card
CLEI Code Label
ACT
STBY
FAIL
PORT 1
PORT 2
PORT 3
PORT 4
PORT 5
PORT 6
PORT 7
PORT 8
AUSM
Front card
S6183
8T1/E1
Cisco MGX 8230 Installation and Configuration
1-24
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Table 1-2 describes what the AUSM/B LEDs indicate.
Table 1-2
Eight-Port AUSM/B LED Indicators
Type of LED
Color
Description
PORT LED
Green
Green indicates the port is active.
Red
Red indicates a local alarm on the port.
Yellow
Yellow indicates a remote alarm on the port.
Off indicates the port has not been activated (upped).
ACTIVE LED
Green
On indicates the card set is in active mode.
STANDBY LED
Yellow
Slow blink with Active LED off means the card is in the boot
state.
Fast blink with Standby LED on means card is receiving
firmware.
Fast blink indicates the service module is passing BRAM channel
information to the PXM.
Steady yellow indicates the card is in Standby mode and the
firmware is executing ADMIN code.
FAIL LED
Red
Steady Red with Active and Standby LEDs off indicates either the
card is in the Reset condition, the card has failed, or the card set
is not complete (no line module).
Steady Red with Active LED on indicates the card was active
prior to failing.
Steady Red with Standby LED on indicates the card was standby
prior to failing.
AUSM/B Back Cards
The MGX-AUSM/B-8T1 and MGX-AUSM/B-8E1 use the generic 8-port T1 or E1 line modules that
operate with the 8-port service modules. The standard T1 version of the back card has eight RJ-48
connectors. The standard versions of the E1 back card have either eight RJ-48 connectors or eight pairs
of SMB connectors. The following back cards are compatible with the AUSM/B:
•
RJ48-8T1 back card for T1
•
RJ48-8E1 back card for E1
•
SMB-8E1 back card for E1
Figure 1-19 illustrates a T1 back card for an AUSM/B. Figure 1-20 illustrates the E1 back cards for the
AUSM/B with either RJ-48 or SMB connectors. All these cards will be rotated 90 degrees to the right
when they are installed in an MGX 8230 back card slot that corresponds to their mating AUSM/B.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-25
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Figure 1-19 Standard RJ-48 Back Card for the MGX-AUSM/B-8T1
RJ48-8T1
1
2
3
4
5
6
7
17945
8
T1 RJ48
Back Card
Cisco MGX 8230 Installation and Configuration
1-26
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Figure 1-20 Standard RJ-48 and SMB Back Cards for the MGX-AUSM/B-8E1
RJ48-8E1
RX1
1
TX1
RX2
2
TX2
3
4
RX3
TX3
RX4
5
TX4
6
RX5
TX5
7
RX6
8
TX6
RX7
TX7
RX8
17946
TX8
E1RJ48
Back Card
E1 SMB
Back Card
Frame Service Module Features
The Frame Relay Service Modules (FRSMs) can be used in either an MGX 8230 or an MGX 8850. The
primary function of the FRSM is to convert between the Frame Relay-formatted data and ATM/AAL5
cell-formatted data. It converts the header format and translates the address for Frame Relay
port/DLCIs, ATM-Frame UNI (FUNI) port/frame address, or frame forwarding port, and the ATM
virtual connection identifiers (VPI/VCIs).
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-27
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
For individual connections, you can configure the FRSM to perform network interworking (NIW) or
service interworking (SIW). The FRSM allows both NIW and SIW connections on the same port. You
specify NIW, SIW, FUNI, or frame forwarding when adding the connection.
All FRSMs support the following features:
•
Frame Relay-to-ATM Network Interworking (NIW) as defined in FRF.5.
•
Frame Relay-to-ATM Service Interworking (SIW) with or without translation as in FRF.8.
•
Frame forwarding.
•
ATM Frame-UNI.
•
Maximum frame sizes of 4510 bytes for Frame Relay and 4096 bytes for ATM-FUNI
•
Per-virtual-circuit (VC) queuing in the ingress direction (towards the cell bus). Traffic arriving at
the network on a connection has a dynamically assigned buffer at the entrance to the switch. Buffer
size depends on the amount of traffic and the service-level agreement (SLA).
•
Advanced buffer management. When a frame arrives, the depth of the queue for the LCN is
compared against the peak queue depth scaled down by a specified factor. The scale-down factor
depends on the amount of congestion in the free buffer pool. As the free buffer pool begins to
empty, the scale-down factor is increased, preventing an excessive number of buffers from being
held up by any single LCN.
•
Multiple priority level queuing to support class of service (CoS) in the egress direction. The FRSM
services egress queues according to a weighted priority. The priority depends on the percentage of
logical port bandwidth needed by all connections of a particular type on a logical port. The FRSM
supports:
– A high-priority queue
– A real-time Variable Bit Rate (rt-VBR) queue
– A common queue for non-real-time Variable Bit Rate (nrt-VBR) and ABR connections
– A UBR queue
•
Initial burst per channel. After a period of silence, the FRSM sends a configurable number of bytes
at a peak service rate.
•
The ForeSight option. This Cisco mechanism for managing congestion and optimizing bandwidth
continuously monitors the utilization of ATM trunks. It proactively adjusts the bandwidth for
connections to avoid queuing delays and cell discards.
•
Consolidated Link Layer Management (CLLM), an out-of-band mechanism to transport congestion
related information to the far end.
•
Dual leaky bucket policing. Within the basic parameters such as committed burst, excess burst, and
CIR, incoming frames go into two buckets: those to be checked for compliance with the committed
burst rate and those to be checked for compliance with the excess burst rate. Frames that overflow
the first bucket go into the second bucket. The buckets “leak” by a certain amount to allow for
policing without disruption or delay of service.
•
Standards-based management tools. Each FRSM supports SNMP, TFTP for configuration and
statistics collection, and a command line interface. The Cisco WAN Manager application provides
full graphical user interface support for connection management. The CiscoView application
provides equipment management.
•
MGX 8800 series network management functions, including image download, configuration
upload, statistics, telnet, UI, SNMP, trap, and MIBs.
•
OAM features: OAM F5 AIS, RDI, end-to-end or segment loopback as well as LMI and Enhanced
LMI (ANNEX A, ANNEX D, Strata LMI).
Cisco MGX 8230 Installation and Configuration
1-28
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
•
Hot-swappable redundancy (see sections for individual implementations).
•
Resource partitioning at the card level or port level for use by other controllers, such as a
Multiprotocol Label Switching (MPLS) controller.
FRSM Models
The MGX 8230 supports the following FRSM models:
•
Frame Service Module for T1 (FRSM-8T1)
The FRSM-8T1 card provides interfaces for up to eight T1 lines, each of which can support one 56
Kbps or one Nx64 Kbps FR-UNI, FR-NNI port, ATM-FUNI, or a Frame Forwarding port.
•
Frame Service Module for T1, channelized (FRSM-8T1-C)
The FRSM-8T1-C card provides interfaces for up to eight T1 lines, each of which can support up
to twenty-four 56 Kbps or Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or Frame Forwarding ports.
•
Frame Service Module for E1 (FRSM-8E1)
The FRSM-8E1 card provides interfaces for up to eight E1 lines, each of which can support one 56
Kbps or one Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or Frame Forwarding port.
•
Frame Service Module for E1, channelized (FRSM-8E1-C)
The FRSM-8E1-C card provides interfaces for up to eight E1 channelized Frame Relay lines, each
of which can support multiple (up to thirty-one) 56 Kbps or Nx64 Kbps FR-UNI, FR-NNI,
ATM-FUNI, or Frame Forwarding ports.
•
Frame Service Module for T3 and E3 (FRSM-2E3T3)
The FRSM-2E3/T3 card provides interfaces for up to two T3 or E3 Frame Relay lines, each of
which can support either two T3 lines (each at 44.736 Mbps) or two E3 lines (each at 34.368 Mbps)
FR-UNI, FR-NNI, ATM-FUNI, or Frame Forwarding ports.
•
Frame Service Module for channelized T3 (FRSM-2CT3)
The FRSM-2CT3 card supports interfaces for up to two T3 channelized Fame Relay lines, each of
which supports 56 Kbps, 64 Kbps, Nx56 Kbps, Nx64 Kbps, T1 ports for a total of 256 ports that
can be freely distributed across the two T3 lines.
•
FRSM-HS2
The FRSM-HS2 provides unchannelized Frame Relay service for up to 1000 user-connections over
two HSSI lines on the SCSI2-2HSSI back card. The maximum rate for the card is 104 Mbps. Each
port can operate in either DTE or DCE mode with incremental rates of N x T1 or N x E1 up to 52
Mbps.
Figure 1-21 illustrates the FRSM front cards as they would be oriented in a front card slot of an MGX
8230 chassis.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-29
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Figure 1-21 FRSM Front Cards
2CT3
FRSM
PORT 2
PORT 1
FAIL
ACT
STBY
FRSM-2CT3 front card
PORT 1
PORT 1
PORT 1
2T3E3
FAIL
FAIL
FAIL
FRSM
STBY
STBY
STBY
PORT 2
ACT
ACT
ACT
FRSM-2T3E3 front card
FRSM
HS2
FRSM
8T1
PORT 2
FRSM-HS2/B front card
26263
PORT 8
PORT 7
PORT 6
PORT 5
PORT 4
PORT 3
PORT 2
FRSM-8T1 front card
The Frame Service Module (FRSM) consists of an FRSM front card and an appropriate back card.
The following are the Frame Service Modules (FRSMs) and related back cards supported by the MGX
8230:
•
FRSM-2CT3 front card with the BNC-2T3 back card
•
FRSM-2T3E3 front card with either a BNC-2T3 or a BNC-2E3 back card
•
FRSM-HS2, with an SCSI2-2HSSI back card
•
FRSM-8T1/8E1 one of the following:
– RJ48-8T1-LM
– RJ48-8E1-LM
– SMB-8E1-LM
The T1 or E1 back cards look identical to the AUSM/B back cards shown in Figure 1-19 and
Figure 1-20.
Cisco MGX 8230 Installation and Configuration
1-30
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
FRSM Redundancy
In the MGX 8230, FRSMs can have 1:1 redundancy using a Y-cable. The very high speed
MGX-FRSM-2CT3, MGX-FRSM-2T3E3, and MGX-FRSM-HS2/B can use Y-cable redundancy.
For 1:1 redundancy, place the card sets in adjacent slots and connect a Y-cable for each pair of active
and standby ports. On the CLI, configure the card for redundancy by executing the addred command.
Refer to the “Service Resource Module” section on page 1-35 in this chapter for information on 1:N
redundancy using the MGX 8230 SRM capability.
Circuit Emulation Service Module 8T1E1
The main function of the Circuit Emulation Service Module (CESM), which can be used in either an
MGX 8230 IP + ATM multiservice gateway or an MGX 8250/8850 switch, is to provide a constant bit
rate (CBR) circuit emulation service by converting data streams into CBR AAL1 cells for transport
across an ATM network. The CESM supports the CES-IS specifications of the ATM Forum.
The 8-port Circuit Emulation Service Module (CESM-8T1E1) lets you configure individual physical
ports for structured or unstructured data transfer.
Structured Data Transfer
If you configure an individual port for structured data transfer, the CESM-8T1E1 supports:
•
Synchronous timing.
•
Superframe or Extended Superframe.
•
N x 64 Kbps, fractional DS1/E1 service (contiguous time slots only). You can map an N x 64 Kbps
channel to any VC.
•
CAS robbed bit for T1 (ABCD for ESF and SF frames) and CAS for E1 (channel 16). This feature
applies to only AAL1 interworking conversion.
•
CCS channel as a transparent data channel.
•
A choice of partially filled cells.
•
Idle detection and suppression for 64 Kbps CAS connections.
•
Loopback diagnostics on a line or a connection (addlnloop, tstcon, and tstdelay commands).
Unstructured Data Transfer
If you configure an individual port for unstructured data transfer, the CESM-8T1E1 supports:
•
Synchronous or asynchronous timing at T1 (1.544 Mbps) or E1 (2.048 Mbps) rates. For
asynchronous timing, you can select its basis as either SRTS or adaptive clock recovery.
•
The special port type framingOnVcDisconnect. This port type prevents a remote-end CPE from
going to LOF by placing a line in remote loopback mode when the CESM determines that a
connection deletion or suspension occurred at the network-side ATM interface.
•
Ability to detect and display a yellow alarm for the ESF framing on a T1 line.
•
Loopback diagnostics on a line or a connection (addlnloop, tstcon, and tstdelay commands).
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-31
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
CESM Models
The MGX 8230 supports two CESM models:
•
Circuit Emulation Service Module for T1 (CESM-8T1)
The CESM-8T1 card provides interfaces for up to eight T1 lines, each of which is a 1.544 Mbps
structured or unstructured synchronous data stream.
•
Circuit Emulation Service Module for E1 (CESM-8E1)
The CESM-8E1 card provides interfaces for up to eight E1 lines, each of which is a 2.048 Mbps
structured or unstructured synchronous data stream.
Figure 1-22 illustrates the two CESM front cards. In an MGX 8230 chassis, these cards would be rotated
90 degrees to the left.
The CESM-8T1E1 card set consists of the CESM-8T1E1 front card and one of the following back cards:
•
RJ48-8T1-LM
•
RJ48-8E1-LM
•
SMB-8E1-LM
The CESM E1 or T1 back cards appear the same as the AUSM/B back cards shown in Figure 1-19 and
Figure 1-20.
Cisco MGX 8230 Installation and Configuration
1-32
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Processor and Service Modules
Figure 1-22 CESM Front Cards
•••••
ACT
ACT
STBY
STBY
FAIL
FAIL
PORT 1
PORT 1
PORT 2
PORT 2
PORT 3
PORT 3
PORT 4
PORT 4
PORT 5
PORT 5
PORT 6
PORT 6
PORT 7
PORT 7
PORT 8
PORT 8
CESM
CESM
8T1
8E1
T1 Front card
E1 Front card
17689
•••••
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-33
Chapter 1
MGX 8230 Overview
Redundancy Architecture
Table 1-3 describes what the CESM LEDs mean.
Table 1-3
LED Indicators for 8-Port CESM
Type of LED
Color
Meaning
PORT LED
Green
Green indicates the port is active.
Red
Red indicates there is local alarm on the port.
Off indicates the port has not been activated (upped).
ACTIVE LED
Green
On indicates the card set is in active mode.
STANDBY LED
Yellow
Slow blink without the Active LED indicates the card
is in the boot state.
Fast blink with the Standby LED indicates the card is
being downloaded.
Fast blink indicates the service module is passing
BRAM channel information to the PXM
Steady yellow indicates the card is in Standby mode
and the firmware is executing ADMIN code.
FAIL LED
Red
Steady Red with Active and Standby LEDs off
indicates either the card is in the Reset condition, the
card has failed, or the card set is not complete (no line
module).
Steady Red with Active LED on indicates the card was
active prior to failing.
Steady Red with Standby LED on indicates the card
was standby prior to failing.
Both standby and red LED lit indicates self test failure.
Redundancy Architecture
Since the MGX 8230 chassis is a smaller form factor MGX 8850, most of the redundancy features
available in MGX 8850 are available in MGX 8230 chassis. The following is a list of available
redundancy features on the MGX 8230 chassis.
•
Dual PXM
•
Y-cable redundancy on PXM uplink ports
•
1:N redundancy for T1/E1 service modules
•
Eight cell buses per PXM
•
N+1 cooling fan redundancy
•
N+1 AC or DC power redundancy (optional)
•
1:1 Y-cable redundancy for T3/E3 interfaces
Cisco MGX 8230 Installation and Configuration
1-34
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
MGX 8230 Management
MGX 8230 Management
To control the MGX 8230, you can use the Cisco WAN Manager (formerly StrataView Plus) application
for connection management, the CiscoView application for hardware configuration, and a command
line interface for low-level control. The firmware determines the available functionality, and you can
download firmware to upgrade functionality through a TFTP application on a workstation or a PC.
The current status and configuration parameters of the MGX 8230 modules reside in an SNMP
Management Information Base (MIB). Firmware updates the MIB as changes in status and
configuration occur.
You can control most of the MGX 8230 functions through the graphical interface in the Cisco WAN
Manager application and CiscoView for the MGX 8230.
The control port (SLIP protocol only), the LAN (ethernet) port, and the in-band ATM connection
(feeder application only) all support the CLI (via telnet), TFTP, and SNMP protocols for
communicating with the MGX 8230 IP + ATM multiservice gateway or an MGX 8850/8250 switch.
Service Resource Module
This section describes the possible impact of installing a Service Resource Module-3T3
(MGX-SRM-3T3/B) on the service modules it supports. The MGX-SRM-3T3/B (or “SRM” for short)
can provide 1:N redundancy for the T1 and E1 cards as well as bulk distribution for T1 cards. It has no
communication with higher speed service modules, such as the MGX-FRSM-2CT3 and
MGX-FRSM-HS2. See Figure 1-23 for an illustration of the MGX-SRM-3T3/B front card and the
MGX-BNC-3T3-M back card.
The multifunction SRM has the following capabilities:
•
A de-multiplexing function called bulk distribution carries traffic across the distribution bus
between the T3 lines on the MGX-SRM-3T3/B and the T1 service modules. Bulk distribution can
greatly reduce the number of T1 lines coming into the enclosure.
•
1:N redundancy support for service modules with RJ-48 connectors.
•
Bit error rate testing (BERT) for T1 and subrate service module lines.
General Installation Requirements for the MGX-SRM-3T3/B
The following are card-level characteristics that apply to the SRM installation:
•
The MGX 8230 can have MGX-SRM-3T3/B cards installed in slots 7 and 14 only.
•
The distribution bus does not support slots 7 and 14, so any service module that uses bulk
distribution or relies on the distribution bus for redundancy cannot reside in these slots.
Bulk Distribution and Redundancy Support
The use of bulk distribution affects the requirements for SRM and service module back cards:
•
With bulk distribution and 1:N redundancy support by way of the distribution bus, the service
modules do not use back cards.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-35
Chapter 1
MGX 8230 Overview
Service Resource Module
•
For just 1:N redundancy by way of the redundancy bus, the supported service modules must have
back cards—including one special redundancy back card. E1 redundancy requires the R-RJ48-8E1
line module, and T1 redundancy requires the R-RJ48-8T1 line module.
For bulk distribution, the T3 lines connect to an external multiplexer. The T1 lines on the other side of
the multiplexer connect to the CPE. The SRM converts the received traffic from its T3 lines to T1
channels and sends the data to linked service modules. For instructions on linking T1 channels and card
slots to the MGX-SRM-3T3/B, see Chapter 3, “Configuring the MGX 8230.”
For bulk distribution of T1 lines, note the following about the MGX-SRM-3T3/B:
Note
•
Each T3 line can support up to 28 T1 channels.
•
The maximum number of T1 channels an MGX-SRM-3T3/B can support at one time is 80.
Upon replacing the failed card, you must switch back to normal operation because the
switch does not automatically do so.
Cisco MGX 8230 Installation and Configuration
1-36
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 1
MGX 8230 Overview
Service Resource Module
Figure 1-23 MGX-SRM-3T3/B Card Set
BNM 3T3 M
CLEI Code Label
ACT
STBY
FAIL
LIN RED
SRM
Front card
Back card
S6181
3T3
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1-37
Chapter 1
MGX 8230 Overview
Service Resource Module
Statistics and Command Line Interface
All statistics counters available in MGX 8850 are supported by the MGX 8230. There will be no change
in the command line interface from MGX 8850. See Appendix A for a listing of the supported statistics.
The Add Shelf command on IGX has been modified to support adding an MGX 8230 shelf on the UXM.
Alarm and Error Handling
The MGX 8230 provides the same alarm and error handling as SWSW Release 9.2 and MGX 8850
Release 1.1.
Cisco MGX 8230 Installation and Configuration
1-38
Release 1.0, Part Number 78-10616-01, June 2000
CH A P T E R
2
Installation
This chapter describes the physical installation of the MGX 8230. It contains two main sections:
•
Preparing for Installation
•
Installing an MGX 8230
Warning
Only trained service personnel should install the equipment.
Warning
Read the installation instructions before you connect the equipment to its power
source.
Preparing for Installation
This section includes the following subsections:
•
Safety
•
Translated Safety Warnings
•
Site Preparation
Safety
The guidelines that following help ensure your safety and protect the MGX 8230 equipment. The list
of guidelines may not address all potentially hazardous situations in your working environment, so be
alert and exercise good judgement at all times.
The safety guidelines are:
•
Keep the chassis area clear and dust-free before, during, and after installation.
•
Keep tools away from walk areas where you and others could fall over them.
•
Do not wear loose clothing or jewelry, such as ear rings, bracelets, or chains, that could get caught
in the chassis.
•
Wear safety glasses if your are working under any conditions that may be hazardous to your eyes.
•
Do not perform any actions that creates a potential hazard to people or makes the equipment unsafe.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-1
Chapter 2
Installation
Preparing for Installation
•
A fully loaded MGX 8230 can weigh 150 lbs; never attempt to lift an object that is too heavy for
one person to handle.
Maintaining Safety with Electricity
Before working on a chassis or working near power supplies, unplug the power cord on an AC powered
system. On a DC-powered system, disconnect the power at the circuit breakers.
Follow these guidelines when working on equipment powered by electricity:
•
Locate the emergency power-off switch for the room in which you are working, then, if an electrical
accident occurs, you can act quickly to turn off the power.
•
Do not work alone if potentially hazardous conditions exist anywhere in your work space.
•
Never assume that power is disconnected from a circuit; always check the circuit.
•
Look carefully for possible hazards in your work area, such as moist floors, ungrounded power
extension cables, frayed power cords and missing safety grounds.
•
If an electrical accident occurs, proceed as follows:
– Use caution; do not become a victim yourself.
– Disconnect power from the system.
– If possible, send another person to get medical help. Otherwise, assess the condition of the
victim and then call for help.
•
Use the MGX 8230 AC or MGX 8230 DC systems within their marked electrical ratings and
product usage instructions.
•
Install the MGX 8230 AC or MGX 8230 DC systems in accordance with the following local and
national electrical codes:
– United States—National Fire Protection Association (NFPA70), United States National
Electrical Code.
– Canada—Canadian Electrical Code, Part I, CSA C22.1.
– Other countries—International Electrotechnical Commission (IEC) 364, Part 1 through Part 7.
•
MGX 8230 AC models are shipped with a 3-wire electrical cord with grounding-type plug that fits
only a grounding-type power outlet. This is a safety feature that you should not circumvent.
Equipment grounding should comply with local and national electrical codes.
•
MGX 8230 DC models are equipped with DC power entry modules (PEMs) and require you to
terminate the DC input wiring on a DC source capable of supplying at least 30 Amps. A 30-Amp
circuit breaker is required at the - 48 VDC facility power source. An easily accessible disconnect
device should be incorporated into the facility wiring. Be sure to connect the grounding wire
conduit to a solid earth ground. A close loop ring is recommended to terminate the ground
conductor at the ground stud.
•
Other DC power guidelines are:
– Only a DC power source that complies with the safety extra low voltage (SELV) requirements
of UL1950, CSA C22.2 No.950-95, EN 60950 and IEC 950 can be connected to an MGX 8230
DC-input power entry and module.
– MGX 8230 DC models which are equipped with DC power entry modules are only intended
for installation in a restricted access location. In the United States, a restricted access location
is in accordance with Articles 110-16, 110-17, and 110-18 of the national Electrical Code
ANSI/NFPA 70.
Cisco MGX 8230 Installation and Configuration
2-2
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Preparing for Installation
Warnings and Cautions
This section provides regulatory compliance and safety information for the MGX 8230 AC and DC
models.
Warning
Only trained service personnel should install the equipment.
Warning
Read the installation instructions before you connect the equipment to its power
source.
The MGX 8230 AC- and DC-powered systems are intended for installation in a RESTRICTED
ACCESS LOCATION.
Translated Safety Warnings
Warning Definition
Warning
Waarschuwing
Varoitus
Means danger. You are in a situation that could cause bodily injury. Before you work
on any equipment, be aware of the hazards involved with electrical circuitry and be
familiar with standard practices for preventing accidents.
Dit waarschuwingssymbool betekent gevaar. U verkeert in een situatie die lichamelijk
letsel kan veroorzaken. Voordat u aan enige apparatuur gaat werken, dient u zich
bewust te zijn van de bij elektrische schakelingen betrokken risico's en dient u op de
hoogte te zijn van standaard maatregelen om ongelukken te voorkomen.
Tämä varoitusmerkki merkitsee vaaraa. Olet tilanteessa, joka voi johtaa
ruumiinvammaan. Ennen kuin työskentelet minkään laitteiston parissa, ota selvää
sähkökytkentöihin liittyvistä vaaroista ja tavanomaisista onnettomuuksien
ehkäisykeinoista.
Attention
Ce symbole d'avertissement indique un danger. Vous vous trouvez dans une situation
pouvant causer des blessures ou des dommages corporels. Avant de travailler sur un
équipement, soyez conscient des dangers posés par les circuits électriques et
familiarisez-vous avec les procédures couramment utilisées pour éviter les accidents.
Warnung
Dieses Warnsymbol bedeutet Gefahr. Sie befinden sich in einer Situation, die zu einer
Körperverletzung führen könnte. Bevor Sie mit der Arbeit an irgendeinem Gerät
beginnen, seien Sie sich der mit elektrischen Stromkreisen verbundenen Gefahren
und der Standardpraktiken zur Vermeidung von Unfällen bewußt.
Avvertenza
Questo simbolo di avvertenza indica un pericolo. La situazione potrebbe causare
infortuni alle persone. Prima di lavorare su qualsiasi apparecchiatura, occorre
conoscere i pericoli relativi ai circuiti elettrici ed essere al corrente delle pratiche
standard per la prevenzione di incidenti.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-3
Chapter 2
Installation
Preparing for Installation
Advarsel
Dette varselsymbolet betyr fare. Du befinner deg i en situasjon som kan føre til
personskade. Før du utfører arbeid på utstyr, må du vare oppmerksom på de
faremomentene som elektriske kretser innebærer, samt gjøre deg kjent med vanlig
praksis når det gjelder å unngå ulykker.
Aviso
Este símbolo de aviso indica perigo. Encontra-se numa situação que lhe poderá causar
danos físicos. Antes de começar a trabalhar com qualquer equipamento,
familiarize-se com os perigos relacionados com circuitos eléctricos, e com quaisquer
práticas comuns que possam prevenir possíveis acidentes.
¡Atención!
Este símbolo de aviso significa peligro. Existe riesgo para su integridad física. Antes
de manipular cualquier equipo, considerar los riesgos que entraña la corriente
eléctrica y familiarizarse con los procedimientos estándar de prevención de
accidentes.
Varning!
Denna varningssymbol signalerar fara. Du befinner dig i en situation som kan leda till
personskada. Innan du utför arbete på någon utrustning måste du vara medveten om
farorna med elkretsar och känna till vanligt förfarande för att förebygga skador.
Product Disposal Warning
Warning
Ultimate disposal of this product should be handled according to all national laws and
regulations.
Waarschuwing
Dit produkt dient volgens alle landelijke wetten en voorschriften te worden afgedankt.
Varoitus
Tämän tuotteen lopullisesta hävittämisestä tulee huolehtia kaikkia valtakunnallisia
lakeja ja säännöksiä noudattaen.
Attention
La mise au rebut définitive de ce produit doit être effectuée conformément à toutes les
lois et réglementations en vigueur.
Warnung
Dieses Produkt muß den geltenden Gesetzen und Vorschriften entsprechend entsorgt
werden.
Avvertenza
L'eliminazione finale di questo prodotto deve essere eseguita osservando le normative
italiane vigenti in materia.
Advarsel
Aviso
Endelig disponering av dette produktet må skje i henhold til nasjonale lover og
forskrifter.
A descartagem final deste produto deverá ser efectuada de acordo com os
regulamentos e a legislação nacional.
Cisco MGX 8230 Installation and Configuration
2-4
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Preparing for Installation
¡Advertencia!
Varning!
El desecho final de este producto debe realizarse según todas las leyes y regulaciones
nacionales.
Slutlig kassering av denna produkt bör skötas i enlighet med landets alla lagar och
föreskrifter.
Lightning Activity Warning
Warning
Do not work on the system or connect or disconnect cables during periods of lightning
activity.
Waarschuwing
Tijdens onweer dat gepaard gaat met bliksem, dient u niet aan het systeem te werken
of kabels aan te sluiten of te ontkoppelen.
Varoitus
Älä työskentele järjestelmän parissa äläkä yhdistä tai irrota kaapeleita ukkosilmalla.
Attention
Ne pas travailler sur le système ni brancher ou débrancher les câbles pendant un
orage.
Warnung
Arbeiten Sie nicht am System und schließen Sie keine Kabel an bzw. trennen Sie keine
ab, wenn es gewittert.
Avvertenza
Advarsel
Aviso
Non lavorare sul sistema o collegare oppure scollegare i cavi durante un temporale
con fulmini.
Utfør aldri arbeid på systemet, eller koble kabler til eller fra systemet når det tordner
eller lyner.
Não trabalhe no sistema ou ligue e desligue cabos durante períodos de mau tempo
(trovoada).
¡Advertencia!
No operar el sistema ni conectar o desconectar cables durante el transcurso de
descargas eléctricas en la atmósfera.
Varning!
Vid åska skall du aldrig utföra arbete på systemet eller ansluta eller koppla loss
kablar.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-5
Chapter 2
Installation
Preparing for Installation
Jewelry Removal Warning
Warning
Before working on equipment that is connected to power lines, remove jewelry
(including rings, necklaces, and watches). Metal objects will heat up when connected
to power and ground and can cause serious burns or weld the metal object to the
terminals.
Waarschuwing
Alvorens aan apparatuur te werken die met elektrische leidingen is verbonden,
sieraden (inclusief ringen, kettingen en horloges) verwijderen. Metalen voorwerpen
worden warm wanneer ze met stroom en aarde zijn verbonden, en kunnen ernstige
brandwonden veroorzaken of het metalen voorwerp aan de aansluitklemmen lassen.
Varoitus
Ennen kuin työskentelet voimavirtajohtoihin kytkettyjen laitteiden parissa, ota pois
kaikki korut (sormukset, kaulakorut ja kellot mukaan lukien). Metalliesineet
kuumenevat, kun ne ovat yhteydessä sähkövirran ja maan kanssa, ja ne voivat
aiheuttaa vakavia palovammoja tai hitsata metalliesineet kiinni liitäntänapoihin.
Attention
Avant d’accéder à cet équipement connecté aux lignes électriques, ôter tout bijou
(anneaux, colliers et montres compris). Lorsqu’ils sont branchés à l’alimentation et
reliés à la terre, les objets métalliques chauffent, ce qui peut provoquer des blessures
graves ou souder l’objet métallique aux bornes.
Warnung
Vor der Arbeit an Geräten, die an das Netz angeschlossen sind, jeglichen Schmuck
(einschließlich Ringe, Ketten und Uhren) abnehmen. Metallgegenstände erhitzen sich,
wenn sie an das Netz und die Erde angeschlossen werden, und können schwere
Verbrennungen verursachen oder an die Anschlußklemmen angeschweißt werden.
Avvertenza
Prima di intervenire su apparecchiature collegate alle linee di alimentazione,
togliersi qualsiasi monile (inclusi anelli, collane, braccialetti ed orologi). Gli oggetti
metallici si riscaldano quando sono collegati tra punti di alimentazione e massa:
possono causare ustioni gravi oppure il metallo può saldarsi ai terminali.
Advarsel
Fjern alle smykker (inkludert ringer, halskjeder og klokker) før du skal arbeide på
utstyr som er koblet til kraftledninger. Metallgjenstander som er koblet til
kraftledninger og jord blir svært varme og kan forårsake alvorlige brannskader eller
smelte fast til polene.
Aviso
Antes de trabalhar em equipamento que esteja ligado a linhas de corrente, retire todas
as jóias que estiver a usar (incluindo anéis, fios e relógios). Os objectos metálicos
aquecerão em contacto com a corrente e em contacto com a ligação à terra, podendo
causar queimaduras graves ou ficarem soldados aos terminais.
Cisco MGX 8230 Installation and Configuration
2-6
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Preparing for Installation
¡Advertencia!
Antes de operar sobre equipos conectados a líneas de alimentación, quitarse las joyas
(incluidos anillos, collares y relojes). Los objetos de metal se calientan cuando se
conectan a la alimentación y a tierra, lo que puede ocasionar quemaduras graves o
que los objetos metálicos queden soldados a los bornes.
Varning!
Tag av alla smycken (inklusive ringar, halsband och armbandsur) innan du arbetar på
utrustning som är kopplad till kraftledningar. Metallobjekt hettas upp när de kopplas
ihop med ström och jord och kan förorsaka allvarliga brännskador; metallobjekt kan
också sammansvetsas med kontakterna.
Power Supply Warning
Warning
Do not touch the power supply when the power cord is connected. For systems with a
power switch, line voltages are present within the power supply even when the power
switch is off and the power cord is connected. For systems without a power switch,
line voltages are present within the power supply when the power cord is connected.
Waarschuwing
U dient de voeding niet aan te raken zolang het netsnoer aangesloten is. Bij systemen
met een stroomschakelaar zijn er lijnspanningen aanwezig in de voeding, zelfs
wanneer de stroomschakelaar uitgeschakeld is en het netsnoer aangesloten is. Bij
systemen zonder een stroomschakelaar zijn er lijnspanningen aanwezig in de voeding
wanneer het netsnoer aangesloten is.
Varoitus
Älä kosketa virtalähdettä virtajohdon ollessa kytkettynä. Virrankatkaisimella
varustetuissa järjestelmissä on virtalähteen sisällä jäljellä verkkojännite, vaikka
virrankatkaisin on katkaistu-asennossa virtajohdon ollessa kytkettynä.
Järjestelmissä, joissa ei ole virrankatkaisinta, on virtalähteen sisällä verkkojännite,
kun virtajohto on kytkettynä.
Attention
Ne pas toucher le bloc d'alimentation quand le cordon d'alimentation est branché.
Avec les systèmes munis d'un commutateur marche-arrêt, des tensions de ligne sont
présentes dans l'alimentation quand le cordon est branché, même si le commutateur
est à l'arrêt. Avec les systèmes sans commutateur marche-arrêt, l'alimentation est
sous tension quand le cordon d'alimentation est branché.
Warnung
Berühren Sie das Netzgerät nicht, wenn das Netzkabel angeschlossen ist. Bei
Systemen mit Netzschalter liegen Leitungsspannungen im Netzgerät vor, wenn das
Netzkabel angeschlossen ist, auch wenn das System ausgeschaltet ist. Bei Systemen
ohne Netzschalter liegen Leitungsspannungen im Netzgerät vor, wenn das Netzkabel
angeschlossen ist.
Avvertenza
Non toccare l’alimentatore se il cavo dell’alimentazione è collegato. Per i sistemi con
un interruttore di alimentazione, tensioni di linea sono presenti all’interno
dell’alimentatore anche quando l’interruttore di alimentazione è en posizione di
disattivazione (off), se il cavo dell’alimentazione è collegato. Per i sistemi senza un
interruttore, tensioni di linea sono presenti all’interno dell’alimentatore quando il
cavo di alimentazione è collegato.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-7
Chapter 2
Installation
Preparing for Installation
Advarsel
Berør ikke strømforsyningsenheten når strømledningen er tilkoblet. I systemer som har
en strømbryter, er det spenning i strømforsyningsenheten selv om strømbryteren er
slått av og strømledningen er tilkoblet. Når det gjelder systemer uten en strømbryter,
er det spenning i strømforsyningsenheten når strømledingen er tilkoblet.
Aviso
Não toque na unidade abastecedora de energia quando o cabo de alimentação estiver
ligado. Em sistemas com interruptor, a corrente eléctrica estará presente na unidade
abastecedora, sempre que o cabo de alimentação de energia estiver ligado, mesmo
quando o interruptor se encontrar desligado. Para sistemas sem interruptor, a tensão
eléctrica dentro da unidade abastecedora só estará presente quando o cabo de
alimentação estiver ligado.
¡Advertencia!
No tocar la fuente de alimentación mientras el cable esté enchufado. En sistemas con
interruptor de alimentación, hay voltajes de línea dentro de la fuente, incluso cuando
el interruptor esté en Apagado (OFF) y el cable de alimentación enchufado. En
sistemas sin interruptor de alimentación, hay voltajes de línea en la fuente cuando el
cable está enchufado.
Varning!
Vidrör inte strömförsörjningsenheten när nätsladden är ansluten. För system med
strömbrytare finns det nätspänning i strömförsörjningsenheten även när strömmen har
slagits av men nätsladden är ansluten. För system utan strömbrytare finns det
nätspänning i strömförsörjningsenheten när nätsladden är ansluten.
Power Supply Disconnection Warning
Warning
Before working on a chassis or working near power supplies, unplug the power cord
on AC units; disconnect the power at the circuit breaker on DC units.
Waarschuwing
Voordat u aan een frame of in de nabijheid van voedingen werkt, dient u bij
wisselstroom toestellen de stekker van het netsnoer uit het stopcontact te halen; voor
gelijkstroom toestellen dient u de stroom uit te schakelen bij de stroomverbreker.
Varoitus
Kytke irti vaihtovirtalaitteiden virtajohto ja katkaise tasavirtalaitteiden virta
suojakytkimellä, ennen kuin teet mitään asennuspohjalle tai työskentelet
virtalähteiden läheisyydessä.
Attention
Avant de travailler sur un châssis ou à proximité d'une alimentation électrique,
débrancher le cordon d'alimentation des unités en courant alternatif ; couper
l'alimentation des unités en courant continu au niveau du disjoncteur.
Warnung
Bevor Sie an einem Chassis oder in der Nähe von Netzgeräten arbeiten, ziehen Sie bei
Wechselstromeinheiten das Netzkabel ab bzw. schalten Sie bei Gleichstromeinheiten
den Strom am Unterbrecher ab.
Avvertenza
Prima di lavorare su un telaio o intorno ad alimentatori, scollegare il cavo di
alimentazione sulle unità CA; scollegare l'alimentazione all’interruttore automatico
sulle unità CC.
Cisco MGX 8230 Installation and Configuration
2-8
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Preparing for Installation
Advarsel
Før det utføres arbeid på kabinettet eller det arbeides i nærheten av
str¿mforsyningsenheter, skal str¿mledningen trekkes ut pŒ vekselstrømsenheter og
strømmen kobles fra ved strømbryteren på likestrømsenheter.
Aviso
Antes de trabalhar num chassis, ou antes de trabalhar perto de unidades de
fornecimento de energia, desligue o cabo de alimentação nas unidades de corrente
alternada; desligue a corrente no disjuntor nas unidades de corrente contínua.
¡Advertencia!
Antes de manipular el chasis de un equipo o trabajar cerca de una fuente de
alimentación, desenchufar el cable de alimentación en los equipos de corriente
alterna (CA); cortar la alimentación desde el interruptor automático en los equipos de
corriente continua (CC).
Varning!
Innan du arbetar med ett chassi eller nära strömförsörjningsenheter skall du
för växelströmsenheter dra ur nätsladden och för likströmsenheter bryta
strömmen vid överspänningsskyddet.
Power Disconnection Warning
Warning
Before working on a system that has an On/Off switch, turn OFF the power and unplug
the power cord.
Waarschuwing
Voordat u aan een systeem werkt dat een aan/uit schakelaar heeft, dient u de
stroomvoorziening UIT te schakelen en de stekker van het netsnoer uit het stopcontact
te halen.
Varoitus
Ennen kuin teet mitään sellaiselle järjestelmälle, jossa on kaksiasentokytkin,
katkaise siitä virta ja kytke virtajohto irti.
Attention
Avant de travailler sur un système équipé d'un commutateur marche-arrêt, mettre
l'appareil à l'arrêt (OFF) et débrancher le cordon d'alimentation.
Warnung
Bevor Sie an einem System mit Ein/Aus-Schalter arbeiten, schalten Sie das System
AUS und ziehen das Netzkabel aus der Steckdose.
Avvertenza
Prima di lavorare su un sistema dotato di un interruttore on/off, spegnere (OFF) il
sistema e staccare il cavo dell’alimentazione.
Advarsel
Slå AV strømmen og trekk ut strømledningen før det utføres arbeid på et system som er
utstyrt med en av/på-bryter.
Aviso
Antes de começar a trabalhar num sistema que tem um interruptor on/off, DESLIGUE a
corrente eléctrica e retire o cabo de alimentação da tomada.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-9
Chapter 2
Installation
Preparing for Installation
¡Advertencia!
Varning!
Antes de utilizar cualquier sistema equipado con interruptor de Encendido/Apagado
(ON/OFF), cortar la alimentación y desenchufar el cable de alimentación.
Slå AV strömmen och dra ur nätsladden innan du utför arbete på ett system med
strömbrytare.
Grounded Equipment Warning
Warning
Waarschuwing
Varoitus
This equipment is intended to be grounded. Ensure that the host is connected to earth
ground during normal use.
Deze apparatuur hoort geaard te worden Zorg dat de host-computer tijdens normaal
gebruik met aarde is verbonden.
Tämä laitteisto on tarkoitettu maadoitettavaksi. Varmista, että isäntälaite on
yhdistetty maahan normaalikäytön aikana.
Attention
Cet équipement doit être relié à la terre. S’assurer que l’appareil hôte est relié à la
terre lors de l’utilisation normale.
Warnung
Dieses Gerät muß geerdet werden. Stellen Sie sicher, daß das Host-Gerät während
des normalen Betriebs an Erde gelegt ist.
Avvertenza
Questa apparecchiatura deve essere collegata a massa. Accertarsi che il dispositivo
host sia collegato alla massa di terra durante il normale utilizzo.
Advarsel
Dette utstyret skal jordes. Forviss deg om vertsterminalen er jordet ved normalt bruk.
Aviso
Este equipamento deverá estar ligado à terra. Certifique-se que o host se encontra
ligado à terra durante a sua utilização normal.
¡Advertencia!
Este equipo debe conectarse a tierra. Asegurarse de que el equipo principal esté
conectado a tierra durante el uso normal.
Varning!
Denna utrustning är avsedd att jordas. Se till att värdenheten är jordad vid normal
användning.
Installation Warning
Warning
Waarschuwing
Read the installation instructions before you connect the system to its power source.
Raadpleeg de installatie-aanwijzingen voordat u het systeem met de voeding verbindt.
Cisco MGX 8230 Installation and Configuration
2-10
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Preparing for Installation
Varoitus
Lue asennusohjeet ennen järjestelmän yhdistämistä virtalähteeseen.
Attention
Avant de brancher le système sur la source d'alimentation, consulter les directives
d'installation.
Warnung
Lesen Sie die Installationsanweisungen, bevor Sie das System an die Stromquelle
anschließen.
Avvertenza
Advarsel
Aviso
¡ Atención!
Varning!
Consultare le istruzioni di installazione prima di collegare il sistema all’alimentatore.
Les installasjonsinstruksjonene før systemet kobles til strømkilden.
Leia as instruções de instalação antes de ligar o sistema à sua fonte de energia.
Ver las instrucciones de instalación antes de conectar el sistema a la red de
alimentación.
Läs installationsanvisningarna innan du kopplar systemet till dess
strömförsörjningsenhet.
Class 1 Laser Product Warning
Warning
Waarschuwing
Varoitus
Class 1 laser product.
Klasse-1 laser produkt.
Luokan 1 lasertuote.
Attention
Produit laser de classe 1.
Warnung
Laserprodukt der Klasse 1.
Avvertenza
Prodotto laser di Classe 1.
Advarsel
Laserprodukt av klasse 1.
Aviso
Produto laser de classe 1.
¡Advertencia!
Varning!
Producto láser Clase I.
Laserprodukt av klass 1.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-11
Chapter 2
Installation
Preparing for Installation
Site Preparation
This section describes the steps to take and the considerations you should keep in mind prior to
installing an MGX 8230 chassis in a rack. It also contains information that applies to an MGX 8230
installation in a Cisco closed rack. If the MGX 8230 arrives in a Cisco closed rack, your initial concerns
would be the cabinet grounding, and power connections. For specifications on the enclosure and power
system, see the Appendix A, “Technical Specifications.”
This section includes:
•
Parts Checklist
•
Card Slot Locations
•
Site Requirements
•
Seismic Considerations
•
Power and Grounding
•
AC Power Circuit Breakers
•
DC Power Circuit Breakers
•
Electrical Power for AC Units
•
Electrical Power for a DC-Powered MGX 8230
•
Bonding and Grounding
•
Telecommunications Requirements
Parts Checklist
Before proceeding with the installation, verify that all the ordered parts are present and in good
condition. Store a record of the parts and serial numbers. If any parts are missing or damaged, contact
your sales representative.
Card Slot Locations
Slots are 1 and 2 are always double-height slots and reserved for the primary and redundant MGX 8230
Processor Switch Modules (PXMs). Slots 3 through 6 (and 3 through 6 and 13 through 14 for
single-height modules) are used for various service modules. Each service module slot can accept one
single-height card or be converted to accept two double-height cards. Slots 7 and 14 are reserved for
SRM only.
If you are considering any future card changes in which you replace a single-height card with a
double-height card, place the single-height replacement candidates in as low of a slot number as
possible, that is start with slot 3. Remember when you are converting single-height slots into
double-height slots, you must start from the bottom. For example, before you can convert slot 4 into a
double-height slot, you must first have converted slot 3.
Cisco MGX 8230 Installation and Configuration
2-12
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Preparing for Installation
Site Requirements
The site must satisfy the requirements in the following categories:
•
Space
The MGX 8230 IP + ATM multiservice gateway is typically co-located in a rack with either an
MGX switch or a BPX switch.
Refer to the Cisco BPX 8600 Series Installation and Configuration documents for information
about rack and cabinet mounted switches.
•
Environment
The operating environment should be as follows:
Temperature and humidity range: 0° to 40°C (32° to 104°F) for normal operation, 50°C for up to
72 hours. Recommend range of 20° to 30°C. Up to 85% relative humidity, non-condensing.
•
Shock
– Operating: 10 g shock, three pulses in the positive and negative directions, all axes, 1/2 sine
wave, 11 ms duration.
– Non-operating: 20 g shock, three pulses in the positive and negative directions, all axes,
1/2 sine wave, 11 ms duration.
•
Vibration
– Operating: 5 Hz to 2 kHz at .75 g peak, limited to 0.25-inch double amplitude, sine wave,
1 octave/minute, two sweeps.
– Non-operating: 5 Hz to 500 Hz at 1.0 g peak, limited to 0.50-inch double amplitude, sine wave,
1 octave/minute, two sweeps.
•
Power
For AC power use, an AC power source must be available within 6 feet (1.8 m) of the MGX 8230.
For systems using a DC source, Cisco does not supply the DC power cord, so the user or installer
determines the wire length and the distance to the DC source. The wire should be 10 AWG (4 square
millimeters).
•
Heat Dissipation
A fully loaded, AC-powered MGX 8230 dissipates up to 4,800 BTUs (1.4 KW hour).
A DC-powered MGX 8230 dissipates up to 4,100 BTUs.
•
Weight
A fully loaded, DC-powered MGX 8230 can weigh up to 120 lbs (54.3 Kgs). A fully loaded
AC-powered MGX 8230 can weigh up to 150 lbs (68.03 Kgs).
Caution
If you move a Cisco-supplied cabinet, do not push it at its sides. Push at the front or back.
•
Flooring
Raised flooring with sufficient under-floor space for external cabling is best.
•
Mounting
The location of the IGX or BPX switch, which has a co-located MGX 8230 IP + ATM multiservice
gateway, should accommodate the routing of the data cables and the termination of the telephone
company’s or common carrier’s circuits.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-13
Chapter 2
Installation
Preparing for Installation
•
Electrostatic Discharge
The building should provide adequate grounding to prevent damage from electrostatic discharge.
See the sections “Bonding and Grounding” in the IGX or BPX installation documents for specific
details.
In addition, the MGX 8230 comes with a wrist strap that you can connect to the rear of the chassis
near the ground lug or to a convenient point on the front of the chassis. You should put on a wrist
strap before handling any cards.
Seismic Considerations
In Cisco-supplied cabinets, a feature is available for seismic anchoring. Holes exist in the upper and
lower corners for 3/8" or 1/2" bolts. Also, an optional stability plate can be purchased with the Cisco
cabinet. The stability plate is bolted to the floor, then the Cisco cabinet is bolted to the stability plate.
The “Seismic” section in the IGX or BPX installation documents contains instructions for installing the
seismic stability plate.
Power and Grounding
This section lists the requirements that relate to electrical power and grounding. These requirements
cover installations at Central Office (CO) and Private Enterprise locations.
AC Power Circuit Breakers
For an AC-powered MGX 8230, verify that the shelf ’s power comes from dedicated AC branch circuits.
The circuits must be protected by a dedicated, 15 Amp minimum circuit breaker. Cisco Systems
recommends that the site have a 15 Amp AC circuit breaker for 120 VAC outlet and 20 Amp AC circuit
breaker for 220 VAC with a long trip-delay at each branch circuit.
DC Power Circuit Breakers
For a DC-powered MGX 8230, verify that its power comes from a dedicated DC branch circuit. This
branch circuit must be protected by a dedicated circuit breaker. Cisco Systems recommends the site
have a dedicated 30 Amp circuit breaker with a medium trip delay at each branch circuit.
A DC-powered MGX 8230 uses a single pole 30 Amp circuit breaker with a short trip delay on each
–48V input. The circuit breaker manufacturer is ETA. The part number is ETA
8340-F110-PIKI-A2H030A.
Electrical Power for AC Units
The MGX 8230 AC power requirement is a voltage range of 100 to 120 or 200 to 240 VAC. A worst-case
90 VAC is allowed. Refer to Appendix A, “Technical Specifications.” An AC power source must be
available within 6 feet (1.8 m) of the system and easily accessible. Before turning on the power, verify
that each power source to the MGX 8230 comes from a dedicated branch circuit.
The power receptacles to which the node connects must be of the grounding type. The grounding
conductors that connect to the receptacles should connect to protective earth at the service equipment.
Cisco can provide AC power cords with the following plugs:
•
20 A NEMA Lb-20P, twist lock plug (domestic U.S.)
Cisco MGX 8230 Installation and Configuration
2-14
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Preparing for Installation
•
13 A 250 Vac BS1363, 3-prong fused plug (UK, Ireland)
•
CEE 7/7 (Continental Europe)
•
AS3112 (Australia/New Zealand)
•
CEI23-16/VII (Italy)
•
NEMA5-15P 125V/15 A 3-prong plug, grounding type (North America)
Electrical Power for a DC-Powered MGX 8230
Only a - 48 VDC supply that complies with the Safety Extra Low Voltage (SELV) requirements of EN
60950 can connect to the DC input.
For DC supply connections, consult local or national codes for conductor sizing. Conductors must be
suitable for 30 Amps. Wiring that is 10 AWG (4 square millimeters) is adequate.
Bonding and Grounding
To maintain the full EMI and EMC integrity of this equipment, it must be bonded to an integrated
ground plane or an isolated ground plane network. The purpose of this requirement is to mitigate the
damaging effects to equipment from electrostatic discharge and lightning. Refer to the latest edition of
ITU Recommendation K.27 or Bellcore GR-1089-CORE requirements to ensure that the correct
bonding and grounding procedures are followed. As recommended in these documents, a frame bonding
connection is provided on the Cisco-supplied cabinet for rack-mounted systems.
Refer to the section “Making the Frame Bonding (Ground) Connection” in the IGX or the BPX
installation documents for information on how to make a connection.
Note
Except for the AC power supply module, every module in a rack-mount system relies on
the rack itself for grounding. Therefore, the rack must be properly connected to protective
earth before operating the system.
A DC-powered node must have grounding conductors that connect at two separate locations, as follows:
•
The grounding conductor provided with the supply source must connect to the correct terminal of
the Power Entry Module (PEM).
•
A grounding conductor as described previously must connect to the appropriate terminal of a rack
assembly or to the grounding point on the lower-right corner of the MGX 8230 chassis rear panel.
Telecommunications Requirements
The following telecommunications requirements may be relevant to a private network connected to the
public switched networks in some international service areas: you must attach cables so that their
securing bolts are tightened to the degree that removing the cable requires a tool.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-15
Chapter 2
Installation
Installing an MGX 8230
Installing an MGX 8230
This section includes the following subsections:
•
Installing Processor and Service Modules
•
Rack Mounting the MGX 8230
•
Connecting Power for DC Systems
•
Connecting Power for AC Systems
•
Powering up the MGX 8230
Installing Processor and Service Modules
The MGX 8230 is shipped from the factory with all cards and modules tested and installed. During
initial installation, however, you may have to remove some of the service modules, the AC Power
Supply Modules, or the Fan Tray Assembly to be able to more easily maneuver the MGX 8230 chassis
into place. Cisco recommends not removing the PXMs. Before removing any modules or assemblies,
Cisco suggests that you carefully note and write down their location or slot number in the chassis.
Using the Electrostatic Wrist Strap
The MGX 8230 IP + ATM multiservice gateway ships with a wrist strap for grounding the user and
protecting the electronic components from electrostatic shock. The wrist strap kit consists of a strap, a
coiled cord, and a clip for holding the strap.
The wrist strap can be connected to the MGX 8230 chassis on the lower rear corner near the grounding
lug, or to a convenient place on the front panel.
Caution
To prevent damage to the cards from static electricity, put on a wrist strap and connect it
to any convenient metal contact on the MGX 8230 IP + ATM multiservice gateway before
you touch any cards.
Caution
Do not drop or bump the PXM. Handle the PXM front card very carefully because it
contains an attached disk drive.
Caution
Inserting the cards in the correct slot is important for all cards but especially for the back
cards because of the potential for electrical damage. If you insert a service module back
card into a MGX 8230 PXM back card slot (1 or 2), damage to the card and backplane can
result. Never remove or insert either card in a PXM/SONET back card set with the power
on.
If you accidentally try to insert a service module back card into slots 1 or 2, then observe
incorrect MGX 8230 IP + ATM multiservice gateway operation, check for bent or
damaged pins on the backplane and the back card.
Cisco MGX 8230 Installation and Configuration
2-16
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Installing an MGX 8230
Note
Both the front card and the back card of all card sets in the shelf must be present for proper
operation of the MGX 8230.
If a back card is removed and reseated or changed for another back card, the associated
front card must be reset.
Removing and Installing the Front Cards
MGX 8230 front (and back) cards are horizontally mounted. When seated, MGX 8230 front cards are
retained by a mechanical latch attached to the card. The top of a front card corresponds to the left side
of the MGX 8230 card cage as seen from the front, as shown in Figure 2-1.
Caution
Before removing a PXM from an operational system, execute the syncdisk and shutdisk
commands.
Caution
If you allow a front card to droop when you are inserting it in a card slot, you could damage
components on the bottom of the card when you slide it in or out. When inserting or
extracting an MGX 8230 front card, make sure that you support the faceplate to keep the
card level until it is completely inserted or extracted from the chassis.
Left side or
top of card
26267
Front Card Insertion/Extractor Lever
•••••
Figure 2-1
Slot
To remove a front card:
Step 1
Insert a the small flat head screwdriver provided into the slot in the insertion/extractor lever and press
until the latch springs open, approximately 10°. (There are two levers, on the left and right side, or top
and bottom, on double-height cards.) Pull/rotate the insertion/extractor lever to disconnect the card
from the backplane.
Step 2
Gently pull the card out of the card cage keeping it level through full extraction.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-17
Chapter 2
Installation
Installing an MGX 8230
Caution
To prevent damaging components on the bottom side of the card, make sure that you
support the face plate and that the card remains level while you are pulling it out of the
chassis.
To install a front card:
Step 1
Be sure the extractor is in the unlatch position.
Step 2
Position the rear card guides over the appropriate slot at the left (top) and right (bottom) of the card
cage.
Step 3
Gently slide the card all the way into the slot and then press/rotate the insertion/extractor lever (or both
levers on double-height cards) until it (or they) snaps into the vertical position.
Caution
Note
To prevent damaging components on the bottom side of the card, make sure that you
support the face plate and the card remains level while you are sliding it into the chassis.
The card should slide in and out with only slight friction on the adjacent board’s EMI
gaskets. Do not use force. Investigate any binding.
Removing and Installing the Back Cards
Back cards are retained with two captive screws: one at the top of the faceplate and one at the bottom
of the faceplate.
To remove a back card:
Step 1
Label and remove any cables connected to the back card.
Step 2
Use the screwdriver provided (flat or phillips as applicable) to undo the two retaining screws in the back
card’s faceplate.
Step 3
Pull both of the two extractor levers out to the horizontal position, this will start the removal of the card.
Gently pull the card out of the card cage.
To install a back card:
Step 1
Ensure the two extractor levers are rotated to the “in” position. When the card is being inserted into the
slot, the levers should be horizontal along the line of the back card.
Step 2
Position the rear card edges over the appropriate guides at the left and right sides of the MGX 8230 card
cage.
Step 3
Gently slide the card all the way into the slot and push to seat the card.
Step 4
Alternately tighten the two captive screws on the back card’s faceplate.
Cisco MGX 8230 Installation and Configuration
2-18
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Installing an MGX 8230
Tighten the right and left captive screws in increments to prevent misalignment of the card. Do not
overtighten the screws, but secure the card.
Warning
Cards must be inserted in the correct slot positions. This is particularly true with back
cards. If service module back cards are inserted into slots intended only for MGX 8230
PXM back cards, slots 1 and 2, damage can be done.
If you accidentally attempt to insert a service module back card into slots 1 and 2 and
have difficulty in operating the shelf, examine the backplane pins and the back card
connector to see if they have been bent or damaged.
Rack Mounting the MGX 8230
The MGX 8230 is shipped with all the ordered modules installed and tested at the factory. If you’ve
ordered an AC power option, the AC power supply tray is attached to the bottom of the MGX 8230
chassis at the factory. To make the unit lighter for installation, Cisco advises you to remove the service
modules (but leave the PXM processor modules installed), fan tray assembly, and AC power supply
modules before installing the MGX 8230.
When you install an MGX 8230, keep the following in mind:
1.
Due to the presence of a disk drive on each MGX 8230 Processor Switch Module (PXM), leave the
PXMs in place if possible. If you remove a PXM, handle it with caution to preserve disk alignment.
2.
Even with all cards removed, the weight and bulk of the card cage mandate that three or more
people install it. Alternatively, one person with a mechanical lift can install the MGX 8230.
3.
Two installers can support and maneuver the MGX 8230 while a third secures it to the rack.
4.
Rear mounting brackets cannot be installed before putting a unit in a 19-inch rack.
5.
On MGX 8230 systems that will be mid-mounted, attach mid-mounting brackets before installing
the unit in a rack.
Co-Locating Cisco Units in the Same Rack
Different Cisco products can reside in the same rack. An MGX 8230 is typically co-located and
rack-mounted either with an IGX or BPX switch, when it used as a feeder.
Rack-Mount Positions
An MGX 8230 is designed to be mounted flush with the front rails of the rack or mid-mounted. When
the MGX 8230 is flush mounted with the front of the rack, it must also be supported by a pair of
mounting rails at the rear of the unit. When the MGX 8230 is mid-mounted, it typically attached to only
one intermediate rail on each side. The allowable positions for intermediate rails are shown in
Figure 2-2.
There are two mid-mount brackets in each rack-mounting kit. One mid-mount bracket fits on each side
of the MGX 8230 chassis. The mid-mount bracket is 12.25 inches (seven rack units) high and has
cutouts along the flange that attaches to the side of the MGX 8230 to allow air flow. The same
mid-mount bracket is used for the AC or DC-powered MGX 8230s; thus for an AC-powered MGX 8230,
with the optional AC power tray assembly attached underneath the MGX 8230 chassis, the mid-mount
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-19
Chapter 2
Installation
Installing an MGX 8230
bracket does not extend down to AC power tray assembly. There are some shorter screws included in
the rack-mount kits for attaching mid-mount brackets; these shorter screws are included specifically for
attaching the mid-mount bracket to the side of the MGX 8230 chassis that has the Fan Tray Assembly.
Longer screws can interfere with the spinning of the fans in the Fan Tray Assembly. The shorter screws
can be used on both mid-mount brackets, however.
Figure 2-2
MGX 8230 Mounting Rail Positions
MGX 8230 depth 23.5 in.
19.86 in.
10.0 in.
5.0 in.
Module
Rear rail
25049
Front rail
Allowable intermediate
rail positions
A rack-mount kit can be ordered for either 19- or 23-inch racks:
•
MGX-8230-MNT19—Mounting kit for 19-inch rack
•
MGX-8230-MNT23—Mounting kit for 23-inch rack
These kits include rear and mid-mount brackets as well as the hardware for mounting the brackets to
the MGX 8230 chassis. Note that there are extra 10-32 screws included in the 19-inch rack-mounting
kit that can be used to secure the MGX 8230 to standard EIA/RETMA rack mounting rails. If the rack
being used has metric or other non-standard mounting holes, the customer must supply appropriate
mounting screws. Since racks often have metric or non-standard threaded holes, you must supply the
screws appropriate for your rack that attach the MGX 8230 to rack mounting rails.
In each 19-inch rack-mounting kit, there are two sets of rear brackets; one set for each side. As shown
in Figure 2-3, one bracket fits on the top at the rear of the MGX 8230, and the other fits on the bottom.
There is a little bend in the bracket that fits over the top (or bottom) of the MGX 8230 chassis. The other
set of brackets fits on the other side of the MGX 8230 chassis.
Cisco MGX 8230 Installation and Configuration
2-20
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Installing an MGX 8230
MGX 8230 Chassis with Rear Mounting Brackets for 19-Inch Rack
Figure 2-4
MGX 8230 Chassis Front View with 19-Inch Mid-Mounting Bracket
23828
17273
Figure 2-3
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-21
Chapter 2
Installation
Installing an MGX 8230
Rack Mounting Procedures
Caution
The MGX 8230 weighs 120 lbs to 150 lbs (54 kg to 68 kg) depending upon the number of
installed cards. Have two persons, one each side, lift the MGX 8230 into the rack, or use
a lift.
19-inch rack mounting
Follow these steps to mount an MGX 8230 in a 19-inch rack.:
Step 1
If applicable, attach one mid-mounting bracket to each side of the MGX 8230.
Step 2
Use a lift or have two people position the MGX 8230 into the rack.
Step 3
Use the 10-32 truss head screws to secure the MGX 8230 to the front mounting rails (or mid-mounting
rails if appropriate).
Step 4
Use the10-32 screws to secure the MGX 8230 to the rear mounting rails and to the rear mounting
bracket, if applicable.
23-inch rack mounting
Follow these steps to mount an MGX 8230 in a 23-inch rack.:
Step 1
Attach the 23-inch mounting brackets to both sides of the MGX 8230 chassis, as shown in Figure 2-5.
Step 2
Use a lift or have two people position the MGX 8230 into the rack.
Step 3
Using hardware that you supply, and is appropriate for your 23-inch rack, secure the MGX 8230 to the
rack mounting rails.
Cisco MGX 8230 Installation and Configuration
2-22
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Installing an MGX 8230
Front View of MGX 8230 with 23-Inch Mid-Mounting Brackets
23829
Figure 2-5
Connecting Power for DC Systems
DC power is connected to one or two DC PEMs located on the MGX 8230 chassis rear panel. You must
supply the wiring from the DC source(s) to the DC PEM(s). The wiring should be 10 AWG (4 square
millimeters).
Warning
Be sure the power to the shelf is OFF at this point. DO NOT apply power until later.
To connect DC power to a DC MGX 8230, follow these steps:
Step 1
Locate the DC power entry module(s) on the rear panel of the MGX 8230.
There will be one or two DC PEMs installed and shipped with your MGX 8230 according to your order.
Figure 2-6 illustrates the rear panel of an MGX 8230 with two DC PEMS, and Figure 2-7 illustrates the
rear panel of an MGX 8230 with one DC PEM.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-23
Chapter 2
Installation
Installing an MGX 8230
Rear View of MGX 8230 with Two DC PEMs
Figure 2-7
Rear View of MGX 8230 with 1 DC PEM
23826
23827
Figure 2-6
Step 2
Locate the pluggable terminal block (TB1) on the DC PEM to which you are connecting source power.
Cisco MGX 8230 Installation and Configuration
2-24
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Installing an MGX 8230
DC Power Entry Module, Rear View
17275
Figure 2-8
OFF
TB1
48 VDC
30A
3
2
1
Step 3
Note the polarities of the TB1 connection points.
Figure 2-9 illustrates the polarity of each connection on the pluggable terminal block. The numbers start
with 1 on the left and go to 3. The connection at the left is for the –48 VDC wire. The middle wire is
Safety Ground. The connection at the right is for the positive return wire (for the –48 VDC).
Figure 2-9
Polarities at MGX 8230 PEM Pluggable Terminal Block
-48 VDC
return
Safety
ground
26265
-48 VDC
1
Step 4
2
3
Locate the wiring block for TB1. Figure 2-10 illustrates the TB1 wiring block (that is, the mating plug
that attaches to TB1).
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-25
Chapter 2
Installation
Installing an MGX 8230
3
2
1
–48 VDC
26264
Figure 2-10 Pluggable Terminal Block on MGX 8230 PEM
–48 VDC Return
Safety ground
10 AWG
or 4 sq. mm.
Step 5
Insert and secure the stripped ends of the 10 AWG wire in the wiring block as shown in Figure 2-9 and
Figure 2-10. Figure 2-10 shows the assembly with an example wire and the screw that secures it in the
pluggable wire block.
Step 6
Plug the pluggable terminal block to the receptacle TB1 on the PEM.
Step 7
If you have a redundant DC PEM installed in your MGX 8230, repeat step 1 through step 6 for the
second DC PEM.
Step 8
For each DC PEM, connect the DC input wiring to a separate dedicated DC source capable of supplying
at least 30 Amps (typical). The –48VDC power source in the building should have a 30 Amp DC circuit
breaker. The building’s wiring should include an easily accessible disconnect device. Make sure the
safety ground wire connects to a reliable building (earth) ground.
Warning
Step 9
For personnel safety, the green or green/yellow wire must connect to safety (earth)
ground at both the equipment and at the supply side of the DC wiring.
Before you turn on the system power, check the supply voltage.
The screws at positions 1 and 3 on the pluggable terminal block are convenient measuring points. Also,
check the impedance between the safety ground (screw at location 2 on the pluggable terminal block)
and the chassis. It should be close to 0.
Step 10
Turn the circuit breaker on all installed PEMs to the off position.
Step 11
Turn on the source power, and check the voltage at the screws at positions 1 and 3 on the pluggable
terminal block for all installed PEMs.
Step 12
Turn off the source power, and go to the section “Cable Management,” which is followed by the section
“Powering up the MGX 8230.”
Cisco MGX 8230 Installation and Configuration
2-26
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Installing an MGX 8230
Connecting Power for AC Systems
This section describes how to connect AC power to an MGX 8230, which has an optional AC power
supply. The optional AC power supply tray is factory-installed on the bottom of the MGX 8230 chassis.
It is one rack unit high and can hold one or two 1200 Watt AC Power Supply Modules. Figure 2-11
illustrates a rear view of an AC Power Supply Module. Each AC Power Supply Module has its own
independent connectors, power switch, and LEDs.
23818
Figure 2-11 Optional 1200 Watt AC Power Supply Module, Rear View
AC DC
Each AC power supply module takes AC power and converts it to -48 VDC, which is then routed
through an external cable to the MGX 8230 backplane connector. (There are no DC PEMs in an
AC-powered MGX 8230.) Each power supply provides a signal that indicates the status of the power
supply.
Note
There must be at least two inches of empty space around the front and rear panels of the
AC power supply for cooling air.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-27
Chapter 2
Installation
Installing an MGX 8230
The rear panel of each AC Power Supply Module has:
•
An AC input connector
•
A special cable that connects the DC output connector of the AC Power Supply Module to the MGX
8230 backplane is supplied with your MGX 8230 for each AC Power Supply Module.
•
Power Supply Enable (On/Off) switch
•
Status light
•
Power cable strain relief clamp
The AC Power Supply Module front panel has both a DC OK LED and an AC OK LED.
Installing AC Power Supply Modules in the AC Power Supply Tray
The AC Power Supply Modules slide into the Optional AC Power Supply Tray from the rear of the MGX
8230. As seen from the front of the MGX 8230, AC Power Supply A (PSA) is on the left, and AC Power
Supply B (PSB) is on the right. The front grill of the Optional AC Power Supply Tray has cutouts that
allow the AC OK and DC OK LEDs on the AC Power Supply Modules (PSA and PSB) to be seen.
To install a 1200 Watt Power Supply Module in the AC Power Supply Tray, follow these steps:
Step 1
From the rear of the MGX 8230, slide a 1200 Watt AC Power Supply Module into the AC Power Supply
Tray.
Step 2
Secure the set screw on the top of the AC Power Supply Module to secure it in the AC Power Supply
Tray.
Step 3
Repeat step 1 and step 2 for the second 1200 Watt Power Supply Module if applicable.
If only one AC Power Supply Module is used in your system, make sure that the slot for the other AC
Power Supply Module is covered with a blank faceplate.
Making the Connections to the AC Power Supply Module(s)
Step 1
Connect a cable supplied with your MGX 8230 to the DC out connector on the optional AC power
supply.
Note
Without the DC cable connected to the MGX 8230 backplane, the AC power
supply will not power up. This is a safety feature.
The other end of this cable has a connector and a fixture for attaching to the MGX 8230 backplane. The
cable from the left AC Power Supply Module is connected to the connector on the left side of the MGX
8230 backplane. Likewise, the cable from the right AC Power Supply Module is connected to the
connector on the right side of the MGX 8230 backplane.
Step 2
Use the appropriate AC power cord to connect the AC power source to the IEC receptacle(s) on the AC
Power Supply Module and tighten the strain relief clamp to secure the cable.
Step 3
Make sure that the building AC receptacle is properly grounded.
Step 4
Repeat steps 2 through 3 for the second AC Power Supply Module if appropriate.
Cisco MGX 8230 Installation and Configuration
2-28
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Installing an MGX 8230
Figure 2-12 illustrates a MGX 8230 chassis with two AC Power Supply Modules connected to the MGX
8230 backplane.
Figure 2-13 illustrates an MGX 8230 with one AC Power Supply Module connected to the MGX 8230
backplane. If only one AC Power Supply Module is used in your MGX 8230, make sure that there are
blank faceplates covering the slots for the second AC Power Supply Module and the opening where the
DC PEM would otherwise be installed.
In order for the AC power supply to function the enable switch must be in the “On” position, and the
DC cable must be connected between the AC power supply connector and the MGX 8230 backplane.
Proceed to the section “Cable Management,” which is followed by the section “Powering up the MGX
8230.”
Note
An AC power module will not power on if the DC cable is disconnected from the MGX
8230 backplane.
23825
Figure 2-12 Rear View of MGX 8230 with Two Optional AC Power Supply Modules
AC DC
AC DC
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-29
Chapter 2
Installation
Installing an MGX 8230
23824
Figure 2-13 Rear View of MGX 8230 with One AC Power Supply Module
AC DC
AC DC
Cable Management
A fully loaded MGX 8230 may have many cables attached to the rack’s modules. Cable management
kits are available for installation on the rear of rack modules. These kits provide the means to route the
power and data cables in a neat and orderly fashion to and from the modules in the MGX 8230. The
cable management system is shipped with attaching hardware along with your MGX 8230.
Install the cable management brackets after a rack mounted unit has been installed in a rack, or a
standalone MGX 8230 has been positioned. Figure 2-14 illustrates an installed cable management
system. When installing the cable management system on a rack-mount MGX 8230, the screws securing
the cable guides to the MGX 8230 chassis are inserted from the outside into the captive nuts in the
chassis. When installing the cable management system in a standalone MGX 8230, the screws securing
the cable guides to the MGX 8230 chassis are inserted from the outside into the captive nuts in the
chassis.
Cisco MGX 8230 Installation and Configuration
2-30
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 2
Installation
Installing an MGX 8230
23830
Figure 2-14 Cable Management System on Rack-Mount MGX 8230
The cable management system provides the following features:
•
Cards can be inserted or removed without disturbing cables attached to cards in adjacent slots.
•
Cables can be routed from both above and below the chassis.
Powering up the MGX 8230
Before applying power to the MGX 8230, check the following items:
1.
Assure that the unit is properly connected to site safety grounding.
2.
AC or DC power sources are correctly installed.
3.
All cards are locked in the correct slots.
4.
All cables are secure.
5.
Control terminal is connected to the Console Port on the PXM-UI back card. (See the “MGX 8230
Feeder” appendix in the Cisco IGX 8400 Series Installation and Configuration document for
Release 9.2.)
After the preceding checks, turn on the power. Check the following:
1.
At the front of the unit, the status light on the PXM should be green.
2.
For an AC-powered system, the “AC” and “DC” LEDs on each AC Power Supply Module, as
applicable, should be green.
3.
For a DC-powered system, the “DC OK” LED on each DC PEM should be on.
4.
After each service module comes up, the status LEDs on each should show that it is in standby.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
2-31
Chapter 2
Installation
Installing an MGX 8230
5.
When power is turned on, make a visual check to verify that all fans are running.
6.
After the system comes up, execute the dsppwr command.
Configuring the MGX 8230 as an MGX Feeder
Connecting an MGX 8230 to an MGX and configuring it to function as a feeder is covered in Chapter 3,
“Configuring the MGX 8230.”
Cisco MGX 8230 Installation and Configuration
2-32
Release 1.0, Part Number 78-10616-01, June 2000
CH A P T E R
3
Configuring the MGX 8230
The MGX 8230 is a 12-slot card cage that uses a subset of MGX 8850/8250 modules and is configured
as an MGX or BPX feeder. This chapter describes the configuration of the MGX 8230 as an MGX or
BPX feeder. Before configuring an MGX 8230 as an MGX or BPX feeder, you should have read the
previous sections to perform the physical installation of MGX 8230.
MGX 8230 Overview
The MGX 8230, shown in Figure 3-1, is a 12-slot chassis with horizontally mounted processor modules
(MGX 8230-PXMs), service modules, and back cards. Built with the MGX 8850/8250 architecture, the
MGX 8230 accepts the same double-height and single-height service modules as the MGX 8850/8250,
with a few exceptions. The MGX 8230 feeder does not support the Voice Interface Service Module
(VISM), or the Route Processor Module (RPM) of the MGX 8850.
MGX 8230 slots 1 and 2 are reserved for MGX 8230 PXMs, the processor module, and slots 3 through
6 accept service modules, AUSM, FRSM, CESM. Slots 7 and 14 accept an SRM modules only. Slots
3-5 can accept 1 double-height service module or be divided to accept 2 single-height service modules.
Slot numbers 8 and 9 only apply to backcard slots. Rules and instructions for changing double-height
slots into single-height slots are given in Chapter 2, “Installation.” The slots are numbered as shown in
Figure 3-1.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-1
Chapter 3
Configuring the MGX 8230
MGX 8230 Overview
MGX 8230
F
A
N
7 RU
(12.25 in.,
31.1 cm.)
T
R
A
Y
7
SRM 1
SRM 2
14
6
Single height SM
Single height SM
13
5
Single height SM
Single height SM
12
4
Single height SM
Single height SM
11
3
Double height SM
10
2
PXM1 B
9
1
PXM1 A
8
1 RU
(1.75 in.,
4.5 cm.)
38384
Figure 3-1
23.5 in.,
(59.7 cm.)
Optional AC power tray
As an MGX or BPX feeder, the MGX 8230 concentrates user ATM, Frame Relay, and circuit emulation
traffic and feeds it to an MGX 8000 series switch over an OC-3 or OC-12 feeder trunk. The MGX/BPX
series switch performs the switching and routing of the MGX 8230 user connections through an MGX
and BPX network. Figure 3-2 is a simplified diagram of the MGX 8230 MGX feeder application.
MGX 8230 MGX Feeder Application
T1/E1 ATM
T1/E1 Frame Relay
T3/E3 Frame Relay
T1/E1 Circuit Emulation
BPX 8600
switch
MGX 8230
Service interfaces
BPX and MGX network
OC-3 ATM, OC-12, or T3/E3
feeder connection
42293
Figure 3-2
Main Features
For the first release of MGX 8230 MGX feeder, all features available in MGX 8850 Release 1.1 will be
available. The features include:
•
MGX 8230-PXM with 4-port OC-3c ATM port.
– MMF and SMFIR and SMFLR back cards are supported.
– MGX 8230-PXM ports can be used only as feeder trunks.
– Core redundancy for MGX 8230-PXM.
– Environmental monitoring.
Cisco MGX 8230 Installation and Configuration
3-2
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
MGX 8230 Overview
•
ATM, Frame Relay, and Circuit Emulation service modules:
– AUSM-8T1/E1 with RJ-48-T1 and SMB E1 back card with UNI and IMA support.
– FRSM-8T1/E1 with RJ48-T1/E1 and SMB E1 back cards.
– FRSM-2T3E3 with BNC-2T3/E3 back cards.
– FRSM-HS2 with 2 port HSSI back card.
– FRSM-2CT3 with BNC-2T3 back card.
– CESM-8T1/E1 with RJ48-T1 and SMB E1 back cards.
•
1:1 redundancy for T3/E3 cards.
•
Redundancy for T1/E1 service modules
•
Graceful upgrade.
•
1000 connections per card, 4000 connections per shelf.
•
As an MGX feeder:
– Four feeders per MGX
– 2750 connections per MGX (1M BRAM)
– 7000 connections per MGX (2M BRAM)
– 8000 LCN/UXM (combination of trunks and ports)
The MGX 8230 backplane supports a minimum of 1.2 Gbps of non-blocking switching.
The MGX 8230 can also support a wide range of services over narrowband and mid-band user
interfaces. It maps all the service traffic to and from ATM based on standardized interworking methods.
When the MGX 8230 is used as a feeder, it uses a single port to communicate the aggregated traffic over
an ATM interface with an MGX 8000 series switch.
The MGX 8230 supports up to 80 channelized or non-channelized T1 and E1 interfaces on a single
IP + ATM multiservice gateway. These interfaces support:
•
Frame Relay, UNI, and NNI
•
ATM UNI, NNI, and FUNI
•
Frame Relay-to-ATM network interworking
•
Frame Relay-to-ATM service interworking
•
Circuit emulation services
Frame-based services on T3 and E3 high-speed lines are also supported.
The MGX 8230 also supports Inverse Multiplexing for ATM (IMA) to provide ATM connectivity below
T3 or E3 rates.
The modular, software-based system architecture enables it to support new features through
downloadable software upgrades or new hardware modules.
Standards-Based Conversion to ATM
The MGX 8230 converts all user-information into 53-byte ATM cells by using the appropriate ATM
Adaptation Layer (AAL) for transport over the ATM backbone network. The individual service modules
segment and reassemble (SAR) cells to eliminate system bottlenecks. The following list shows the
applicable AAL for each service:
•
Circuit emulation services use AAL1.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-3
Chapter 3
Configuring the MGX 8230
MGX 8230 Overview
•
Frame Relay-to-ATM network interworking uses AAL5 and Frame Relay Service Specific
Convergence Sub-layer (FR-SSCS).
•
Frame Relay-to-ATM service interworking uses both transparent and translation modes to map
Frame Relay to native ATM AAL5.
•
Frame Forwarding uses AAL5.
The complete list of MGX 8230 technical specifications is contained in Appendix A, “Technical
Specifications.”
MGX 8230 Management
To control the MGX 8230, you can use the Cisco WAN Manager (formerly StrataView Plus) application
(Release 9.2.04) for connection management, the CiscoView application (Release 2.03) for hardware
configuration, and a command line interface (CLI) for low-level control. The command line interface
is identical that of the MGX 8850 and is described in the section “MGX 8230 and MGX 8850
Command Line Interface,”the firmware determines the available functionality, and you can download
firmware to upgrade functionality through a TFTP application on a workstation or a PC.
The current status and configuration parameters of the MGX 8230 modules reside in an SNMP
Management Information Base (MIB). Firmware updates the MIB as changes in status and
configuration occur.
The control port (SLIP protocol only), the LAN (Ethernet) port, and the in-band ATM connection
(feeder application only) all support the CLI (via telnet), TFTP, and SNMP protocols for communicating
with the MGX 8230 IP + ATM multiservice gateway (or an MGX 8850/8250 switch).
Statistics and Command Line Interface
All statistics counters available in MGX 8850 Release 1.1 are supported by the MGX 8230. There will
be no change in the command line interface from MGX 8850. See Appendix A, “Technical
Specifications” for a listing of the supported statistics.
The addshelf command on MGX has been modified to support adding an MGX 8230 IP + ATM
multiservice gateway to an MGX’s UXM trunk.
Alarm and Error Handling
The MGX 8230 provides the same alarm and error handling as SWSW Release 9.2 and MGX 8850 and
MGX 8250.
MGX 8230 Processor and Service Modules
In this release, the MGX 8230 as an MGX feeder supports the following processor and service modules:
•
MGX 8230 Processor Switching Module (PXM-1)—This front card controls the MGX 8230 and
supports two types of back cards: the user interface card and the broadband network module, which
provides the OC3, OC12, or 7323 feeder trunk to an MGX. Note that MGX 8230 PXM is not
physically identical to an MGX 8850 PXM and is keyed so that it will not fit in an MGX 8850
chassis.
– Processor Switch Module User Interface (PXM-UI)—The PXM1-UI provides user-control of
the MGX 8230.
Cisco MGX 8230 Installation and Configuration
3-4
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
MGX 8230 Overview
– Broadband Network Module (MGX-MMF-4-155)—The MMF-4-155 provides 4 SONET
OC3/STM1 ATM interfaces at 155 Mbps over multi-mode fiber. Only port 1 is used as the
MGX feeder trunk in this application of the MGX 8230.
– Broadband Network Module (MGX-SMFIR-4-155)—The SMF-4-155 provides 4 SONET
OC3/STM1 ATM interfaces at 155 Mbps over single multi-mode fiber intermediate reach.
Only port 1 is used as the MGX feeder trunk in this application of the MGX 8230.
– Broadband Network Module (MGX-SMILR-4-155)—The SMF-4-155 provides 4 SONET
OC3/STM1 ATMM interfaces at 155 Mbps over single multi-mode fiber long reach. Only port
1 is used as the MGX feeder trunk in this application of the MGX 8230.
– Frame Service Module for T3 and E3 (MGX-FRSM-2E3T3)—The MGX-FRSM-2E3/T3
provides interfaces for up to two T3 or E3 frame relay lines, each of which can support either
2 T3 lines (each at 44.736 Mbps) or 2 E3 lines (each at 34.368Mbps) FR-UNI, ATM-FUNI, or
Frame Forwarding port.
– Broadband Network Module (MGX-SMFIR-1-622 and MGX-SMFLR-1-622)—The
SMFIR-1-622 is a broadband network module for the PXM and provides a SONET
OC12/STM4 ATM interface at 622 Mbps.
Note
The MGX 8230 supports redundant processor modules (PXMs) in chassis slots 1 and 2. If
either card malfunctions, the standby set automatically becomes the active set.
•
Frame Service Module for T3 and E3 (MGX-FRSM-2E3T3)—The FRSM-2E3/T3 card provides
interfaces for up to two T3 or E3 Frame Relay lines, each of which can support either two T3 lines
(each at 44.736 Mbps) or two E lines (each at 34.368Mbps) FR-UNI, FR-NNI, ATM-FUNI, or
Frame Forwarding port.
•
Frame Service Module for channelized T3 (MGX-FRSM-2CT3)—The FRSM-2CT3 card supports
interfaces for up to two T3 channelized Frame Relay lines, each of which supports
56 Kbps, 64 Kbps, Nx56 Kbps, Nx64 kbps, T1 ports for a total of 256 ports that can be freely
distributed across the two T3 lines.
•
Frame Service Module for unchannelized HSSI (MGX-HS2/B)
•
Frame Service Module for T1 (MGX-FRSM-8T1)—The FRSM-8T1 card provides interfaces for
up to eight T1 lines, each of which can support one 56 Kbps or one Nx64 Kbps FR-UNI, FR-NNI
port, ATM-FUNI, or a Frame Forwarding port.
•
Frame Service Module for T1, channelized (MGX-FRSM-8T1-C)—The FRSM-8T1-C card
provides interfaces for up to eight T1 lines, each of which can support up to twenty-four 56 Kbps or
Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or Frame Forwarding ports.
•
Frame Service Module for E1 (MGX-FRSM-8E1)—The FRSM-8E1 card provides interfaces for
up to eight E1 lines, each of which can support one 56 Kbps or one Nx64 Kbps FR-UNI, FR-NNI,
ATM-FUNI, or Frame Forwarding port.
•
Frame Service Module for E1, channelized (MGX-FRSM-8E1-C)—The FRSM-8E1-C card
provides interfaces for up to eight E1 channelized Frame Relay lines, each of which can support
multiple (up to thirty-one) 56 Kbps or Nx64 Kbps FR-UNI, FR-NNI, ATM-FUNI, or Frame
Forwarding ports.
•
ATM UNI Service Module for T1 (MGX-AUSM/B-8T1E1)—This card provides interfaces for up
to eight T1 or E1 lines, each of which can support one T1 ATM UNI or ATM NNI plus additional
support for IMA, permitting the BPX ATM trunk to be used over multiple T1 or E1 lines instead of
a single T3 or E3 line.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-5
Chapter 3
Configuring the MGX 8230
MGX 8230 Overview
Note
•
Circuit Emulation Service Module for T1 (MGX-CESM-8T1)—The CESM-8T1 card provides
interfaces for up to eight T1 lines, each of which is a 1.544 Mbps structured or unstructured
synchronous data stream.
•
Circuit Emulation Service Module for E1 (MGX-CESM-8E1)—The CESM-8E1 card provides
interfaces for up to eight E1 lines, each of which is a 2.048-Mbps structured or unstructured
synchronous data stream.
The MGX 8230 does not support the Route Processor Module (RPM) or the Voice
Interface Service Module of the MGX 8850/8250 card set.
MGX 8230 MGX Feeder to MGX Functional Overview
All functions supported on MGX Release 1.1.24 are supported when an MGX 8230 is added as an MGX
feeder. This includes features such as ports and trunks, virtual trunks on MGX and so on.
Software Release 9.2 supports UXM as feeder trunks to the MGX 8230. Only the MMF and SMFIR
back cards for the UXM can be connected to an MGX 8230 uplink back card.
Figure 3-3 illustrates a typical configuration for an network with an MGX 8230 feeder to the MGX.
AUSM
MGX 8830
MGX 8830
PXM
PXM
UXM-E
UXM-E
UFM
UXM-E
FRSM
CESM
AUSM
FRSM
Typical MGX 8230 as MGX Feeder Application
CESM
Figure 3-3
UXM-E
UXM-E
IMA
IMA
NTM
NTM
MGX
UFM
MGX
UXM-E
UXM-E
UXM-E
26273
BPX
BXM
BXM
Cisco MGX 8230 Installation and Configuration
3-6
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
MGX 8230 and MGX 8850 Relationship
The following cards are supported as end points for MGX 8230 connections through the MGX. All
physical interfaces to these cards are supported.
•
UFM
•
UXM
Within an MGX/BPX network with MGX 8230 as feeders to the MGX switch, the following trunks are
supported:
•
MGX-BPX—UXM-BXM
•
MGX-MGX:
– UXM-UXM ATM trunk
– UXM-UXM IMA trunk
– NTM-NTM FastPacket trunk
A BPX interface cannot be used as an end point on an MGX 8230 connection. The BPX switch will
function as a routing node (via node) within the MGX/BPX network, however.
The MGX 8230 feeder to the MGX supports the following end point combinations. All interface speeds
supported in MGX 8850 Release 1.1.24 and in BPX 8600 series Release 9.2 are supported.
Table 3-1
MGX 8230 Feeder Connection Endpoints
From
To
MGX 8230-CESM
MGX 8230-CESM through MGX/BPX network
MGX 8230-FRSM
MGX 8230-FRSM through MGX/BPX network
MGX-UFM
MGX-UXM with Service Interworking
MGX 8230-AUSM MGX 8230-AUSM
MGX-UXM
MGX-UFM with Service Interworking
MGX 8230 and MGX 8850 Relationship
In the MGX feeder application, the MGX 8230 serves as a cost-reduced, smaller form-factor of the
MGX 8850 feeder. The MGX 8230 has many similarities to the MGX 8850, which include:
•
MGX 8230 and MGX 8850 Command Line Interface
•
MGX 8230 and MGX 8250 User Interface Access
•
MGX 8230 and MGX 8850 Error Messages
MGX 8230 and MGX 8850 Command Line Interface
The preferred tools for configuring, monitoring, and controlling an MGX 8230 are the CiscoView and
Cisco WAN Manager applications for equipment management and connection management,
respectively. (The Cisco WAN Manager application is the former Cisco StrataView Plus application
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-7
Chapter 3
Configuring the MGX 8230
MGX 8230 and MGX 8850 Relationship
with the equipment management removed.) The MGX 8230 and MGX 8850 command line interface
(CLI) also provides access to the MGX 8230 and is highly applicable during initial installation,
troubleshooting, and any situation where low-level control is useful.
The Cisco MGX 8230 Command Reference provides detailed information about the MGX 8230 CLI
commands. In the Cisco MGX 8250 Command Reference, the CLI commands are divided into major
functional groups. The command reference gives complete name of the command and the cards for
which the command is valid. This chapter contains examples of the use of some of the more common
commands, but for complete information, look at the Cisco MGX 8230 Command Reference.
The MGX 8230 CLI is typically accessed by a terminal attached to PXM-UI back card control port or
through a telnet session as described in the section “MGX 8230 and MGX 8250 User Interface Access.”
The command line prompt shows the name of the MGX 8230, the number of the MGX 8230 (which is
always “1”), the slot number and type for the current card, and whether the card is in the active (a) or
standby state (s). The following is an example of the command line prompt:
excel.1.6.AUSM.a >
In this case, the current card is an active AUSM in slot 6, and the name of the node is “excel.”
The command notation and argument parameters follow standard programming convention: a space
separates the command and each parameter; variables have an italicized typeface; required arguments
appear within “<>” marks; optional parameters appear within square brackets (“[ ]”); and a vertical bar
(|) represents the logical OR function.
Note
When you use the MGX 8230 CLI, you must type all command arguments then press
Return or Enter rather than enter one parameter at a time.
When you enter a command with no parameters, a usage message appears. This message
shows syntax and ranges for the applicable command parameters.
The MGX 8230 commands are divided into commands directed at the MGX 8230 PXM processor
module, the Portable AutoRoute (PAR) commands, and the service module commands. Applicable
service module commands become available when you switch to a card by executing the cc command.
Many commands apply to both the MGX 8230-PXM and the service modules.
MGX 8230 and MGX 8250 User Interface Access
Three external ports exist for controlling the MGX 8230 through the MGX 8230-PXM User Interface
card (PXM-UI):
1.
The control port (sometimes called the console port) to use the command line interface (CLI) on
an ASCII terminal. The purpose of this port is:
– Initial assignment of IP addresses to the Ethernet port, maintenance port, the inband ATM IP
address, and the IP address of the statistics manager. The ATM IP address belongs to the link
between the MGX 8230-PXM and the MGX 8000 series switch and applies to the feeder
application of the MGX 8230.
Before you use the CiscoView or the Cisco WAN Manager (formerly StrataView Plus) network
management applications, the IP addresses you intend for the MGX 8230 must reside on the
workstation in the etc/hosts file. Also, the text file config.sv on the workstation must contain
the name of the MGX 8230 you intend to be the gateway node, the network ID, the network
name, and so on. See the Cisco WAN Manager documentation for the file system requirements
on the workstation.
Cisco MGX 8230 Installation and Configuration
3-8
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
MGX 8230 and MGX 8850 Relationship
–
Low-level control or troubleshooting. (You can also use the CLI through a window in the Cisco
WAN Manager application.)
2.
The Ethernet port to use a workstation running a Cisco network management application such as
the Cisco WAN Manager or CiscoView application. Typically, the workstation on a LAN is
co-located with the MGX 8230 IP + ATM multiservice gateway and an MGX switch.
3.
The maintenance port (sometimes called the modem port) to connect either a single workstation
running an IP-based application or a terminal server that supports multiple workstations. The
workstation must support SLIP. Typically, you use this port with a modem because the MGX
8230/MGX reside at a remote location. The typical applications are software and firmware
download or tasks that require low-level access.
The maintenance port and Ethernet port support IP-based applications. Through these ports, the
following applications run:
•
Telnet supports CLI command execution from any IP-based application window as well as a
window in the Cisco WAN Manager application.
•
TFTP lets you download firmware and upload and download configuration information.
•
SNMP supports equipment management through the CiscoView application and connection
management through the Cisco WAN Manager application.
MGX 8230 and MGX 8850 Error Messages
In response to many MGX 8230 conditions and CLI commands, the MGX 8230 stores error messages
in an error log. Not all messages indicate problems; some messages are only informational, while others
help diagnose problems.
Messages are listed by the facility (hardware device, protocol, or a module or system software) that
produces the messages. Within each facility, messages are listed by the severity level, from 1 through
7. Each message is followed by an explanation and a recommended action. Messages appear only when
the system remains operational.
Message Structure
Messages similar to the following will appear in the error log:
04/27/1999-12:13:58 07 tTnInTsk01
CLI-7-CLITNLOG
cliTelnetd: [email protected]: telnet.01: disconnected
These messages are structured as follows:
mm/dd/yyyy-hh:mm:ss slot# taskname facility-severity-MNEMONIC description
where
mm/dd/yyyy-hh:mm:ss
slot#
is the date and time of the error/event,
is the slot number to which the message applies, and
taskname
is the name of the task to which the message applies.
The remaining parts of the messages, facility-severity-MNEMONIC description, contain the
following information:
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-9
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
•
Facility codes —A facility code consists of two or more uppercase letters that indicate the reference
facility to which the message refers. A facility can be a hardware device, a protocol, or a portion of
the system software, such as BOOT for bootstrap module, for CLI for Command Line Interface, or
CNTP for Control Point Software.
•
Severity Level—A severity level code is a single digit from 0 to 7 that reflects the severity of the
condition from 1-fatal (platform needs reset) to 7-info (informational only). The lower the number,
the more serious the situation.
•
Mnemonic Codes—The MNEMONIC code uniquely identifies the error message. All mnemonics
are all uppercase character strings.
•
Description Text Strings—A description text string describes the condition. Sometimes it contains
detailed information about the event, including terminal port numbers, network addresses, or
addresses that correspond to locations in the system memory address space. Because these variable
fields can change from message to message, they are represented by short strings in square brackets
( [ ]). A decimal number, for example, is represented as [dec].
The MGX 8230 error messages are described in detail in the Cisco MGX 8230 Error Messages.
Configuring an MGX 8230 MGX Feeder
This section provides the initial procedures for connecting an MGX 8230 feeder to an MGX. It assumes
that you have already installed the MGX 8230 in a rack and connected power to it as described in
Chapter 2, “Installation.” The procedures for adding ATM, Frame Relay, or circuit emulation data
connections are contained in the “Adding Service Module Connections” section on page 3-24.
This section contains the following subsections:
•
Making the PXM-UI Interface Connections
•
Initial MGX 8230 Bring-Up
•
Configuring Node-Level Parameters
•
Downloading Firmware to a Service Module
•
MGX 8230 CLI Configuration of a Feeder
•
CiscoView Configuration of a Feeder
Making the PXM-UI Interface Connections
During the initial configuration of an MGX 8230, you typically have to connect a terminal (or PC with
terminal emulation software) to the PXM-UI back card to issue commands to the MGX 8230. The
PXM-UI back card is illustrated in Figure 3-4.
This section includes the following subsections:
•
Attaching a Control Console
•
Making External Clock Connections
•
Alarm Output Connection
Cisco MGX 8230 Installation and Configuration
3-10
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
PXM-UI Faceplate
Maintenance
port
LAN port
C
P
T1
M
P
C
L
O
C
K
L
A
N
A
L
A
R
M
E1 clock
source
PXM-UI
E1 CLOCK
Alarm
outputs
T1 clock
26261
Figure 3-4
Control
port
Attaching a Control Console
The control console can be attached to either the maintenance port or to the control port on the MGX
8230-PXM user interface back card (PXM-UI).
When using an alphanumeric (dumb) terminal to input CLI commands to the MGX 8230, the terminal
must be connected directly (no modem) to the maintenance port DB25 connector on the PSM-UI
faceplate. Use a conventional RS-232 cable with a DB25 connector at each end. A so-called “Null
Modem” cable is not required. This port can be Y-cabled for redundancy.
When using a workstation to issue commands or transfer files to and from the shelf, the workstation can
be attached through the RS-232 control port on the PXM-UI. Using this connection requires the
workstation to communicate using TCP/IP and SLIP communication protocols.
Making External Clock Connections
If external equipment or a local digital central office is to provide synchronization to the MGX 8230,
you can connect the external clock source to the PXM-UI back card. For a T1 clock input, connect the
source to the RJ 45 connector labeled “T1 Clock.” For a E1 clock input, use the SMC connector marked
“E1 Clock.”
Alarm Output Connection
Dry contact relay closures are available for forwarding MGX 8230 alarms to an alarm system. Separate
visual and audible alarm outputs are available for major and minor alarm outputs. The MGX 8230 alarm
outputs are available from a DB15 connector on the PXM-UI back card faceplate. Refer to
Appendix B, “Cable Specifications” for the pinouts on this connector. Use switchboard cable for
running these connections.
Initial MGX 8230 Bring-Up
This section describes how to start up the MGX 8230 for the first time. It begins with an MGX
8230-PXM that has only boot-mode firmware. The descriptions tell you how to:
1.
Establish communication with the MGX 8230.
2.
Configure one or more boot-level IP addresses to make the MGX 8230 available to the network.
3.
Download MGX 8230-PXM firmware.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-11
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
4.
Configure a new, MGX 8230-level Ethernet IP address for the MGX 8230-PXM as needed or other
SLIP or IP addresses.
5.
Specify a name for the MGX 8230.
6.
Specify the time on the MGX 8230.
7.
Optionally configure a time zone for the Western Hemisphere, or configure a time zone relative to
Greenwich Mean Time if the MGX 8230 resides outside the Western Hemisphere.
8.
Download firmware to the service modules.
If the MGX 8230-PXM has no runtime (or “on-line”) firmware Image, begin with the boot-mode
description in the “Bringing Up an MGX 8230-PXM With No Run-time Firmware” section on
page 3-12. If the MGX 8230-PXM has a run-time firmware image, go to the section “Bringing Up an
MGX 8230-PXM With No Run-time Firmware.”
Bringing Up an MGX 8230-PXM With No Run-time Firmware
The section describes the tasks for loading runtime firmware onto a MGX 8230-PXM that has only a
boot loader.
Step 1
Step 2
Establish communication with the MGX 8230 by doing one of the following:
•
Connect a cable between your terminal or PC and the PXM-UI control port.
•
If you are using an ASCII terminal connected to the control port, the prompt for the next command
is already present upon power-up. (If the display is skewed, make sure the terminal speed and
PXM-UI port speeds are the same.)
•
If you are using a utility such as Hyper Terminal on a PC, the firmware may reside on either a floppy
or the hard drive.
Execute the command bootChange to configure boot-level IP parameters.
If the MGX 8230 has a redundant MGX 8230-PXM, execute bootChange on each MGX 8230-PXM to
configure unique, boot-level IP addresses. (During the subsequent MGX 8230-level configuration, you
must configure another Ethernet IP address that applies to both MGX 8230-PXMs.) The following are
the only parameters that are meaningful at this point, so press Return other parameters:
•
Mandatory “host name” is a name for the workstation. For the MGX 8230, enter the letter c.
•
Ethernet IP address and subnet mask for the MGX 8230-PXM LAN port are mandatory (see “inet
on Ethernet” in the following example). Follow the IP address with a colon and a net mask. The
netmask is eight hexadecimal numbers with no embedded periods. Do not type spaces on either side
of the colon.
•
If the workstation from which you download firmware is on a subnet other than the subnet of the
MGX 8230-PXM, enter a gateway IP address (“gateway inet”).
Cisco MGX 8230 Installation and Configuration
3-12
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
Note the three editing functions near the top of the following example. Of these, typing a period to the
clear the current field is the most commonly used.
>bootChange
'.' = clear field; '-' = go to previous field;
boot device
: lnPci
processor number
: 0
host name
:c
file name
:
inet on ethernet (e) : 188.29.37.14:ffffff00
inet on backplane (b):
host inet (h)
:
gateway inet (g)
: 188.29.37.1
user (u)
:
ftp password (pw) (blank = use rsh):
flags (f)
: 0x0
target name (tn)
:
startup script (s)
:
other (o)
:
^D = quit
The MGX 8230-PXM now has a boot-level IP address. Remember to repeat the bootChange command
on the redundant MGX 8230-PXM if the system has one.
Step 3
Enter reboot to reset the MGX 8230-PXM.
The MGX 8230-PXM is ready to receive a firmware image through the Ethernet port. Use the
workstation for the next steps.
Step 4
At the workstation, you can optionally ping the MGX 8230-PXM using the IP address to confirm that
the node is reachable.
Step 5
Establish communication with the MGX 8230-PXM according to the user-communication device type.
For example, at the prompt on a UNIX workstation, you could enter:
>tip -9600 /dev/ttya
The device specification could also be ttyb.
Step 6
Enter the tftp command with the IP address set at the ASCII terminal. For example, if the console port
is connected to the serial port of the workstation:
$tftp 162.29.38.101
Step 7
At the tftp prompt, enter binary mode:
>bin
Step 8
From the directory where the firmware resides, enter the put command and include the arguments that
specify the firmware release number, the statement that this firmware applies to the active MGX
8230-PXM, and the release directory.
If necessary, refer to the release notes for new firmware release numbers. The entries are case-sensitive.
For example:
>put pxm_release_number.fw POPEYE@PXM_ACTIVE.FW
where release_number is a decimal number in the form n.n.nn. Currently, the initial n typically is a “1.”
An example filename for MGX 8230-PXM firmware is “pxm_1.0.03.” Note that the download
automatically includes the firmware for the standby MGX 8230-PXM (if present). You can
subsequently see POPEYE@PXM_STANDBY.FW in c:/FW.
Check the console to verify that the transfer completed and the checksum passed.
Step 9
Quit the tftp application, then go to the ASCII terminal connected to the control port:
>quit
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-13
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
Step 10
At the ASCII terminal, cd to FW directory on the hard drive.
Step 11
List the contents to confirm that the firmware resides in the FW directory:
>cd “c:/FW”
>ll
Note these required quote marks are absent when you use the CLI after you reboot the MGX 8230-PXM
with its run-time image (see “Configuring Node-Level Parameters”).
Enter the following:
Step 12
>setPXMPrimary “version”
where version is the version number of the firmware. The name of a MGX 8230-PXM firmware file has
the format pxm_version.fw. For example: in PXM_1.0.03.fw, version is 1.0.03.
Reboot the system again:
Step 13
>reboot
A login prompt appears on the ASCII terminal. The MGX 8230-PXM is now the same as an MGX
8230-PXM that Cisco ships with a run-time firmware image.
Configuring Node-Level Parameters
Except for adding a user and creating a password, all the tasks described in this section can be
performed through the CiscoView application. For descriptions of the commands you enter at the CLI,
see the Cisco MGX 8250 Command Reference. A representation of the feeder application of the MGX
8230 appears in Figure 3-5.
MGX 8230 MGX Feeder Application
T1/E1 ATM
T1/E1 Frame Relay
T3/E3 Frame Relay
T1/E1 Circuit Emulation
Service interfaces
MGX 8230
Uplink
U
X
BPX 8600
M-E
switch
BPX and MGX network
OC-3 ATM, OC-12, or T3/E3
feeder connection
38379
Figure 3-5
Resource Partitioning
A resource partition on an MGX 8230-PXM consists of a percentage of bandwidth, a VPI/VCI range,
and the number of global logical connection numbers (GLCNs) available to a network control
application. By default, all resources on a logical interface are available to any controller on a
first-come, first-served basis. In this release of the MGX 8230 MGX feeder application, Portable
AutoRoute (PAR) is the only network control application. Future releases of the MGX 8230 may
include other network control applications such as Multiprotocol Label Switching (MPLS), then the
resources will have to be carefully partitioned.
Note
The MGX 8230-PXM resources do not have to be partitioned for the MGX 8230 MGX
feeder application.
Cisco MGX 8230 Installation and Configuration
3-14
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
At the MGX 8230 CLI prompt on the ASCII terminal:
Step 1
Enter the default login and password provided in the release notes.
The terminal displays the slot number of the MGX 8230-PXM you have logged into by default:
card number [1]:
Step 2
Press Return to enter the CLI of this MGX 8230-PXM.
At run-time, you could also enter the slot number of a service module or a standby MGX 8230-PXM.
In this case, the CLI prompt shows:
NODENAME.1.1.PXM.a>
where NODENAME shows that the node has no name; the slot number of the MGX 8230-PXM is 1;
and this MGX 8230-PXM is active. The general format of the CLI prompt is:
nodename.1.slot.cardtype.a>
where nodename is the name of the node; the shelf (node) number is always 1; slot is the card location;
cardtype identifies the card; and the card state is active (a) or standby (s).
Step 3
Display the cards in the system:
NODENAME.1.1.PXM.a> dspcds
Step 4
Display any IP addresses in the system:
NODENAME.1.1.PXM.a> dspifip
Step 5
Change any IP addresses as needed:
NODENAME.1.1.PXM.a> cnfifip <interface> <IP_Addr> <Net_Mask> [BrocastAddr]
where interface is a number: 26 is the Ethernet (LAN AUI) port, 28 is the maintenance port (SLIP), or
37 for the ATM IP address (feeder application only). Note that BrocastAddr applies to only the
Ethernet interface (number 26).
Note
Step 6
Check the Release Notes for any variations in how to configure IP addresses.
Execute the cnfname command to assign a name to the MGX 8230:
UNKNOWN.1.1.PXM.a> cnfname <node name>
where node name is a case-sensitive name up to eight characters. For example:
UNKNOWN.1.1.PXM.a> cnfname cisco22
Step 7
Execute the cnftime command to specify the time on the MGX 8230:
cisco22.1.1.PXM.a> cnftime <hh:mm:ss>
where hh is the hour of the day in the range 1–24; mm is the minute of the hour in the range 1–60; and
ss is the number of seconds in the minute and has a range of 1–60.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-15
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
Step 8
Optionally configure a time zone for the node. Use cnftmzn to specify a time zone in the Western
Hemisphere. To configure a time zone outside the Western Hemisphere, first specify Greenwich Mean
Time (GMT) with cnftmzn then specify the offset from GMT by using cnftmzngmt:
•
cisco22.1.1.PXM.a> cnftmzn <timezone>
where timezone is 1 for GMT, 2 for EST, 3 for CST, 4 for MST, 5 for PST.
•
cisco22.1.1.PXM.a> cnftmzngmt <timeoffsetGMT>
where timeoffsetGMT is the offset in hours from GMT. The range of possible values for timeoffsetGMT
is -12 through +12.
Step 9
Execute the cnfstatsmgr command to specify the IP address of the workstation that runs the Cisco WAN
Manager application.
Before it sends statistics, the MGX 8230 must have the IP address of the workstation with this
application. The syntax is:
>cnfstatsmgr <IP_Addr> where IP_Addr is the IP address of the workstation.
If the node has a redundant MGX 8230-PXM, it automatically receives the same IP addresses and
configuration as the primary MGX 8230-PXM. With the IP addresses in place, you can configure the
logical ports for the broadband interface through the CiscoView application or the CLI.
Step 10
Add one or more users by executing adduser once for each new user.
Note that the access privilege level is case-sensitive as the syntax description indicates. After you enter
the privilege level, the system prompts for a new password for the user. (This password parameter does
not appear in the help information for adduser.)
adduser <user_Id> <accessLevel>
user_Id is 1–12 alphanumeric characters.
accessLevel is the case-sensitive privilege level. It can be ANYUSER or within the range
GROUP1–GROUP5. For example, to specify a privilege level 2, type GROUP2.
After you enter a user-name and privilege level, the system prompts for a password. The password is a
string of 5–15 characters. If you press Return without entering a password, the system assigns the
default password “newuser.”
Step 11
Optionally change your password or another user’s password by executing:
cnfpasswd [username]
username is the name of another user whose password you are changing. That user must have a privilege
level that is lower than your privilege. To change your own password, enter cnfpasswd with no
username.
Step 12
To specify the MGX 8230 as a feeder, execute the cnfswfunc command:
cnfswfunc <-ndtype>
and follow -ndtype with “fdr.”
Step 13
Configure as needed an external clock by executing cnfextclk.
Cisco MGX 8230 Installation and Configuration
3-16
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
Downloading Firmware to a Service Module
This section describes how to download firmware for a service module from a workstation. The
descriptions apply whether you are upgrading the existing firmware or downloading because no runtime
firmware resides on the hard drive.
Service modules do not retain runtime firmware. The hard drive on the MGX 8230-PXM may come with
default firmware for the service modules, but the details of the customer order actually determine
whether firmware is on the disk. If default firmware exists on the hard drive, the MGX 8230-PXM
downloads it upon power-up or when you reset the card, otherwise you can download firmware from
the workstation according to the instructions that follow.
Note that if you download firmware from a workstation to the hard drive, the MGX 8230-PXM does not
automatically load the firmware to the card. You must reset the card (resetcd on the CLI) to download
firmware from disk to the card. With the single execution of a command, you can load either generic
firmware for all cards of a certain type or firmware destined to a specific slot.
To load service module firmware from a workstation to the hard drive on the MGX 8230-PXM:
Step 1
Start the tftp application:
$tftp <IP address>
then
>bin
Step 2
To download generic firmware for a type of service module to the MGX 8230-PXM hard drive:
>put cardtype.fw POPEYE@SM_1_0.FW
where cardtype is the firmware for a type of card; the shelf number always is 1; and the 0 represents the
slot number for the purpose of generic download. An example of cardtype.fw is
“frsm8t1e1_10.0.11.fw.” Note the space between “.fw” and “POPEYE.”
Step 3
To load slot-specific firmware at a particular card:
>put cardtype.fw POPEYE@SM_1_slot.FW
where cardtype is the firmware, and slot is the number of the card slot. Note the space between “.fw”
and “POPEYE.” Repeat this step for each slot as needed.
Note
Slot-specific firmware overwrites the current firmware at a slot.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-17
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
With slot-specific firmware, the card does not come up if you do either of the following:
•
Specify the wrong firmware, where the firmware specified by cardtype does not match the targeted
card at slot.
•
Insert a different card (which does not use the firmware specified for the slot).
An example command for downloading specific firmware for an FRSM-2CT3 in slot 3 is:
>put frsm2ct3_10.0.01.fw POPEYE@SM_1_3.FW
where “frsm2ct3_10.0.0” refers to the firmware for the FRSM-2CT3, and “3” is the slot.
Note
See the Release Notes for current names of firmware files and release directories.
Step 4
When you have finished downloading firmware, enter quit to quit the tftp application.
Step 5
At the CLI on either the workstation or the ACSII terminal, display the firmware files. Note that the
directory specification ll c:/FW has no quote marks.
cisco22.1.1.PXM.a> ll c:/FW
Step 6
If you want to download the firmware from the disk to a card, execute resetcd.
MGX 8230 CLI Configuration of a Feeder
This section first describes how to use the CLI to configure physical and logical characteristics of the
equipment, such as physical line, logical ports, and resource partitioning. The section then describes
how to add daxcons and three-segment connections. To do these tasks, the requisite IP addresses must
have been assigned. The descriptions tell you how to:
•
Specify that the application of the MGX 8230 is a feeder to an MGX 8000 series switch.
•
At the card-level, optionally specify the total number of connections available to each network
controller (PAR, and so on).
•
Activate a line on the broadband interface of the MGX 8230-PXM—only one line for an MGX
feeder.
•
Optionally modify the characteristics of the line.
•
Create one or more logical ports on the line. Each port has associated bandwidth and VPI/VCI
ranges. By default, each controller competes for all the resources you assign to the port.
•
Optionally specify the amount of resources a network controller has on a logical port rather than
allow the controllers to compete for resources.
•
Add the MGX 8230 shelf from the MGX side.
Configuring the OC-3 Uplink
The MGX 8230-PXM uses only an OC-3 uplink back card as a feeder trunk.
Step 1
Execute the cnfswfunc command to specify the feeder application:
cnfswfunc <-vsvd enable(yes)/disable(no)> | <-ndtype>
Cisco MGX 8230 Installation and Configuration
3-18
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
Follow -ndtype with “fdr” or “routing.” The default application is routing.You can configure one option
each time you execute cnfswfunc.
Step 2
If the MGX 8230 must support the paid feature of virtual source/virtual destination (VSVD) on ABR
connections, execute cnfswfunc. The cnfswfunc syntax is:
cnfswfunc <-vsvd enable(yes)/disable(no)> | <-ndtype>
where you follow “-vsvd” with “e” or “d.”
Step 3
Optionally, modify the resource partitioning for the whole card by executing the cnfcdrscprtn
command. You can view resource partitioning through dspcdrscprtn.
cnfcdrscprtn <number_PAR_conns> <number_PNNI_conns> <number_TAG_conns>
number_PAR_conns is the number of connections in the range 0–32767 available to PAR.
number_PNNI_conns is the number of connections in the range 0–32767 available to PNNI.
number_TAG_conns is the number of connections in the range 0–32767 available to Tag.
For example, you could reserve 10,000 connections for each controller on the MGX 8230-PXM with:
cnfcdrscprtn 10000 10000 10000
In this release, there is no need to partition MGX 8230-PXM resources.
Note
Step 4
Activate the uplink line by executing addln according to the following syntax:
addln -ds3 <slot.line> | -e3 <slot.line> | -sonet <slot.line>
where:
•
-ds3 indicates a T3 line
•
-e3 indicates an E3 line
•
-sonet indicates an OC-3 or OC-12 line
•
slot is always 1 for the MGX 8230-PXM whether the active MGX 8230-PXM is in slot 1 or 2
•
line has the range 1–4 but depends on the number of lines on the uplink card
You can activate only one MGX 8230-PXM line for the feeder application.
Step 5
If necessary, you can configure line characteristics by using the cnfln command.
Step 6
Create logical ports for the physical line by executing addport once for each logical interface. (Related
commands are cnfport, dspports, and delport.)
addport <port_num> <line_num> <pct_bw> <min_vpi> <max_vpi>
port_num is the number for the logical port. The range is 1–32 for standard connections, and 34 is the
port number reserved for inband ATM PVCs for network management.
line_num is the physical line in the range 1–N. N is the number of lines on the card.
pct_bw is percentage of bandwidth. The range is 0–100. This parameter applies to both ingress and
egress.
min_vpi is the minimum VPI value. The range is 0–4095.
max_vpi is the maximum VPI value. The range is 0–4095.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-19
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
Step 7
Optionally use cnfportrscprtn to specify the resources that a controller has on a port:
cnfportrscprtn <port_no> <controller> <ingress_%BW> <egress_%BW>
<min_VPI> <max_VPI> <min_VCI> <max_VCI> <max_GLCNs>
port_no is the number for the logical port in the range 1–32 for user-connections or 34 for inband ATM
PVCs for network management.
controller is a string identifying the network controller—”PAR,” “PNNI,” or “TAG.”
ingress_%BW is the percentage of ingress bandwidth—a number in the range 0–100.
egress_%BW is the percentage of egress bandwidth—a number in the range 0–100.
min_vpi is the minimum VPI Value—a number in the range 0–4095.
max_vpi is the maximum VPI Value—a number in the range 0–4095.
min_vci is the minimum VCI Value—a number in the range 0–65535.
max_vci is the maximum VCI Value—a number in the range 0–65535.
max_chans is the maximum GLCNS—a number in the range 0–32767.
Step 8
Execute cnfifastrk to configure the port as a trunk. To change the port usage after you execute
cnfifastrk, first execute the uncnfifastrk command.
cnfifastrk <slot.port> <trunk>
Step 9
•
slot.port is the slot and port number of the line you want to serve as the trunk. Note that, whether
the active MGX 8230-PXM is in slot 1 or 2, always specify slot 1 in CLI syntax because this
parameter is a logical value.
•
trunk is the MGX 8230 application and can be either “fdr” for a feeder or “rtrk” for a stand-alone
node. Specify “fdr.”
Log in to the MGX at the other end of the feeder trunk and use the addshelf command to add the
MGX 8230 as a feeder.
CiscoView Configuration of a Feeder
This section describes how to use the CiscoView application to create and optionally modify the
characteristics of the logical ports on the MGX 8230 uplink card. It provides another way of configuring
the MGX 8230. To configure equipment on an MGX 8230, you must use Release 2.x or higher of
CiscoView. No CiscoView screen representations appear in this appendix. For a description of
CiscoView usage, see the CiscoView documentation. The task descriptions begin from the point where
you have already specified all IP addresses and the top-level CiscoView window is on-screen. The task
descriptions tell you how to:
•
Specify that the application of the MGX 8230 is a feeder to an MGX series switch.
•
At the card level, optionally specify the number of connections available to a network controller.
•
Activate and optionally modify the characteristics of a line on the broadband interface of the MGX
8230-PXM—only one line for an MGX feeder.
Cisco MGX 8230 Installation and Configuration
3-20
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
•
Create 1–32 logical ports on the line. By default, each network controller can compete for all the
resources you assign to the port.
•
Optionally specify the amount of resources each network controller has on a logical port rather than
allow the controllers to compete for resources. (Note that for this release PAR is the only network
controller using MGX 8230 resources.)
Selecting an MGX 8230
To reach the target MGX 8230:
Step 1
Click on the File option at the top of the CiscoView - Main window, then click on the Open Device
option.
Step 2
Enter the node name or IP address of the MGX 8230 in the Device Select window. When the graphical
representation of the MGX 8230 shows the cards’ faceplate features, you can begin configuration.
Step 3
You can configure features from either the front or back view of the MGX 8230. Optionally, select a
side of the MGX 8230 through the View option at the top of CiscoView - Main.
Note
If you configure MGX 8230-PXM features at the back card, select the Configure Card
options by clicking with the left mouse button on the MGX 8230-PXM back card but away
from the connectors. If you successfully select the card features, an outline of the entire
back card lights up. To select the Configure Line features, click on the back card near the
connectors. If you select the line features, an outline around the connectors lights up.
Similarly, in the front view, select either a port LED for line configuration or a nonspecific
area of the MGX 8230-PXM front card for card configuration.
Specifying the Feeder Application
To specify that the MGX 8230 operate as a feeder to an MGX 8000 series switch or to make ABR VSVD
operational on this switch:
Step 1
Click with the left mouse button on the MGX 8230-PXM so that the card outline lights up.
Step 2
Click on the Configure option at the top of the CiscoView - Main window; then click on the highlighted
“card” choice that appears under “Configure.” The Configure Card box appears. Next to the
“CATEGORY” label, the menu button shows “Card.”
Step 3
Click on Card to display the node configuration options.
Step 4
Select PAR Configuration. The Configure PAR window opens.
Step 5
Click on the menu button next to the CATEGORY field to display the PAR topics.
Step 6
Select PAR SW Configuration. The PAR Configuration box shows the defaults of “false” for VSVD and
“routing” for Node Type. Change the selection to “feeder.” If VSVD has been purchased, select the
true/false button and change the setting to “true.”
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-21
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
Step 7
Select Modify at the bottom of the box.
Step 8
Select Cancel to exit the PAR Configuration box or select another PAR topic at the menu button next to
the CATEGORY field.
Activating a Physical Line for the Uplink
To activate a line for the uplink:
Step 1
Click on the LED that corresponds to the MGX 8230-PXM line you want to activate. For the feeder
application, only port 1 is selectable. If you correctly select the LED of an inactive line, an outline of
the LED lights up. If an outline of the card lights up, you have selected the card rather than the port.
Step 2
Click on the Configure option at the top the screen then the line option in the subsequent pull-down list.
The Configure Line window appears and shows the selected line with its current characteristics.
Step 3
Change appropriate line characteristics as needed, then select the LineEnable button and change the
state to “enable.”
Step 4
Click on the Modify button to transmit any configuration changes and enable the line.
Configuring Logical Interfaces for the Feeder
To configure logical, broadband interfaces on the physical interface:
Step 1
Select the MGX 8230-PXM by clicking on the faceplate of the card. An outline of the card lights up.
Step 2
Select “Configure” then “card” at the top of the MGX 8230 graphic. The Configure Card window
appears with information on the current card.
Step 3
Click on the button next to the CATEGORY field, then select Broadband Interfaces. A matrix appears
for configuring logical interfaces on the active lines. The maximum number of user-ports is 32.
Step 4
Select the Create button to add a logical interface. A text box appears that lets you enter:
Step 5
Note
•
A number in the range 1–32 for the new logical interface
•
The port number of the physical line to which you assign the logical interface
•
A percentage of the maximum bandwidth on the line for the new logical interface
•
A minimum VPI number for the new logical interface in the range 0–4095
•
A maximum VPI number for the new logical interface in the range 0–4095
Type a value in each of the fields, then press the Apply button. The message “Addition of broadband
interface is successful” appears, otherwise an error message appears. Example errors are entries
out-of-range or values that conflict with existing configurations.
The Create window’s message of successful addition of an interface is accurate, but new
interfaces do not appear in the Configure Broadband Interfaces per Card window until you
close and reopen this window.
Cisco MGX 8230 Installation and Configuration
3-22
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Configuring an MGX 8230 MGX Feeder
Step 6
If necessary, specify additional interfaces in the matrix. You can leave the Create box open and write
over residual text or reopen this box later.
Step 7
Select the Cancel button at the bottom of the window to exit.
If you subsequently want to delete or change a logical interface:
Step 1
Open the Broadband Interfaces window.
Step 2
On the row for the targeted logical interface, move the cursor to the Status column and hold the left
mouse button down on the current status. A small menu opens with “add, “del,” and “mod” choices.
•
Select “del” to delete the interface.
or
•
Step 3
Select “mod” to change a parameter.
Select the Modify button at the bottom of the window. To see the result of any changes, close then
reopen the Broadband Interfaces window.
Partitioning Resources on the Broadband Interface
Note in this release, since PAR is the network controller controlling the MGX 8230, there is no need to
configure resources.
Configuring the Line as a Feeder Trunk
A line connected to the MGX 8230-PXM line module can function only as a feeder trunk in this release.
In addition to configuring the use of the trunk at the MGX 8230, you must also configure the trunk at
the far-end MGX.
To configure the trunk for the feeder application at the near-end:
Step 1
Open the Configure Card window.
Step 2
For the CATEGORY, select PAR Configuration.
Step 3
In the PAR Configuration window, select PAR Interface. In the PAR Interface window, the only
configurable column is the PAR Interface Type.
Step 4
For the logical interface type—1 for the feeder trunk—hold the left mouse button down in the PAR
Interface Type column for this logical interface. The choices are “feedertrunk” and “routing trunk.”
Step 5
Select “feedertrunk,” then click on the modify button at the bottom of the screen.
Step 6
Log in to the MGX at the other end of the feeder trunk and use the addshelf command to add the MGX
8230 as a feeder.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-23
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Adding Service Module Connections
This section contains a general description of the sequence of tasks for configuring service modules
(FRSM, AUSM, CESM) and the services they support and the available services (ATM, Frame Relay,
or circuit emulation). It also contains details on how to configure resource partitions and add local
connections and three-segment connections. Detailed descriptions of these tasks for individual service
modules appear in subsequent sections.
Although many of the configuration and connection tasks can be done with either Cisco WAN Manager
(CWM) and CiscoView network management applications, this appendix uses the MGX 8230 command
line interface commands in its examples. Refer to the appropriate CWM 9.2.xx and CiscoView 2.xx
documentation for information about using those applications with the MGX 8230.
Connections on a Feeder
The MGX 8230 MGX feeder can support local connections (daxcons) and three-segment connections
across the network. How you add connections depends on the technology of the service module, which
card is the master or slave end of the connection, and whether the connection is a daxcon or part of a
three-segment connection. The following rules govern connection addition in an MGX 8230 feeder.
The descriptions of connection addition later in this section reflect these rules:
1.
If the MGX 8230-PXM is an endpoint, it functions as the slave. The service module is the master
end.
2.
For a daxcon, you first add the connection at the slave end then add it at the master end. Further,
when you start by adding a connection at the slave end, the system generates the remote (master)
connection ID for you. The remote connection ID contains required information for adding the
connection at the master end.
3.
For a three-segment connection, you start the segment by adding a connection at the master end. In
this case, you specify the connection ID of the slave end of the segment and subsequently use that
information for adding the connection at the slave end.
4.
If the remote termination is an MGX 8230-PXM on the other side of a network cloud, specify the
slot number as “0.” (This requirement applies to only the feeder application of the MGX 8230.)
Modifying the Resource Partitioning
A resource partition on a card consists of a percentage of bandwidth, a DLCI or VPI/VCI range, and
the number of logical connection numbers (LCNs) available to a network control application. On the
MGX 8230-PXM, the connections are global logical connections (GLCNs). By default, all resources on
a logical interface are available to any controller on a first-come, first-served basis. If necessary, you
can modify the resources for a controller at the card level and logical port level. Port-level resource
modification follows card-level modification, so the available port-level resources depend on whether
and how much you change the card-level resource partitioning. You do not have to change the resource
partitioning for the card before changing resource partitioning for a port.
The current network control application is Portable AutoRoute (PAR). Planning considerations should
include the possibility of modifying the partitioning of resources for the interface. For example, the
MGX 8230 has the capacity to support a Cisco Multi-Protocol Label Switching (MPLS) controller or a
Private Network to Network Interface (PNNI) controller.
Cisco MGX 8230 Installation and Configuration
3-24
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Note
There is no need to partition MGX 8230 service module resources in this release of the
MGX 8230 MGX feeder.
Sequence of Configuration Tasks
In a new MGX 8230, the common approach is to configure the same aspect for all cards at once—adding
logical ports, for example. In contrast, the likely sequence for installing a new or replacement card is
to begin with the card-level features and continue until you have added every connection. The common
tasks for a new MGX 8230 are:
1.
Activate physical lines.
2.
Optionally configure the line if default parameters are not appropriate.
3.
Create the logical ports then modify as needed the logical ports.
4.
Optionally configure resource partitions for a logical port if the default partitioning does not
support the intended operation of the port. (With this release of MGX 8230 MGX feeder, there is
no need to partition resources.)
5.
Add connections, then modify as needed individual connections.
Rules for Adding Connections
This section describes the rules for adding local connections, three-segment connections, and
management connections. The MGX 8230 can support
•
Local-only, digital access cross-connect (DAX) connections
•
Three-segment connections across an ATM or Frame Relay network
As a preface to the steps for adding connections, this section describes the applicable rules for these
connections. Although the rules include references to CLI syntax, they also apply to the Cisco WAN
Manager application.
Rules for Adding a DAX Connection
A DAX con is a connection whose endpoints for the entire connection exist on the same MGX 8230.
The following apply to the MGX 8230:
1.
On a feeder, a DAX con can exist between different service modules or within the same service
module.
2.
A stand-alone node supports DAX cons with one or both endpoints on the MGX 8230-PXM in
addition to DAX cons between service modules.
3.
Either endpoint can be the master.
4.
The first endpoint to add is the slave. The generic syntax is:
addcon <local parameters>
where local parameters are the port, DLCI or VPI and VCI, and mastership status. Slave is the
default case, so you actually do not have to specify it. When you press Return, the system returns
an identifier for this connection. The identifier includes the port and DLCI or VPI and VCI.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-25
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Use the returned identifier to specify the slave endpoint when you subsequently add the connection
at the master end. The slave endpoint is specified as the remote parameters in item 5.
5.
To complete the DAX con, add the master endpoint. The generic syntax is
addcon <local parameters> <remote parameters>
where local parameters are the port, DLCI or VPI and VCI, and mastership status (master in this
case). The remote parameters are the items in the connection identifier that the system returned
when you added the slave endpoint.
6.
If the endpoint is a MGX 8230-PXM port in a stand-alone node, specify the slot as 0. The addcon
command is the only command in which you specify the slot number for the MGX 8230-PXM as 0.
Rules for Adding Three-Segment Connections
A three-segment connection consists of a local segment on each MGX 8230 at the edges of the network
cloud and a middle segment across the network cloud. Figure 3-6 illustrates a three-segment Frame
Relay connection. The MGX 8230 requirements are:
1.
For MGX 8230 feeders, the backbone must consist of MGX 8000 series or BPX 8600 series
switches.
2.
On a feeder, the local segment exists between a service module and the MGX 8230-PXM.
3.
On a stand-alone node, the local segment can be between a service module and the uplink port on
the MGX 8230-PXM.
4.
For the local segment, add the connection at only the master endpoint. The generic syntax is:
addcon <local parameters> <remote parameters>
where local parameters are the port, DLCI or VPI and VCI, and mastership status (master in this
case). The remote parameters are the current nodename, slot, port, and VPI and VCI of the slave
end. For the MGX 8230-PXM endpoints, specify the slot number as 0. The addcon command is the
only command in which you specify the slot number for the MGX 8230-PXM as 0.
Figure 3-6
Frame Relay Connection Through an MGX 8230/MGX/BPX Network
Segment 1
Segment 2
Customer Equipment to
MGX 8230 to IGX switch
Segment 3
Customer Equipment to
MGX 8230 to IGX switch
IGX/BPX network
A
B
MGX/
BPX
T1
Channel
Port
F
R MGX
S 8230
M
MGX/
BPX
Port
T1
B
Channel
MGX/BPX Backbone
Network
38380
A
F
MGX R
8230 S
M
Cisco MGX 8230 Installation and Configuration
3-26
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Redundancy Support by the MGX-SRM-3T3/B
The MGX-SRM-3T3/B can provide redundancy to service modules with T1 or E1 lines. For E1 or T1
modules, it can provide redundancy through the redundancy bus. For T1 modules only, it can provide
redundancy through the distribution bus. The redundancy and distribution buses impose different
requirements, but the common requirement is that all primary and secondary cards supported by a
particular MGX-SRM-3T3/B must reside on the same level of the card cage as the SRM.
The need for back cards and the choice of bus for redundancy support depends on whether the
MGX-SRM-3T3/B must provide bulk distribution:
•
With bulk distribution, the T1 service modules do not use back cards. The MGX-SRM-3T3/B uses
the distribution bus to support redundancy.
•
Without bulk distribution, the supported service modules must have back cards. The redundant card
set requires a special redundancy back card (the R-RJ48-8T1 or R-RJ48-8E1). The primary card
sets use standard back cards (RJ48-8T1 or RJ48-8E1).
With redundancy provided by the SRM, no Y-cables are necessary because the MGX-SRM-3T3/B itself
passes the traffic to the redundant front card if a failure necessitates switchover. Conversely, any card
with 1:1 redundancy supported by Y-cabling does not require an SRM. For example, the FRSM-VHS
cards have 1:1 redundancy through a Y-cable. The MGX-SRM-3T3/B redundancy feature is particularly
important for cards that do not have Y-cable redundancy—the T1 and E1 service modules.
Configuring Redundancy Through the Redundancy Bus
For redundancy that utilizes the redundancy bus, the characteristics are:
•
Both the primary and the redundant front cards must have back cards. The secondary back card
must be the version specifically designed to be redundant cards. Examples are the R-RJ48-8T1 and
R-RJ48-8E1, where the first “R” means redundant.
•
An MGX-SRM-3T3/B can redirect traffic for only one failed card at a time regardless of the number
of redundant groups you have configured to rely on that MGX-SRM-3T3/B for redundancy.
To configure redundancy through the redundancy bus:
Step 1
Execute addred on the active PXM1:
addred <redPrimarySlotNum> <redSecondarySlotNum> <RedType>
where:
redPrimarySlotNum
is slot number of the slot containing the primary card.
The slot numbers are 1–6, 9–14, 17–22, and 25–30.
redSecondarySlotNum
is slot number of the slot containing the secondary card
of the card pair. The ranges are 1–6, 9–14, 17–22, and
25–30.
RedType
is a number that specifies the type of redundancy. Enter
a 1 to specify 1:1 redundancy. Enter a 2 to specify 1:N
redundancy. Only an SRM can support 1:N redundancy.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-27
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Step 2
Check the redundancy status for all cards by using dspred.
To remove redundancy, use delred.
ATM Universal Service Module Connections
The 8-port ATM Universal Service Module (MGX-AUSM/B-8T1 and MGX-AUSM/B-E1) is a
multipurpose card set with eight T1 or E1 lines that support:
•
ATM UNI with high port-density for the CPE—with AUSMs in all 24 service module slots, an
MGX 8230 can support up to 192 individual T1 or E1 lines. An individual card set can support 1000
data connections and 16 management connections.
•
Inverse multiplexing for ATM (IMA) that complies with ATM Forum v3.0, v3.1, and v4.0—the
8-port AUSM can provide N x T1 or N x E1 logical ports up to maximum rates of 12 Mbps for T1
or 16 Mbps for E1.
•
Classes of service—CBR, VBR, ABR, and UBR with per-VC queuing on ingress and multiple
class-of-service queues on egress.
•
Statistics collection.
•
Virtual path connections (VPCs).
•
Network synchronization derived from one of its lines.
•
BERT functionality with loopback pattern generation and verification on individual lines.
•
Automatic card-restore.
•
SNMP and TFTP to support card and connection management.
•
Resource partitions for individual network control applications (not needed in this release).
Using the CLI to Configure the Card, Lines, and Ports
You can activate and configure the card, the lines, and the ports on the AUSM-series cards through the
CiscoView application or the CLI. To perform connection-related tasks, use the Cisco WAN Manager
application or the CLI. Refer to the documentation for these applications for task descriptions. Use the
commands described in this section to:
•
Optionally modify resource partitioning at the card-level
•
Activate and configure a line
•
Create and configure a logical port
•
Optionally modify resource partitioning at the port level
•
Configure usage parameters
•
Configure queue depths
•
Configure the ForeSight feature
•
Configure a line as a clock source
Cisco MGX 8230 Installation and Configuration
3-28
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
On the MGX 8230 CLI of the AUSM:
Step 1
If necessary, modify the resource partitioning for the whole card by executing the cnfcdrscprtn
command. You can view resource partitioning through dspcdrscprtn.
cnfcdrscprtn <number_PAR_conns | number_PNNI_conns | number_TAG_conns>
•
number_PAR_conns is the number of connections in the range 0–1000 for PAR.
•
number_PNNI_conns is the number of connections in the range 0–1000 for PNNI.
•
number_TAG_conns is the number of connections in the range 0–1000 for MPLS.
For example, you could reserve 300 connections for each controller on the AUSM with:
cnfcdrscprtn 300 300 300
Step 2
Activate a physical line by using addln for each of the eight lines as needed:
addln <line_number>
Step 3
Optionally, use the cnfln command to specify line coding, line length, and clock source:
cnfln <line_num> <line_code> <line_len> <clk_src> [E1-signaling]
Step 4
Execute upport to activate the logical operation of the line:
upport <port_number>, where port_number is in the range 1–8.
Step 5
If necessary, execute cnfportq to modify the egress queues:
cnfportq <port_num> <q_num> <q_algo> <q_depth> <clp_high> <clp_low> <efci_thres>
port_num
is the logical port number in the range 1–8.
q_num
is the queue number in the range 1–16. 0 is the default for addchan.
1=CBR
2=VBR
3=ABR
4=UBR
q_algo
is a number to specify the queue algorithm:
0=disable queue
1=high priority—always serve
2=best available
3=minimum guaranteed bandwidth
4=minimum guaranteed bandwidth with maximum rate shaping
5=CBR with smoothing
q_depth
is the maximum queue depth in the range 1–16000 cells
clp_high
clp high is the high Cell Loss Priority in the range 1–16000 cells
clp_low
clp low is the low Cell Loss Priority in the range 1–16000 cells
efci_thres
efci threshold is the EFCI threshold in the range 1–16000 cells
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-29
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Step 6
If necessary, configure resources at the port level by executing cnfportrscprtn. Use dspportrscprtn to
see the current resource partitioning.
cnfportrscprtn <port_num> <controller> <ingress_%BW> <egress_%BW> <number_of_cons>
<VPImin/VPImax> [VCImin/VCImax]
•
port_num is the port number in the range 1–8.
•
controller is a number representing the controller: 1=PAR, 2=PNNI, and 3=MPLS.
•
ingress_%BW is the percentage of ingress bandwidth in the range 0–100.
•
egress_%BW is the percentage of egress bandwidth in the range 0–100.
•
number_of_cons is the maximum number of connections on the port.
•
VPImin/VPImax is the minimum and maximum VPI numbers.
•
VCImin/VCImax is the optional specification for VCI range.
Using the CLI to Configure Inverse Multiplexing
Use the following command sequence for configuring the IMA feature:
Step 1
addln on all constituent links.
Step 2
cnfln if necessary.
Step 3
addimagrp (or addaimgrp) to create the IMA group by using the following syntax:
addimagrp <group_num> <port_type> <list_of_links> <minNumLink>
group_num
is a number for IMA group. The range is 1–8.
port_type
is the port type: 1=UNI, 2=NN1.
list_of_links
is the list of links to be included in the group. Separate each link
number by a period.
minNumLink
is the minimum number of links in the range 1–8 to form a group.
For example: the following creates IMA group 1 with lines 3, 4, and 5. The minimum is 3.
addimagrp 1 3.4.5 3
IMA-related commands are dspimagrp, dspimagrpcnt, dspimagrps, dspimainfo, and dspimalncnt.
Refer to the Cisco MGX 8250 Command Reference for descriptions.
Cisco MGX 8230 Installation and Configuration
3-30
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Adding and Configuring Connections on the AUSM/B
You can add and modify connections through the Cisco WAN Manager or the CLI. Refer to applicable
documentation if you use the WAN Manager application. This section describes how to add an ATM
connection through the CLI according to the rules for adding a standard connection or a management
connection in the form of either a DAX con or a three-segment connection. See “Rules for Adding
Connections” earlier in this chapter.
On the CLI of the AUSM/B:
Step 1
Execute the addcon command.
When you add a connection with addcon, the system automatically assigns the next available channel
number, so addcon does not require it. However, some related commands require a channel
number—cnfchanfst, cnfchanq, and cnfupcabr, for example. To see the channel number after you add
a connection, use dspcons.
The addcon syntax is:
addcon <port_number> <vpi> <vci> <ConType> <SrvType> [Controller_Type] [mastership]
[remoteConnID]
port number
port number is in the range 1–8.
vpi
vpi has a value in the range 0–255.
vci
vci can be in the range 0–65535 for a VCC or * for a VPC.
Conn type
is the connection type: 0=VCC, and non-0 is the local ID of a
VPC in the range 1–1000.
Service Type
is the service type: 1=CBR, 2=VBR, 3=ABR, and 4=UBR.
mastership
is the mastership status of the endpoint. 1=master, and 2=slave.
The default is slave, so you actually do not need to type a 2.
Controller_Typ is the optional controller specification. 1=PAR (the default}.
e
2=SPVC (PNNI).
connID
Step 2
is entered at only the master end and consists of the node name,
slot number, port number, vci, and vpi of the slave end.
To configure usage parameter control (UPC) for the connection (channel), use cnfupccbr, cnfupcvbr,
cnfupcabr, or cnfupcubr. Use dspcons to obtain the channel number.
cnfupccbr <port.vpi.vci> <enable/disable> <pcr[0+1]> <cdvt[0+1]> <IngPcUtil> <EgSrvRate>
<EgPcUtil>
port.vpi.vci
identifies the connection.
enable/disable is the UPC enable: 1=disable, 2=enable.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-31
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
pcr[0+1]
is the peak cell rate. Without IMA, the range is as follows:
T1, 10–3622 cells per second
E1, 10–4528 cells per second
clear E1, 10–4830 cells per second
For IMA, multiply the line rate by the number of links.
cdvt[0+1]
is the cell delay variation tolerance for cells with CLP=0 and
CLP=1. The range is 1–250000 microseconds.
IngPcUtil
is the percent utilization on the ingress. The range is 1–127. The
default is 0.
EgSrvRate
is the egress service rate. Without IMA, the range is as follows:
T1, 10–3622 cells per second
E1, 10–4528 cells per second
clear E1, 10–4830 cells per second
For IMA, multiply the line rate by the number of links
EgrPcUtil
is the percent utilization on the egress. The range is 1–127.
The default is 0.
cnfupcvbr has the same syntax and parameters as cnfupcabr <port.vpi.vci> <enable> <pcr[0+1]>
<cdvt[0+1]> <scr> <scr_police> <mbs> <IngPcUtil> <EgSrvRate> <EgPcUtil> <clp_tag>
port.vpi.vci
identifies the connection.
enable
is the enabled/disable for UPC: 1=Disable, 2=Enable.
pcr
is the peak cell rate. Without IMA, the range is as follows:
T1, 10–3622 cells per second
E1, 10–4528 cells per second
clear E1, 10–4830 cells per second
For IMA, multiply the line rate by the number of links.
cdvt
cdvt[0+1] is the cell delay variation tolerance for cells with
CLP=[0+1]. The range is 1–250000 microseconds.
scr
is the peak cell rate. Without IMA, the range is as follows:
T1, 10–3622 cells per second
E1, 10–4528 cells per second
clear E1, 10–4830 cells per second
For IMA, multiply the line rate by the number of links.
scr_police
specifies the type of scr policing: 1= CLP[0] cells,
2=CLP[0+1] cells, and 3=no SCR policing.
mbs
is the maximum burst size: the range is 1–5000 cells.
Cisco MGX 8230 Installation and Configuration
3-32
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
IngPcUtil
is the percent utilization on the egress. The range is 1–127.
Default=0.
EgSrvRate
is the egress service rate. Without IMA, the range is as follows:
T1, 10–3622
E1, 10–4528
clear E1, 10–4830
For IMA, multiply the line rate by the number of links
EgrPcUtil
is the percent utilization on the ingress. The range is 1–127.
Default=0.
clp_tag
is the enable for CLP tagging: 1=disable, 2=enable.
cnfupcubr <port.vpi.vci> <enable> <pcr[0+1]> <cdvt[0+1]> <IngPc> <util> <clp_tag>
port.vpi.vci
identifies the connection.
enable
is the enabled/disable for UPC: 1=Disable, 2=Enable.
pcr
is the peak cell rate. Without IMA, the range is as follows:
T1, 10–3622
E1, 10–4528
clear E1, 10–4830
For IMA, multiply the line rate by the number of links.
cdvt
cdvt[0+1] is the cell delay variation tolerance for cells with
CLP=[0+1]. The range is 1–250000 microseconds.
scr
is the peak cell rate. Without IMA, the range is as follows:
T1, 10–3622
E1, 10–4528
clear E1, 10–4830
For IMA, multiply the line rate by the number of links.
Step 3
scr_police
specifies the type of scr policing: 1= CLP[0] Cells,
2=CLP[0+1] cells, and 3=no SCR policing.
mbs
is the maximum burst size: the range is 1–5000 cells.
IngPc
is the percent utilization on the ingress. The range is 1–127.
Default=0.
clp_tag
is the enable for CLP tagging: 1=disable, 2=enable.
If the system has the ForeSight feature, use cnfchanfst to configure it.
cnfchanfst <port.vpi.vci> <enable> <fgcra_enable> <ibs> <pcr> <mcr> <icr>
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-33
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
port.vpi.vci
identifies the connection.
enable
is the enabled/disable for the ForeSight feature: 1=disable,
2=enable.
fgcra_enable
is the enabled/disable for the frame-based generic cell rate
algorithm: 1=disable, 2=enable.
ibs
is the initial burst size in the range 0–5000 cells.
pcr
is the peak cell rate for the connection. Without IMA, the range
is as follows:
T1, 10–3622
E1, 10–4528
clear E1, 10–4830
For IMA, multiply the line rate by the number of links.
mcr
is the minimum cell rate for the connection. Without IMA, the
range is as follows:
T1, 0–3622
E1, 0–4528
clear E1, 0–4830
For IMA, multiply the line rate by the number of links.
icr
is the initial cell rate. Without IMA, the range is as follows:
T1, 0–3622
E1, 0–4528
clear E1, 0–4830
For IMA, multiply the line rate by the number of links.
Step 4
If necessary, change the queue depths by using cnfchanq.
cnfchanq <port.vpi.vci> <discard_option> <vc_q_depth> <clp_thresh_high> <clp_thresh_low |
epd_threshold> <efci_thresh>
Cisco MGX 8230 Installation and Configuration
3-34
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
port.vpi.vci
identifies the connection.
discard_option
is either 1 for clp hysteresis or 2 for frame-based.
vc_q_depth
is the ingress queue depth in the range 1–16000 cells.
clp_thresh_high
is the CLP high threshold in the range 1–16000 cells.
clp_thresh_low
is the CLP low threshold in the range 1–16000 cells for
CLP hysteresis-based discard.
or
or
epd_threshold
is the EPD threshold in the range 1–16000 cells
frame-based discard.
efci_thresh
is the EFCI threshold in the range 1–16000 cells.
Adding the Middle Segment of the Connection
For the middle segment, be sure to use the same connection type as the local segments on the MGX
8230 (CBR, VBR, ABR, or UBR). The parameters directly map from those specified at the connection
endpoint.
Frame Relay Service Module Connections
This section describes the features available on each of the Frame Service Modules (FRSMs). For
descriptions of how to set up these cards and add connections, see the subsequent section titled
“Configuring Frame Relay Service.” The section consists of:
•
Brief descriptions of each model of the FRSM
•
Lists of features shared by all FRSMs
•
Lists of features for each model of the FRSM
•
Brief descriptions of the services
The models of the FRSM include 8-port T1 and E1 cards and high-speed modules. The higher speed
modules support unchannelized E3 and HSSI as well as channelized and unchannelized T3.
The primary function of all FRSM models is to convert between the Frame Relay-formatted data and
ATM/AAL5 cell-formatted data. For individual connections, you can configure the card to perform
network interworking (NIW), service interworking (SIW), ATM to Frame Relay UNI (FUNI), or frame
forwarding. An FRSM converts the header format and translates the address for:
•
Frame Relay port number and DLCI
•
ATM-Frame UNI (FUNI) port number and frame address or frame forwarding port
•
ATM virtual connection identifiers (VPI/VCIs)
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-35
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Very High Speed Frame Service Modules
The Very High Speed Frame Service Modules (FRSM-VHS) support Frame Relay services on T3, E3,
and HSSI interfaces. Up to 8 FRSM-VHS cards in any combination can operate in the MGX 8230. The
FRSM-VHS group on an MGX 8230 consists of:
•
MGX-FRSM-2CT3, which provides channelized Frame Relay service for up to 1000 user
connections over two T3 lines on the BNC-2T3 back card (or line module).
•
MGX-FRSM-2T3E3, which provides unchannelized (clear-channel) Frame Relay service for up to
1000 user connections over two T3 lines (44.736 Mbps each) or two E3 lines (34.368 Mbps each)
on a BNC-2T3 or BNC-2E3 back card. The MGX-FRSM-2T3E3 can also support subrate T3 or E3
for tiered DS3 on each physical port.
•
MGX-FRSM-HS2, which provides unchannelized Frame Relay service for up to 1000
user-connections over two HSSI lines on the SCSI2-2HSSI back card. The maximum rate for the
card is 70 Mbps. Each port can operate either as DTE or DCE with incremental rates of NxT1 or
NxE1 up to 52 Mbps.
Eight-Port Channelized and Unchannelized Frame Service Module
The AX-FRSM-8T1 and AX-FRSM-8E1 provide unchannelized Frame Relay service for up to 1000
user-connections on eight T1 or E1 lines. The AX-FRSM-8T1c and AX-FRSM-8E1c provide
channelized Frame Relay service for up to 1000 connections.
Frame Service Module Features
This section first lists the features common to all FRSM models then lists the features of each model.
All FRSMs support:
•
Frame Relay-to-ATM Network Interworking (NIW) as defined in FRF.5.
•
Frame Relay-to-ATM Service Interworking (SIW) with or without translation as in FRF.8.
•
Frame forwarding.
•
ATM Frame-UNI.
•
Maximum frame sizes of 4510 bytes for Frame Relay and 4096 bytes for ATM-FUNI.
•
Per-virtual-circuit (VC) queuing in the ingress direction (towards the cell bus). Traffic arriving at
the network on a connection has a dynamically assigned buffer at the entrance to the MGX 8230.
Buffer size depends on the amount of traffic and the service-level agreement (SLA).
•
Advanced buffer management. When a frame arrives, the depth of the queue for the LCN is
compared against the peak queue depth scaled down by a specified factor. The scale-down factor
depends on the amount of congestion in the free buffer pool. As the free buffer pool begins to empty,
the scale-down factor is increased, preventing an excessive number of buffers from being held up
by any single LCN.
•
Multiple, priority-level queuing to support class of service on the egress. The FRSM services egress
queues according to a weighted priority. The priority depends on the percentage of logical port
bandwidth needed by all connections of a particular type on a port. The FRSM supports
– High-priority queue
– Real-time Variable Bit Rate (rt-VBR) queue
– Common queue for non-real-time Variable Bit Rate (nrt-VBR) and ABR connections
– UBR queue
Cisco MGX 8230 Installation and Configuration
3-36
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
•
Initial burst per channel. After a period of silence, the FRSM sends a configurable number of bytes
at a peak service rate.
•
The ForeSight option. This Cisco mechanism for managing congestion and optimizing bandwidth
continuously monitors the utilization of ATM trunks. It proactively adjusts the bandwidth for
connections to avoid queuing delays and cell discards.
•
Consolidated Link Layer Management (CLLM), an out-of-band mechanism to transport
congestion-related information to the far end.
•
Dual leaky bucket policing. Within the basic parameters such as committed burst, excess burst, and
CIR, incoming frames go into two buckets: those to be checked for compliance with the committed
burst rate and those to be checked for compliance with the excess burst rate. Frames that overflow
the first bucket go into the second bucket. The buckets “leak” by a certain amount to allow for
policing without disruption or delay of service.
•
Standards-based management tools. Each FRSM supports SNMP, TFTP for configuration and
statistics collection, and a command line interface. The Cisco WAN Manager application provides
full graphical user interface support for connection management. The CiscoView application
provides equipment management.
•
MGX 8800 series and MGX 8230 network management functions, including image download,
configuration upload, statistics, telnet, UI, SNMP, trap, and MIBs.
•
OAM features: OAM F5 AIS, RDI, end-to-end or segment loopback as well as LMI and Enhanced
LMI (ANNEX A, ANNEX D, Strata LMI).
•
Hot swappable redundancy (see sections for individual implementations).
•
CLLM (router ForeSight and NNI ForeSight operation).
•
Resource partitioning at the card level or port level (not needed in this release).
MGX-FRSM-2CT3 Features
The specific features are:
•
Up to 1000 user-connections
•
Two T3 lines
•
Up to 256 logical ports
•
Logical port speed from DS0 56 Kbps through DS1 1.536 Mbps
•
Support for five Class of Service (CoS) queues (high priority, rt-VBR, nrt-VBR, ABR, UBR)
•
1:1 redundancy through Y-cable redundancy (no Service Resource Module required)
MGX-FRSM-2T3E3 Features
The specific features are:
•
Up to 1000 user-connections
•
Two T3 or E3 lines coinciding with two logical ports
•
ADC Kentrox and Digital Link methods for supporting fractional T3 or E3 ports
•
Maximum possible number of DLCIs per port by using the Q.922 two-octet header format
•
Support for five Class of Service (CoS) queues (high priority, rt-VBR, nrt-VBR, ABR, UBR)
•
1:1 redundancy through Y-cable redundancy (no Service Resource Module required)
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-37
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
•
Fractional T3 speeds available through either the Digital Link or ADC Kentrox method
MGX-FRSM-HS2 Features
The specific features are:
•
Up to 1000 user-connections
•
Maximum of two logical ports
•
Two HSSI lines with configurable line speeds in multiples of 56 Kbps or 64 Kbps
•
Selectable DTE or DCE mode for each port
•
In DCE mode, per port clock speeds of NxT1 and NxE1 up to 52 Mbps
•
Various DTE/DCE loopback operations
•
Maximum possible number of DLCIs per port by using the Q.922 two-octet header format
•
1:1 redundancy through a Y-cable
Eight-Port FRSM Features
The specific features are:
•
Up to 1000 user-connections.
•
Fractional FRSMs support a single 56-Kbps or multiple 64-Kbps user-ports (FR-UNI, FR-NNI,
FUNI, and frame forwarding) per T1 or E1 line. Channelized FRSMs (AX-FRSM-8T1c and
AX-FRSM-8E1c) support multiple 56 Kbps or N x 64 Kbps user-ports per line up to the physical
line bandwidth limit.
•
If the FRSM uses an SMB-8E1 back card, 1:1 redundancy is available through Y-cabling.
Frame Relay-to-ATM Network Interworking
FR-ATM network interworking (NIW), illustrated in Figure 3-7, supports a permanent virtual
connection (PVC) between two Frame Relay users over a Cisco network or a multi-vendor network. The
traffic crosses the network as ATM cells. To specify NIW for a connection, add the connection with a
channel type of “network interworking.”
MGX 8230/MGX/BPX Network with NIW Connections
Frame Relay
FRAD
DS1
(router)
FRSM
BPX network
MGX
8230
MGX/
BPX
Frame Relay
DS1
MGX/
BPX
PVCs
MGX/
BPX
MGX
8230
FRSM
MGX
8230
FRSM
Frame Relay
DS1
FRAD
(router)
FRAD
(router)
38381
Figure 3-7
Cisco MGX 8230 Installation and Configuration
3-38
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
In addition to frame-to-cell and DLCI-to-VPI/VCI conversion, the NIW feature maps cell loss priority
(CLP) and congestion information from Frame Relay-to-ATM formats. Subsequent sections contain the
details. You can modify the CLP and congestion indicators for individual connections.
Congestion Indication for NIW Connections
You can modify the CLP and congestion parameters for individual connections. On the CLI, use the
cnfchanmap command. In the Frame Relay-to-ATM direction, you can configure each Frame
Relay-ATM NIW connection for one of the following CLP-to-DE mapping schemes:
•
DE bit in the Frame Relay frame is mapped to the CLP bit of every ATM cell generated by the
segmentation process.
•
CLP is always 0.
•
CLP is always 1.
In the ATM-to-Frame Relay direction, you can configure each Frame Relay/ATM NIW connection for
one of the following CLP-to-DE mapping schemes:
•
If at least one ATM cell from a frame has CLP=1, the DE field of the Frame Relay frame is set.
•
No mapping from CLP to DE.
Congestion on the Frame Relay/ATM network interworking connection is flagged by the EFCI bit. The
EFCI setting depends on the direction of the traffic. In the Frame Relay-to-ATM direction, EFCI is
always set to 0. In the ATM-to-Frame Relay direction, the FECN bit of the Frame Relay frame is set if
the EFCI field in the last received ATM cell of a segmented frame is set.
PVC Status Management
The management of ATM layer and FR PVC status management can operate independently. The PVC
status from the ATM layer is used when determining the status of the FR PVC. However, no direct
actions of mapping LMI A bit to OAM AIS is performed.
Frame Relay-to-ATM Service Interworking
By specifying a service interworking (SIW) channel type when you add a Frame Relay PVC to an
FRSM, all data is subject to SIW translation and mapping in both the Frame Relay-to-ATM and
ATM-to-Frame Relay directions. Figure 3-8 is an illustration of typical SIW connections.
MGX 8230/MGX/BPX Network with SIW Connections
BPX network
T1 or E1
ATM FUNI CPE
FRSM
AUSM
ATM CPE
T1 or E1
MGX
8230
MGX
switch
MGX
switch
MGX
8230
FRSM
FR UNI
CPE
PVCs
38383
Figure 3-8
In addition to frame-to-cell and DLCI-to-VPI/VCI conversion, SIW maps cell loss priority and
congestion data between the Frame Relay and ATM formats and is FRF.8-compliant. It provides full
support for routed and bridged PDUs, transparent and translation modes, and VP translation.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-39
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Cell Loss Priority
In addition to frame-to-cell and DLCI-to-VPI/VCI conversion, the SIW feature maps cell loss priority
(CLP) and congestion information from Frame Relay-to-ATM formats.
You can modify the CLP and congestion parameters for individual connections. On the CLI, use the
cnfchanmap command. In the Frame Relay-to-ATM direction, you can specify one of the following
discard eligibility (DE)-to-cell loss priority (CLP) schemes for an individual SIW connection:
•
DE bit in the Frame Relay frame is mapped to the CLP bit of every ATM cell generated by frame
segmentation.
•
CLP is always 0.
•
CLP is always 1.
In the ATM-to-Frame Relay direction, you can specify a CLP-to-DE mapping scheme for an individual
connection:
•
If one or more ATM cells belonging to a frame has CLP=1, the DE field of the Frame Relay frame
is set.
•
DE is always 0.
•
DE is always 1.
Congestion Indication
This section describes congestion indictors. You can modify the CLP and congestion indicators for
individual connections. On the CLI, use the cnfchanmap command. In the Frame Relay-to-ATM
direction, you can configure a Frame Relay-to-ATM SIW connection for one of the following Forward
Explicit Congestion Notification (FECN)-to-Explicit Forward Congestion Indicator (EFCI) schemes:
•
FECN bit in the Frame Relay frame is mapped to the EFCI bit of every ATM cell generated by the
segmentation process of the frame.
•
EFCI is always 0.
•
EFCI is always 1.
In the ATM-to-Frame Relay direction, service interworking connections use the following EFCI to
FECN/BECN mapping schemes:
•
If the EFCI bit in the last ATM cell of a segmented frame received is set to 1, the FECN of the Frame
Relay frame is set to 1.
•
BECN is always set to 0.
Command and Response Mapping
The FRSM provides command and response mapping in both directions:
•
In the Frame Relay-to-ATM direction, the FRSM maps the C/R bit of the received Frame Relay
frame to the CPCS-UU least-significant bit of the AAL5 CPCS PDU.
•
In the ATM-to-Frame Relay direction, the FRSM maps the least-significant bit of the CPCS-UU to
the C/R bit of the Frame Relay frame.
Cisco MGX 8230 Installation and Configuration
3-40
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Translation and Transparent Modes
Each service interworking (SIW) connection can exist in either translation or transparent mode. In
translation mode, the FRSM translates protocols between the FR NLPID encapsulation (RFC 1490) and
the ATM LCC encapsulation (RFC 1483). In transparent mode, the FRSM does not translate.
Translation mode support includes address resolution by transforming address resolution protocol
(ARP, RFC 826) and inverse ARP (inARP, RFC 1293) between the Frame Relay and ATM formats.
Frame Forwarding
You can configure an individual port for frame forwarding. Frame forwarding is the same as standard
Frame Relay except that the FRSM:
•
Does not interpret the 2-byte Q.922 header.
•
Maps all received frames to a specific connection if it exists, otherwise it discards the frames.
•
Does not map between DE and CLP or between FECN and EFI.
•
Does not support statistics for “Illegal header count” or “Invalid DLCI.”
•
Does generate statistics for “Discarded frame count due to no connection.”
ATM Frame-to-User Network Interface
All FRSMs support the ATM Frame User-to-Network Interface (FUNI). When a frame arrives from the
FUNI interface, the FRSM removes the 2-byte FUNI header and segments the frame into ATM cells by
using AAL5. In the reverse direction, the FRSM assembles ATM cells from the network into a frame
by using AAL5, adds a FUNI header to the frame, and sends it to the FUNI port.
Loss Priority Indication
The FRSM maps the loss priority indication for both directions:
•
In the FUNI-to-ATM direction, the FRSM maps the CLP bit in the FUNI header to the CLP bit of
every ATM cell that it generates for the FUNI frame.
•
In the ATM-to-FUNI direction, the FRSM always sets the CLP bit in the FUNI header to 0.
Congestion Indication
The FRSM maps congestion indication in both directions:
•
In the FUNI-to-ATM direction, it sets EFCI to 0 for every ATM cell it generates by segmentation.
•
In the ATM-to-FUNI direction, it sets the CN bit in the FUNI header to 1 if the EFCI field in the
last ATM cell of a received, segmented frame is 1. The two reserve bits (the same positions as C/R
and BECN in Frame Relay header) are always 0.
Configuring Frame Relay Service
This section first describes how to configure the FRSM card, lines, and ports, then describes how to add
connections. The descriptions are for the CLI execution of the tasks. You can also configure the FRSM
card, lines, and ports by using the CiscoView application. Refer to the CiscoView documentation for
the directions. Also, the easiest way to add connections is by using the Cisco WAN Manager
application. For full details of how to set up a connection through the WAN Manager GUI, refer to the
Cisco WAN Manager Operations manual.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-41
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Configuring the FRSM Cards, Lines, and Ports
This section describes how to configure card-level parameters, physical lines, and logical ports on the
FRSM-series cards.
Step 1
If necessary, modify the resource partitioning for the whole card by executing the cnfcdrscprtn
command. You can view resource partitioning through dspcdrscprtn.
cnfcdrscprtn <number_PAR_conns | number_PNNI_conns | number_TAG_conns>
number_PAR_conns is the number of connections in the range 0–1000 available to the PAR controller.
number_PNNI_conns is the number of connections in the range 0–1000 available to a PNNI controller.
number_TAG_conns is the number of connections in the range 0–1000 available to the Tag controller.
For example, you could reserve 300 connections for each controller on the FRSM with:
cnfcdrscprtn 300 300 300
Step 2
If the physical line is not yet active, use the addln command to activate it. The only argument addln
takes is the line number.
Step 3
If necessary, modify the lines by using cnfln on the MGX-FRSM-2CT3, MGX-FRSM HSSI cards,
AX-FRSM-8T1 or AX-FRSM-8E1. Use cnfds3ln on the MGX-FRSM-2CT3 and MGX-FRSM-2T3E3.
The cnfln and cnfds3ln commands affect different aspects of the MGX-FRSM-2CT3.
Step 4
If the logical port does not exist or is not the appropriate type (Frame Relay, FUNI, or frame
forwarding), execute addport to create the appropriate type of port. If the logical port already exists,
go to the step for adding a connection using the addcon command (or addchan if you must use NSAP
addressing format). The parameters for addport depend on the type of FRSM:
For unchannelized VHS cards (MGX-FRSM-2T3E3, MGX-FRSM-HS2):
addport port_num line_num port_type
•
port_num is the logical port number in the range 1–2. The mapping between a logical port and a
line is one-to-one for these cards. Note that the maximum committed information rate (CIR) on
each line for these cards is 0–44210000 bps for MGX-FRSM-2T3, 0–34010000 bps for
MGX-FRSM-2E3, and 0-51840000 bps for MGX-FRSM-HS2. Specify CIR with addcon (or
addchan if necessary).
•
line_num is the physical line number in the range 1–2.
•
port_type is a number representing the mode of operation for the logical port:
1 for Frame Relay; 2 for FUNI mode-1a; and 3 for frame forwarding.
For the channelized VHS card (MGX-FRSM-2CT3):
addport port_num line_num ds0_speed begin_slot num_slot port_ type
•
port_num is the logical port number in the range 1–256. When you subsequently add a connection
through the preferred command addcon or the addchan command (which requires NSAP format),
you must indicate a logical port by using this singular port_num regardless of the number of DS0s.
(You can add 1–24 DS0s to a single port_num through the other addport parameters.)
•
line_num is the DS1 number in the range 1–56 to which you assign the DS0 when both lines are
active. If you activate only one line, the range is 1–28. You can assign up to 24 contiguous DS0s to
one DS1. Each physical line supports up to 28 DS1s. The number of DS0s cannot span more than
DS1.
•
ds0_speed is a number representing the DS0 speed: 1 for 56 Kbps or 2 for 64 Kbps.
Cisco MGX 8230 Installation and Configuration
3-42
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
•
begin_slot is the beginning DS0 timeslot in 1 base. For example, on port number 50, you could
make begin_slot=9 then specify num_slot to be in the range 1–16.
•
num_slot is the number of DS0s in the associated DS1. Note that the number of DS0s cannot be
such that the logical port spans more than DS1.
•
port_type is a number representing the mode of operation for the logical port:
1 for Frame Relay; 2 for FUNI mode-1a; and 3 for frame forwarding.
For AX-FRSM-8T1 and AX-FRSM-8E1:
addport port_num line_num ds0_speed begin_slot num_slot port_type
Step 5
•
port_num is the logical port number in the range of either 1–192 for T1 or 1–248 for E1. When you
subsequently add a connection through the preferred command addcon or the addchan command
(which requires NSAP format), you must indicate a logical port by using this singular port_num
regardless of the number of DS0s. (You can add 1–24 DS0s to a single line through the other
addport parameters.)
•
line_num is the physical line number in the range 1–8.
•
ds0_speed is a number representing the DS0 speed: 1 for 56 Kbps or 2 for 64 Kbps.
•
begin_slot is the beginning DS0 timeslot in 1 base. For example, on port number 50, you could
make begin_slot=9 then specify num_slot to be in the range 1–16,begin_slot is the beginning
timeslot in 1 base.
•
num_slot is the consecutive DS0s that each connection on port_num has.
•
port_type is a number representing the mode of operation for the logical port:
1 for Frame Relay; 2 for FUNI mode-1a; and 3 for frame forwarding.
Configure resources for the port as needed by executing cnfportrscprtn. To see the partitioning, use
dspportrscprtn. The description has a high- and low-bandwidth version:
cnfportrscprtn <port_num> <controller> <percent BW> <low DLCI> <high DLCI> <max LCN>
For FRSM-VHS cards:
•
port_num is the port number in the range 1–2 for MGX-FRSM-2T3E3 and MGX-FRSM-HS2 or
1–256 for MGX-FRSM-2CT3.
•
controller is a number representing the controller: 1=PAR, 2=PNNI, and 3=Tag.
•
percent BW is the percentage of the bandwidth in the range 0–100 and applies to both egress and
ingress.
•
low DLCI is in the range 0–1023.
•
high DLCI is in the range 0–1023.
•
max LCN is the maximum number of logical connections available to the controller on this port.
The ranges are 1–4000 for MGX-FRSM-2CT3 and 1–2000 for MGX-FRSM-2T3E3 and
MGX-FRSM-HS2.
For AX-FRSM-8T1 or AX-FRSM-8E1:
•
port_num is the logical port number in the range 1–192 for T1 or 1–248 for E1.
•
controller-name is PAR, PNNI, or TAG.
•
percent BW is the percentage of the bandwidth in the range 0–100 and applies to both egress and
ingress.
•
low DLCI is in the range 0–1023.
•
high DLCI is in the range 0–1023.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-43
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
•
max LCN is the maximum number of logical connections available to the controller on this port.
The range is 1–1000.
Adding a Frame Relay Connection
This section describes how to add a Frame Relay connection according to the rules for adding a standard
connection or a management connection in the form of either a DAX con or a three-segment connection.
See “Rules for Adding Connections” earlier in this chapter.
Step 1
Add a connection by using addcon. If the application requires the NSAP form for the endpoint, use
addchan as described in the command reference.
The system automatically assigns the next available channel number, so the addcon command does not
require it. However, some related commands require a channel number. To see the channel number after
you add a connection, use dspcons.
On the FRSM-VHS cards (2CT3, 2T3E3, or HS2):
addcon <port> <DLCI> <cir> <chan_type> <egress_service_type> [CAC] <controller_type>
<mastership> [connID] <controllerID>
•
port is the logical port number on the MGX-FRSM-2CT3 in the range 1–256. On the
MGX-FRSM-2T3E3 and MGX-FRSM-HS2, the range is 1–2. (See addport step if necessary.)
•
DLCI is the DLCI number in the range 0–1023 (2CT3/2T3/2E3/HS2).
•
cir is the committed information rate in one of the following ranges:
for 2CT3, 0–1536000 bps; for 2T3, 0–44210000 bps; 2E3, 0–34010000 bps; and
for HS2, 0–51840000 bps.
•
chan_type specifies the type of connection: 1=NIW, 2=SIW-transparent mode;
3=SIW with translation; 4=FUNI, and 5=frame forwarding.
•
egress_service_type is a number that specifies the type of queue on the egress:
1=high priority; 2=real-time VBR, 3=nonreal-time VBR; 4=ABR; and 5=UBR.
•
CAC optionally enables connection admission control; 1=enable. 2=disable (default). With CAC
enabled, the system adds the resource consumption represented by adding the connection to the
total resources consumed on a logical port.
•
controller_type is the controller type for signaling connections: 1 (the default) specifies a PVC and
applies to PAR. 2 specifies a SPVC and applies to PNNI.
•
mastership indicates if this end of the connection is master or slave: 1=master, 2=slave.
•
connID is the connection identifier at the remote end. It appears in the syntax as an optional
parameter because it is mandatory only when you add the connection at the master end. See “Rules
for Adding Connections” at the beginning of this chapter. The connID can have one the following
formats according to the slave endpoint:
Nodename.SlotNo.PortNo.DLCI
Nodename.SlotNo.PortNo.ControllerId.DLCI
Nodename.SlotNo.PortNo.VPI.VCI for ATM endpoint
•
controllerID is a number indicating the type of network control application:
1=PAR, 2=PNNI, 3=MPLS
Cisco MGX 8230 Installation and Configuration
3-44
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
For AX-FRSM-8T1 and AX-FRSM-8E1:
addcon <port> <DLCI> <cir> <chan_type> [CAC] <controller_type> <mastership> <connID>
<controllerID>
•
port is the logical port number in the range 1–192 for T1 or 1–248 for E1. (See addport step if
necessary.)
•
DLCI is the DLCI number in the range 0–1023.
•
cir is the committed information rate in one of the following ranges:
for T1, 0–1536000 bps for T1; for E1, 0–2048000 bps.
•
chan_type specifies the type of connection: 1=NIW, 2=SIW-transparent mode;
3=SIW with translation; 4=FUNI, and 5=frame forwarding.
•
CAC optionally enables connection admission control: 1=enable. 2=disable (default).
•
controller_type is the controller type for signaling: 1=PVC (PAR), the default, 2=SPVC (PNNI).
•
mastership indicates if this end of the connection is master or slave: 1=master, 2=slave.
•
connID is the connection identifier at the remote end and can have one the following formats
according to the type of card at the slave endpoint:
NodeName.SlotNo.PortNo.DLCI
NodeName.SlotNo.PortNo.ControllerId.DLCI
NodeName.SlotNo.PortNo.VPI.VCI for ATM endpoint
If the remote end is a MGX 8230-PXM, the port number can be in the range 1–32 for user
connections or 34 for inband management connections (stand-alone node only).
•
Step 2
controllerID is a number indicating the type of network control application:
1=PAR, 2=PNNI, 3=TAG.
If necessary, modify the CLP and congestion indicator fields by using cnfchanmap:
cnfchanmap <chan_num> <chanType> <FECN/EFCI> <DE to CLP> <CLP to DE>
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-45
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
chan_num
is the channel (connection) number. The ranges are:
2CT3, 16–4015
2T3, 2E3, HSSI, 16–2015
T1, E1, 16–1015
chanType
is a number in the range 1–5 indicating the service type for
the connection.
1=NIW
2=SIW in transparent mode
3=SIW in translation mode
4=FUNI
5=frame forwarding
FECN/EFCI is a number in the range 1–2 that specifies the mapping between
FECN and EFCI fields.
1=map EFCI (SIW only)
2=set EFCI to 0
DE to CLP
is a number in the range 1–3 that specifies the DE to CLP mapping.
1=map DE to CLP
2=set CLP to 0
3=set CLP to 1
CLP to DE
is a number in the range 1–4 that specifies the CLP to DE mapping.
1=map CLP to DE
2=set DE to 0
3=set DE to 1
4=ignore CLP (NIW only)
Establishing the Middle Segment of the Frame Relay Connection
For a three-segment connection, you must establish a middle segment across the MGX/BPX network.
Execute addcon at one of the MGX 8000 series nodes, as follows.
•
For slot and port number, specify slot and port of the MGX UXM connected to MGX 8230.
•
For VPI and VCI, specify the VPI and VCI at the endpoint on the MGX 8230-PXM.
•
For nodename, use the name of the MGX 8000 series switch at the far end of the connection.
•
For Remote Channel, specify the slot and port number of the UXM port attached to the
MGX 8230 at the far end. Specify the VPI as the slot number of the remote MGX 8230 FRSM
connected to the MGX 8000 series switch, and specify VCI as the LCN of the Frame Relay
connection at the remote MGX 8230.
•
Specify the type of connection. Enter ATFST if the ForeSight feature is operating and ATFR if this
feature is not operating.
Cisco MGX 8230 Installation and Configuration
3-46
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Specify the other addcon bandwidth parameters such as MCR, PCR, %Util, and so on.
•
Minimum Cell Rate (MCR) is only used with the ForeSight feature (ATFST connections).
•
MCR and Peak Cell Rated (PCR) should be specified according to the following formulae.
•
MCR=CIR *3/800 cells per second.
•
PCR=AR * 3/800 cells per second but less than or equal to 6000.
AR=Frame Relay port speed in bps. For example,
For example:
AR equals 64K, PCR=237, or
AR speed equals 256K, PCR=950, or
AR speed equals 1536K, PCR=5703
The preceding MCR and PCR formulae are predicated on a relatively small frame size of 100 octets,
and even smaller frame sizes can result in worst-case scenarios. For example:
For a frame size of 64 octects the PCR formula
becomes:
PCR=AR * 2/512 cells per
sec
For a frame size of 43 octects the PCR formula
becomes:
PCR=AR * 2/344 cells per
sec
% Util should be set to the same value as that used for the Frame Relay segments of the connection.
Circuit Emulation Service Module Connections
The main function of the 8-port Circuit Emulation Service Module (MGX-CESM-8T1 and
MGX-CESM-8E1) is to provide a constant bit rate (CBR) circuit emulation service by converting data
streams into CBR AAL1 cells for transport across an ATM network. The CESM supports the CES-IS
specifications of the ATM Forum.
The 8-port CESM lets you configure individual physical ports for structured or unstructured data
transfer. The card sets consist of an MGX-CESM-8T1 or MGX-CESM-8E1 front card and one of the
following back cards:
•
RJ48-8T1-LM
•
R-RJ48-8T1-LM
•
RJ48-8E1-LM
•
R-RJ48-8E1-LM
•
SMB-8E1-LM
Structured Data Transfer
If you configure an individual port for structured data transfer, the 8-port CESM supports:
•
Synchronous timing.
•
Superframe or Extended Superframe for T1.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-47
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
•
N x 64 Kbps, fractional DS1/E1 service (contiguous time slots only). You can map a N x 64-Kbps
channel to any VC.
•
CAS robbed bit for T1 (ABCD for ESF and SF frames) and CAS for E1 (channel 16).
•
CCS channel as a transparent data channel.
•
A choice of partially filled cells.
•
Idle detection and suppression for 64Kbps CAS connections.
•
Loopback diagnostics on a line or a connection (addlnloop, tstcon, and tstdelay commands).
Unstructured Data Transfer
If you configure an individual port for unstructured data transfer, the 8-port CESM supports:
•
Synchronous or asynchronous timing at T1 (1.544 Mbps) or E1 (2.048 Mbps) rates. For
asynchronous timing, you can select its basis as either SRTS or adaptive clock recovery.
•
The special port type framingOnVcDisconnect. This port type prevents a remote-end CPE from
going to LOF by placing a line in remote loopback mode when the CESM determines that a
connection deletion or suspension occurred at the network-side ATM interface.
•
Ability to detect and display a yellow alarm for the ESF framing on a T1 line.
•
Loopback diagnostics on a line or a connection (addlnloop, tstcon, and tstdelay commands).
Configuring Service on an 8-Port CESM
This section describes the steps for setting up a CESM and adding connections. The maximum number
of connections is 248 on the MGX-CESM/B-8E1 and 192 on the MGX-CESM/B-T1. Use either the CLI
or the Cisco WAN Manager application to set up a CESM and add connections. The following list shows
the fundamental tasks and applicable CLI commands:
•
Optionally configure redundancy a the card level (addred and possibly addlink on the MGX
8230-PXM)
•
Optionally modify resource partitions at the card level (cnfcdrscprtn)
•
Activate a physical line (addln) and optionally configure the line (cnfln)
•
Create logical ports for structured data transport on a physical line (addport)
•
Optionally modify resource partitions at the port level (cnfportrscprtn)
•
Add connections by using addcon (or addchan if NSAP addressing is necessary)
For CESM-related commands, see the list of service module commands at the beginning of the Cisco
MGX 8250 Command Reference. Also, each command description in the command reference lists
related commands. For example, it shows display commands that relate to addition commands.
Configuring the Card, Lines, and Ports
This section describes how to configure card, line, and port-level parameters for a CESM through the
CLI. If you use the CiscoView application, refer to the CiscoView documentation. On the CLI, the
command sequence is:
Step 1
addln <line number>
where line number is in the range 1–8. You can modify line characteristics with cnfln.
Cisco MGX 8230 Installation and Configuration
3-48
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Step 2
Optionally execute cnfln to modify line characteristics from the defaults. (Use dspln or dsplns to
check). The syntax for cnfln is:
cnfln <line_num> <line_code> <line_len> <clk_src> [E1-signaling]
•
line_num is a line number in the range 1–8.
•
line_code is a number that specifies the line coding: 2=B8ZS (T1), 3=HDB3 (E1), and
4=AMI (T1/E1)
•
line_len is the line length: 10-15 for T1, 8 for E1 with SMB line module, 9 for E1 with RJ-48 line
module
•
clk_src is a number specifying the clock source: 1 for loop clock, 2 for local clock
•
E1-signalling specifies the E1 signalling. The possible entries are:
– CAS, which specifies CAS and no CRC
– CAS_CRC, which specifies CAS with CRC
– CCS, which specifies CCS and no CRC
– CCS_CRC, which specifies CCS with CRC
– CLEAR: CLEAR channel
Step 3
Create a logical port with addport if the application requires N x 64-Kbps channels:
addport <port_num> <line_num> <begin_slot> <num_slot> <port_type>
Step 4
•
port_num is the logical port number in the range 1–192 for T1 or 1–248 for E1
•
line_num is the number of the physical line in the range 1–8.
•
begin_slot is the beginning timeslot number in the frame: for T1, 1–24. For E1 2–32 with CCS
signaling or 2–16 and 17–32 with CAS signaling.
•
num_slot is the number of timeslots in the frame for the current port (port_num).
•
port_type is: 1=structured, 2=unstructured, 3=framing on VC disconnect.
Configure resources at the port level as needed by executing cnfportrscprtn:
cnfportrscprtn <port_num> <controller_name>
•
port_num is the logical port number in the range 1–192 for T1 or 1–248 for E1.
•
controller_name is the name of the network control application. Enter one of the following strings:
PAR, PNNI, or MPLS.
Adding and Modifying CESM Connections
Use either the Cisco WAN Manager application or the CLI to add or modify connections. If you use the
WAN Manager application, refer to the Cisco WAN Manager Operations Guide.
The preferred command is addcon. If the application requires NSAP addressing, use addchan to add
the connection and cnfchan if you need to modify it. Refer to the command reference for the syntax.
On the CESM CLI:
Step 1
Add a connection through the preferred command addcon. (Alternatively, you can use addchan if your
application requires the NSAP format of endpoint specification.)
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-49
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Execute addcon at both ends of the connection—unless the remote endpoint is on port 34 of an MGX
8230-PXM (see the note at the end of this step). The maximum number of connections for the
MGX-CESM-8T1 is 248 and 192 for the MGX-CESM-8E1. Note that, because you can add only one
connection per port, addcon does not request a connection number.
The system automatically assigns the next available channel number, so the addcon command does not
require it. However, some related commands require a channel number. To see the channel number after
you add a connection, use dspcons.
The syntax for addcon is:
addcon <port_num> <sig_type> <partial_fill> <cond_data> <cond_signalling> [controller_type]
[mastership] [remoteConnId]
Step 2
•
port_num is the logical port number. This port must already exist (see addport).
•
sig_type is a number indicating the type of signaling: 1 specifies basic signaling, 2 specifies E1
CAS, 3 specifies ds1SFCAS (DS1 Superframe CAS), and 4 specifies ds1ESFCAS (DS1 Extended
Superframe CAS).
•
partial_fill is a number representing the number of bytes in a cell. It can be either 0 to specify that
the cell must contain 48 bytes or a non-0 value that fixes the number of bytes in each cell. For
structured E1, the partial_fill range is 20–47 bytes. For structured T1, the range is 25–47 bytes.
Unstructured T1 or E1 can be 33–47 bytes.
•
cond_data is the conditioning data in case of loss of signal (LOS). It is always 255 for unstructured
data transfer or 0–255 for structured data transfer. For a voice connection, the larger the cond_data
value, the louder the hiss heard in case of LOS.
•
cond_signalling is the string of condition signaling bits that you specify with a decimal number in
the range 0–15, where, for example, 15=1111, and 0=0000. These bits represent the ABCD
signaling to the line or network when an underflow occurs.
•
mastership indicates whether this endpoint is the master or slave. 1=master, 2=slave (default).
•
remoteConnId is the identification for the connection at the slave end. The format is
nodename.slot_number.port_number.vpi.vci.
Optionally, you can use cnfcon to modify an individual connection. This command requires a channel
number. If you add a connection by using addcon, you do not need to specify a channel number because
the system automatically uses the next available number. To obtain the channel number for cnfcon,
execute dspcons.
cnfcon <port_num> <CDVT> <CLIP> <bufsize> <cbrclkmode> <isenable> <exttrigis>
•
port_num is the port number.
•
CDVT is a tolerable variation for the arrival time of cells. For T1, the range is 125–24000
microseconds. For E1, the range is 125–26000 microseconds. Both require 125-microsecond
increments.
•
CLIP is CellLossIntegrationPeriod, an amount of time a connection can be in an error condition
before an alarm is declared. The range is 1000-65535 milliseconds.
•
bufsize is the egress buffer size in bytes. These buffers are used for tolerating variations in the cell
delay. The size can be automatically computed, or you can enter a specific size in bytes.
•
cbrclkmode is the clock mode for a circuit emulation connection. The values are 1–3:1 is
synchronous, 2 is SRT, 3 is adaptive. SRT and adaptive are asynchronous clocking schemes.
Cisco MGX 8230 Installation and Configuration
3-50
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
•
isenable is a flag to enable the idle code (ABCD signalling bits)-based cell suppression feature on
a connection. If you enable this feature, idle suppression logic is activated so that suppression
begins when valid idle ABCD bits are detected. This feature is valid for only single DS0
connections. Possible values are 1 to enable and 2 to disable.
•
exttrigis is an enable for an external idle suppression trigger. With this feature enabled, the logic
forcefully suppresses cells on a single DS0 connection. Enter a 1 to disable idle suppression or a 2
to enable idle suppression.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3-51
Chapter 3
Configuring the MGX 8230
Adding Service Module Connections
Step 3
Optionally, you can configure connection parameters for the network segment of a three-segment
connection:
cnfswparms <chan_num> <mastership> <vpcflag> <conn_service_type> (=cos)
<route_priority> <max_cost> <restrict_trunk_type> <pcr> <mcr> <pct_util>
•
chan_number is the connection in the range 32–279.
•
mastership specifies the current endpoint as master or slave: 1=master, 2=slave (default).
•
vpcflag indicates whether the connection is a VPC or a VCC: 1=VPC, and 2=VCC.
•
conn_service_type selects the type of service for the connection: 1=cbr, 2=vbr, 3 is not used, 4=ubr,
5=atfr, 6=abrstd, and 7=abrfst.
•
route_priority is the priority of the connection for rerouting. The range is 1–15 and is meaningful
only in relation to the priority of other connections.
•
max_cost is a number establishing the maximum cost of the connection route. The range is 1–255
and is meaningful only in relation to the cost of other connections.
•
restrict_trunk_type is a number that specifies the type of trunk this connection can traverse. The
numbers are 1 for no restriction, 2 for terrestrial trunk only, and 3 for satellite trunk only.
•
pcr is the peak cell rate.
•
mcr is the minimum cell rate. The range is 1–65535 cells per second.
•
pct_util is the percent utilization in the range 1–100.
Cisco MGX 8230 Installation and Configuration
3-52
Release 1.0, Part Number 78-10616-01, June 2000
CH A P T E R
4
Maintenance
This section provides maintenance procedures for the physical components of the MGX 8230. It
includes:
•
Removing and Replacing the Fan Tray Assembly
•
Removing and Replacing an AC Power Supply Module
•
Removing and Replacing a DC Power Entry Module
•
Removing and Replacing Processor and Service Modules
•
Changing a Single-Height Card Slot into a Double-Height Card Slot
•
Backplane Fuse Replacement
•
Bit Error Rate Testing (BERT) Through an MGX-SRM-3T3
This section does not include detailed troubleshooting information for the MGX 8230 as an IGX feeder.
That information will be found in other documentation.
Removing and Replacing the Fan Tray Assembly
The Fan Tray Assembly, shown in Figure 4-1, can be removed and replaced when an MGX 8230 is
running if it is done very quickly. When the MGX 8230 is running you must remove and replace the Fan
Tray Assembly in less than two minutes. Individual fans in the Fan Tray Assembly are not field
replaceable.
The Fan Tray Assembly is vertically installed on the left side of the front of the MGX 8230 chassis. It
is held in place by one captive screw on its bottom; there is also an ejector lever on the bottom of the
Fan Tray Assembly that can be used to unseat it from the backplane.
Caution
Because of its shape, the Fan Tray Assembly has a tendency to drop suddenly against the
chassis as it is being removed. Be sure to hold it with two hands and hold it firmly until it
is completely removed from the chassis.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
4-1
Chapter 4
Maintenance
Removing and Replacing the Fan Tray Assembly
Fan Tray Assembly
17274
Figure 4-1
Once you have determined that a Fan Tray Assembly is faulty, follow these steps to remove and replace
it:
Note
Make sure that you have the replacement Fan Tray Assembly and your tools ready.
Step 1
Open the MGX 8230 door, if applicable, and locate the Fan Tray Assembly, shown in the left side of
the MGX 8230 chassis as seen from the front. See Figure 4-2.
Step 2
Loosen the captive screw holding the Fan Tray Assembly to the MGX 8230 chassis.
Step 3
Use the ejection lever added to the bottom of the fan and chassis to unseat the Fan Tray Assembly from
the backplane.
You can use the combination tool used to open the door that is provided with the MGX 8230 or a regular
screwdriver for leverage on the injector. Slip it through the opening in the ejector lever and pull the lever
out away from the MGX 8230.
Step 4
Pull the Fan Tray Assembly out carefully, holding it firmly with two hands so it does not drop suddenly
against the MGX 8230 chassis as it is removed.
There is a small standoff on the upper-left side of the chassis that the Fan Tray Assembly rides on that
helps support it as it is being removed, but you must still be careful.
Cisco MGX 8230 Installation and Configuration
4-2
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 4
Maintenance
Removing and Replacing an AC Power Supply Module
Fan Tray Assembly in MGX 8230 Chassis
23828
Figure 4-2
To replace the Fan Tray Assembly, follow these steps:
Step 1
Slide the replacement fan into the MGX 8230 chassis; make sure to get the upper left edge of the Fan
Tray Assembly over the small standoff on the upper left wall of the card cage in the fan slot.
Step 2
Carefully press it until the plug on the rear of the Fan Tray Assembly mates with the connector on the
backplane of the MGX 8230.
Step 3
Tighten the captive screw securing the fan to the MGX 8230 chassis.
Removing and Replacing an AC Power Supply Module
There can be up to two 1200 Watt AC Power Supply Modules installed in the AC Power Supply Tray.
The optional AC Power Supply Tray is factory installed. Each AC Power Supply Module has its own
Enable (On/Off) switch, connectors, and status LEDs. The AC Power Supply Modules are independent
of one another, and one can be replaced while the other powers the MGX 8230.
Figure 4-3 illustrates a rear view of an AC Power Supply Module. Figure 4-4 illustrates the rear panel
of an MGX 8230 with two AC Power Supply Modules installed. There is a captive nut on the flange on
the top of the rear panel of each AC Power Supply Module used to secure the AC Power Supply Modules
to the AC Power Supply Tray and the MGX 8230 chassis, once they are installed.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
4-3
Chapter 4
Maintenance
Removing and Replacing an AC Power Supply Module
AC Power Supply Module, Rear View
23818
Figure 4-3
AC DC
MGX 8230 with Two AC Power Modules Installed
23825
Figure 4-4
AC DC
AC DC
The AC power supply is defective if the front panel AC LED is on, but the DC LED is off with the DC
output cable connected to the backplane and the power supply. To verify that the power supply did not
latch off due to an AC input line transient, turn off the enable switch, wait for at least four seconds, and
turn the enable switch on again. If the DC LED fails to light, the power supply is defective.
Cisco MGX 8230 Installation and Configuration
4-4
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 4
Maintenance
Removing and Replacing an AC Power Supply Module
After determining that an AC power supply is faulty—the front panel AC LED is on, but the DC LED
is off -- follow these steps to remove and replace it:
Step 1
Turn off the Enable (On/Off) switch on the appropriate AC Power Supply Module.
Step 2
Turn off power at the AC source for the appropriate AC Power Supply Module.
Step 3
At the rear of the MGX 8230, disconnect the AC power cord from the AC input of the appropriate AC
Power Supply Module by loosening the st4rain relief clamp screw with the multi tool provided.
Step 4
Disconnect DC power cable from the appropriate AC Power Supply Module.
Step 5
Remove the screw at the top of the AC Power Supply Module that secures it to the AC Power Supply
Tray.
Step 6
Pull AC Power Supply Module out using the handle on rear of the AC power supply as shown in
Figure 4-3.
Step 7
Insert the new AC Power Supply Module.
Step 8
Replace and tighten the screw at the top of the AC Power Supply Module.
Step 9
Reattach the DC power cable.
Step 10
Reattach the AC power input cable.
Step 11
Turn the AC source power on.
Step 12
Turn the Enable switch on the AC Power Module to On.
Step 13
From the front of the MGX 8230, verify that both LEDs (AC and DC) on the replacement AC Power
Supply Module are lit.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
4-5
Chapter 4
Maintenance
Removing and Replacing a DC Power Entry Module
Removing and Replacing a DC Power Entry Module
There can be two DC PEMs located on the rear panel of an MGX 8230. Once you have determined that
you need to remove and replace a DC PEM, shown in Figure 4-5, follow these steps:
DC Power Entry Module
17275
Figure 4-5
OFF
TB1
48 VDC
30A
3
2
1
Removing DC PEM
To remove a DC PEM, follow these steps:
Step 1
Turn off the circuit breaker on the DC PEM that is being removed.
Step 2
Turn off the DC source power.
Step 3
Turn off the switch on the DC PEM.
Step 4
Unplug the pluggable terminal block at TB1.
Step 5
Loosen the captive screws holding the DC PEM to the MGX 8230.
Step 6
Slide the DC PEM out of the MGX 8230.
Replacing DC PEM
To replace a DC PEM, follow these steps:
Step 1
Turn off the circuit breaker on the DC PEM that is being replaced.
Step 2
Slide the DC PEM into its slot on the back of the MGX 8230.
Step 3
Secure the DC PEM to the MGX 8230 with the two captive screws.
Step 4
Plug the pluggable terminal block back in at TB1.
Step 5
Turn on the power at the DC source.
Step 6
Turn on the DC PEM switch.
Step 7
Verify that the DC PEM LED is lit.
Cisco MGX 8230 Installation and Configuration
4-6
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 4
Maintenance
Removing and Replacing Processor and Service Modules
Removing and Replacing Processor and Service Modules
Removing and Replacing Processor and Service Modules is covered in Chapter 2 in the section,
“Installing Processor and Service Modules.” Those procedures include instructions for both front cards
and back cards.
Changing a Single-Height Card Slot into a Double-Height Card
Slot
Note
Even though the card slots in an MGX 8230 are horizontal and would be more
appropriately called single-width and double-width, this manual still refers to the card
slots as single-height and double-height. This is because the MGX 8230 processor and
service module cards are a subset of the MGX 8850 cards, which are installed vertically
in an MGX 8850 chassis.
The MGX 8230 is typically configured at the factory as you ordered it. Unused card slots are configured
for single-height modules and covered with blank faceplates.
Single-height service module slots 3 through 7 and 10 through 14 can be converted into slots for a
double-height by removing the center divider module. Note that these slots have to be converted from
bottom to top, that is, slot 3 has to be converted before you convert slot 4. Figure 4-6 illustrates the slot
numbering of an MGX 8230 with slots 3 configured for a double-height module.
MGX 8230 Slot Numbering
F
A
N
7 RU
(12.25 in.,
31.1 cm.)
1 RU
(1.75 in.,
4.5 cm.)
T
R
A
Y
7
SRM 1
SRM 2
14
6
Single height SM
Single height SM
13
5
Single height SM
Single height SM
12
4
Single height SM
Single height SM
11
3
Double height SM
10
2
PXM1 B
9
1
PXM1 A
8
Optional AC power tray
38384
Figure 4-6
23.5 in.,
(59.7 cm.)
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
4-7
Chapter 4
Maintenance
Changing a Single-Height Card Slot into a Double-Height Card Slot
Be aware of the following before you convert the slots:
Caution
•
Convert lower number slots first. Slot 3 must be converted before slot 4 can be converted, and so
on.
•
After conversion, the left slot, which identifies both single-height and double-height slots, is
numbered from the left-side. Thus slot 4 could refer to either a single-height slot or a double-height
slot. The right slots are numbered on the right side, as shown in Figure 4-6, and refer only to
single-height slots.
You can convert single-height card slots to double-height when there is powered applied
to the MGX 8230. Install the center guide module only in the center of the card slot where
there is a guide which it fits over and slides on. The guide is on the top of the card slot in
the middle. Make sure never to slide the center guide module into the backplane
connectors.
Figure 4-7 illustrates a center guide module, and Figure 4-8 shows the location of center guide modules
in an MGX 8230 chassis.
Center Guide Module, Slot Divider
23819
Figure 4-7
Cisco MGX 8230 Installation and Configuration
4-8
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 4
Maintenance
Changing a Single-Height Card Slot into a Double-Height Card Slot
Front View of an MGX 8230 Card Cage
23820
Figure 4-8
To convert a slot, follow these steps:
Step 1
Delete all the connections, and down all the ports, lines, and trunks on the single-height slots that you
are converting, if applicable.
Step 2
Remove the cabling from the back cards (unless they are the correct back cards for the double-height
card), then remove the back card.
Step 3
Remove the front cards in both single-height slots, if applicable.
Step 4
Repeat steps 3 and 4 for every slot you are going to convert.
Step 5
Insert a screw driver and loosen the long screw that holds in the center guide module in place. See
Figure 4-7.
Step 6
Remove the center guide module by sliding straight out on guide rail.
Step 7
Install the double-height front card and associated back cards as needed.
Install a blank faceplate where you do not fill a double-height slot with a double-height card. (Likewise,
where you do not install a back card, you must install a blank single-height faceplate.)
To replace a center guide module, follow these steps:
Step 1
Locate and prepare the empty slot in which you are going to install the center guide module.
Step 2
Note the position for the center guide module in marked by an indentation on the bottom panel of the
card slot, and there is a guide for the slot fixed to the top panel of the card slot.
Step 3
Slide the center guide module into the card slot, making sure that it rides on the guide fixed to the top
panel.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
4-9
Chapter 4
Maintenance
Backplane Fuse Replacement
Caution
Step 4
Install the center guide module only in the center of the card slot where there is a guide
that fits over and slides on. The guide is on the top of the card slot in the middle. Make
sure never to slide the center guide module into the backplane connectors.
When the guide is all the way in position, insert a screw driver in the hole located at the front of the
center guide module and tighten the long screw.
When reconverting slots to single height, start at the top and work down.
Backplane Fuse Replacement
The MGX 8230 has fuses in the backplane to protect individual card slots. Backplane fuses on the MGX
8230 rarely, if ever, need replacement. These fuses, which are shown in Figure 4-9, are accessed from
the rear of the card cage. They require a special tool for removal and replacement and should be changed
by certified field personnel only.
Backplane fuses are intended to prevent catastrophic damage to the backplane in the event of accidental
shorting of –48 VDC on the backplane to chassis ground. This type of event could be caused by bent
backplane pins, contact of conductive elements (EMI Cans, EMI Gaskets, and so on) to power pins.
These events would most likely happen during a factory build.
Because of design constraints, these fuses need to be in sockets on the backplane and are therefore not
readily accessible.
If a bad card slot is verified, call Cisco TAC. If a card with an open fuse is verified, return it to Cisco.
Warning
Replacing a fuse requires Cisco personnel only using a special tool with the power off.
Cisco MGX 8230 Installation and Configuration
4-10
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 4
Maintenance
Bit Error Rate Testing (BERT) Through an MGX-SRM-3T3
Backplane Fuses
23822
Figure 4-9
Bit Error Rate Testing (BERT) Through an MGX-SRM-3T3
The MGX 8230 feeder can perform a bit error rate test (BERT) on an active line or port. This type of
testing disrupts service because a BERT session requires the tested path to be in loopback mode. In
addition, the pattern test replaces user-data in the path with the test pattern. The applicable line types
and variations for a DS1 are:
•
A T1 or E1 line
•
Fractional portions of a T1 line that add up to a DS1
•
A single 56Kbps or 64Kbps DS0
•
A DS0 bundle consisting of N x 64-Kbps DS0s
With a set of MGX-SRM-3T3/B cards in the system, you can initiate a BERT session on an
MGX-FRSM-2CT3 or any 8-port service module. (In contrast, the MGX-FRSM-2T3E3,
MGX-CESM-T3, and MGX-CESM-E3 do not use the MGX-SRM-3T3/B for BERT. See the sections
for these service modules in this chapter for applicable BERT.)
The MGX 8230 bus structure supports one BERT session, so the feeder can run a maximum of one
session at a time. When you specify the target slot through the CiscoView application or the CLI, the
system determines if a BERT configuration already exists in the MGX 8230. After the system
determines that no BERT configuration exists, the display presents a menu for the BERT parameters.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
4-11
Chapter 4
Maintenance
Bit Error Rate Testing (BERT) Through an MGX-SRM-3T3
The CLI commands (whose functions correspond to CiscoView selections) are:
Note
•
cnfbert to configure and start a test
•
modbert to inject errors into the BERT bit stream
•
dspbert to display the parameters and results of the current test
•
delbert to end the current test
When a BERT session begins, all connections on a line or port go into alarm and return to
normal when the test ends. Consequently, the test may result in other types of traffic (such
as AIS).
During configuration, the parameter display or menu items depend first on the card type and whether
the test medium is a physical line or a logical port. Subsequent choices are test type, test patterns,
loopback type, and so on. See the Cisco MGX 8000 Series Command Reference for details on cnfbert
and the other BERT commands. The concatenation of menu to menu is extensive, so this section
contains tables of menu selections based on the card types and the test type.
The test type can be pattern, loopback, or DDS seek. The choice of test type leads to further menu
displays. Following the tables of menu choices, the remaining sections define the parameters in these
menu choices.
•
For AX-FRSM-8T1, AX-CESM-8T1, and MGX-FRSM-2CT3, see Table 4-1 pattern tests and
Table 4-2 for loopback tests.
•
For AX-FRSM-8E1 and AX-CESM-8E1, see Table 4-3 for pattern tests and Table 4-4 for loopback
tests.
•
For MGX-AUSM-8T1, see Table 4-5 for pattern tests and Table 4-6 for loopback tests.
•
For MGX-AUSM-8E1, see Table 4-7 for pattern and Table 4-8 loopback tests.
Table 4-1
Pattern Test for AX-FRSM-8T1, AX-CESM-8T1, and MGX-FRSM-2CT3
Test Medium
Port
Line
Medium Type
Device to Loop
BERT Pattern
Port with N time slots (can also submit to the v54
DDS seek test)
all patterns
Port with one 64-Kbps time slot (can also
submit to the DDS seek test)
latch or v54
all patterns
Port with one 56-Kbps time slot (can also
submit to the DDS seek test)
noLatch
2 9 or 2 11
latch or v54
all patterns
in-band/ESF or
metallic
all patterns
n/a
Cisco MGX 8230 Installation and Configuration
4-12
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 4
Maintenance
Bit Error Rate Testing (BERT) Through an MGX-SRM-3T3
Table 4-2
Loopback Test for AX-FRSM-8T1, AX-CESM-8T1, and MGX-FRSM-2CT3
Test Medium
Loopback
Port with N timeslots (can also submit to the DDS seek far end or remote
test)
Port
Line
Table 4-3
Medium Type
Port with one 64Kbps time slot (can also submit to the
DDS seek test)
far end or remote
Port with one 56Kbps time slot (can also submit to the
DDS seek test)
far end or remote
n/a
metallic, far end, or
remote
Pattern Test for AX-FRSM-8E1 and AX-CESM-8E1
Test Medium
Medium Type
Device to Loop
BERT Pattern
Port
any
none
all patterns
Line
n/a
metallic
all patterns
Table 4-4
Loopback Test for AX-FRSM-8E1 and AX-CESM-8E1
Test Medium
Medium Type
Loopback
Port
any
remote loopback
Line
n/a
metallic or remote
Table 4-5
Pattern Test for MGX-AUSM-8T1
Test Medium
Medium Type
Device to Loop
BERT Pattern
Line
n/a
in-band/ESF
all patterns
Table 4-6
Loopback Test for MGX-AUSM-8T1
Test Medium
Medium Type
Loopback
Line
n/a
far end, remote, or metallic
Table 4-7
Pattern Test for MGX-AUSM-8E1
Test Medium
Medium Type
Device to Loop
BERT Pattern
Line
n/a
none
all patterns
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
4-13
Chapter 4
Maintenance
Bit Error Rate Testing (BERT) Through an MGX-SRM-3T3
Table 4-8
Loopback Test for MGX-AUSM-8E1
Test Medium
Medium Type
Loopback
Line
n/a
remote or metallic
Pattern Test Options
The pattern test options consist of the device to loop and the pattern. This section lists the device options
and patterns that appear in the menus. Refer to the preceding tables as needed. The device to loop
options identify the type of device that participates in the test:
•
noLatch is a device that does not latch the data. It can be a:
– Non-latching office channel unit (OCU) that consists of one device
– Non-latching OCU that consists of a chain of devices
– Non-latching channel service unit (CSU)
– Non-latching data service unit (DSU)
•
Latch is a device that can latch the data and can be a:
– Latching DS0-DP drop device
– Latching DS0-DP line device
– Latching office channel unit (OCU)
– Latching channel service unit (CSU)
– Latching data service unit (DSU)
– Latching HL96 device
•
in-band/ESF
•
v54 is a polynomial loopback
•
metallic is a local loopback within the service module and does not involve an external device
The available patterns are:
1.
All 0s
2.
All 1s
3.
Alternating 1-0 pattern
4.
Double 1-0 pattern
5.
2 15-1 pattern
6.
2 20-1 pattern
7.
2 20-1 QRSS pattern
8.
2 23-1 pattern
9.
1 in 8 pattern
10. 3 in 24 pattern
11. DDS-1 pattern
12. DDS-2 pattern
13. DDS-3 pattern
Cisco MGX 8230 Installation and Configuration
4-14
Release 1.0, Part Number 78-10616-01, June 2000
Chapter 4
Maintenance
Bit Error Rate Testing (BERT) Through an MGX-SRM-3T3
14. DDS-4 pattern
15. DDS-5 pattern
16. 2 9 pattern
17. 2 11 pattern
Loopback Test Options
The loopback tests do not monitor the integrity of the data but rather the integrity of the path. The type
of loopback indicates the direction of test data transmission. The choices are:
•
far end means the service module transmits data to the CPE and receives the data back
•
remote means the service module receives data from the CPE and loops back to the CPE
•
metallic means the service module receives data from the network and loops it back to the network
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
4-15
Chapter 4
Maintenance
Bit Error Rate Testing (BERT) Through an MGX-SRM-3T3
Cisco MGX 8230 Installation and Configuration
4-16
Release 1.0, Part Number 78-10616-01, June 2000
A P P E N D I X
A
Technical Specifications
This appendix provides the technical specifications relevant to the MGX 8230, its processor and service
modules, and the applications and services that it provides. It contains the following sections:
•
MGX 8230 Enclosure, Power, and Performance Specifications
•
MGX 8230 Processor Switching Module Specifications
•
AUSM/B-8T1E1 Interface Characteristics
•
FRSM-2CT3 Specifications
•
FRSM-2T3E3 Specifications
•
FRSM-HS2 Specifications
•
Counters and Statistics for FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2
•
FRSM-8T1 Specification
•
FRSM-8E1 Specification
•
Circuit Emulation Service Module for T1 Operation
•
Circuit Emulation Service Module for E1 Operation
•
Physical and Electrical Characteristics for Cards
•
Electromagnetic Compatibility
•
Conformance
MGX 8230 Enclosure, Power, and Performance Specifications
This section describes the physical characteristics and system power requirements for the
MGX 8230 feeder. The “MGX 8230 Processor Switching Module Specifications” section lists the
dimensions, weight, and power consumption for each card. The appendix titled “Cabling
Specifications” lists the AC power plugs for domestic and international use.
Table A-1 shows the MGX 8230 enclosure and electrical characteristics.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-1
Appendix A
Technical Specifications
MGX 8230 Enclosure, Power, and Performance Specifications
Table A-1
Enclosure and Electrical Characteristics
Item
Value
Card Slot Capacity
Supports combinations of full and single-height service modules.
Two double-height slots reserved for PXMs.
Up to 10 single-height slots for service modules or
up to 5 double-height slots for service modules.
Enclosure Size,
AC-powered system
8 Rack Units high
Height: 14.00 inches (35.56 cm).
Width: 17.72 ins (45.01 cm).
Depth: 23.5 ins (59.69 cm) (excluding cable management)
DC-powered system
7 Rack Units high
Height: 12.25 inches (63.50 cm).
Width: 17.72 inches (45.01 cm).
Depth: 23.5 inches (59.69 cm) (excluding cable management)
Shipping Weight for
Populated Enclosure
Approximately 150 lbs.
Clearance Requirement
Minimum 30 inches front and rear; nominal 12-inch side clearance.
Power Input Voltage
AC system: Normal operating range is 100–240 VAC, 47 to 63 Hz.
The maximum voltage range is 90–264 VAC.
DC system: –42 to –56 VDC.
Each AC supply can provide up to 1200 Watts at –48 VDC.
Current Requirements,
AC System
Configuration-dependent: use Network Design Tool for exact
requirements.
Current Requirements,
DC System
Configuration-dependent: use Network Design Tool for exact
requirements. For general planning purposes: 25 Amps at nominal –48
VDC; 29 Amps at –42 VDC maximum.
Input AC Power
Connector
IEC 320 C13 input connector. The Appendix titled “Cabling
Specifications” lists the AC power cords for a variety of countries and
regions.
AC Power Cable
Provided with 8 feet (2.3 m) of 3-conductor wire with plug.
AC Plug at
Customer end
20 A NEMA L620, 3-prong plug (domestic U.S.)
13 A 250 Vac BS1363, 3-prong fused plug (UK, Ireland)
CEE 7/7 (Continental Europe)
AS3112 (Australia/New Zealand)
CEI23-16/VII (Italy)
125V/15A North America
DC Input Connections
Three-position terminal block for 10 AWG wire (4 square millimeters).
Operating Environment
0°–40° C (32°–104° F) normal operation (50° C or 122° F up to 72 hours).
Maximum 85% relative humidity.
Shock
Withstands 10 G, 10 ms at 1/2 sine wave.
Vibration
Withstands 1/4 G, 20–500 Hz.
Heat Transfer to
Environment
AC-powered: 4,800 BTUs.
DC-powered: 4,100 BTUs.
Cisco MGX 8230 Installation and Configuration
A-2
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
MGX 8230 Processor Switching Module Specifications
Table A-1
Enclosure and Electrical Characteristics (continued)
Item
Value
MGX 8230 Performance
Cell bus bandwidth
Slots 3 to 5, 10 to 12:
~160 Mbps per slot, single speed
~320 Mbps per slot, double speed
Slots 6 to 7, 13 to 14
~160 Mbps per two slots, single speed
~320 Mbps per two slots, double speed
Alarm and error
handling
Same as MGX 8850 and IGX 8400 series switches
MGX 8230 Processor Switching Module Specifications
This section contains general specifications for the MGX 8230 Processor Switch Module
(MGX 8230-PXM). The information in Table A-2 includes information for the two types of back
cards—the PXM-UI user interface for the switch and the uplink card for trunking and CPE access.
Table A-2
PXM Specifications
Category
Description
Maximum switch fabric
throughput
2 times OC-12.
Control access
Control port: RJ-45 connector, EIA/TIA 232, DTE mode, asynchronous
interface 19,200 baud, 1 start bit, 1 stop bit, no parity bits.
(These ports exits on the
PXM-UI back card)
Maintenance port: RJ-45 connector, EIA/TIA 232, DTE mode,
asynchronous interface 9600 baud, 1 start bit, 1 stop bit, no parity bits.
LAN port: RJ-45 connector, 10BASET, 802.3 Ethernet.
4 OC-3 multi-mode fiber, SC connectors
4 OC-3 single-mode fiber, intermediate reach, SC connectors
(An uplink card can have 4 OC-3 single-mode fiber, long reach, SC connectors
one of these number and
type of connectors. The
wavelength on optical
lines is 1310 nm)
Uplink ports and
connectors
Number of logical ports
32 across all physical ports on the uplink card (regardless of line type).
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-3
Appendix A
Technical Specifications
MGX 8230 Processor Switching Module Specifications
Table A-2
PXM Specifications (continued)
Category
Description
LEDs on PXM front card Status for the card:
(LEDs display status, but
alarm history is a switch)
•
Green means active.
•
Red means failed.
•
Yellow indicates the standby card.
LAN activity: flashing green indicates activity.
Node alarm:
•
Blue indicates critical alarm
•
Red indicates major alarm.
•
Yellow indicates minor alarm.
Node power (note that each AC power supply also has an LED):
•
“DC OK A” is green for okay or red for trouble.
•
“DC OK B” is green for okay or red for trouble.
Alarm history: ACO
Port interface (for the uplink port):
•
Green means active and okay.
•
Red means active and local alarm.
•
Yellow means active and remote alarm.
•
No light means inactive or not provided.
LEDs on back cards
Green means active. No light means inactive or not provided.
Synchronization
8 kHz clock derived from the following sources:
(These clock sources
satisfy Stratum 4
requirements)
BITS clock interface
•
Internal 8 kHz clock (10 ppm).
•
Service modules or trunk line interfaces.
•
External BITS clock port.
•
T1 clock rate 1.544 MHz ± 32 ppm.
•
E1 clock rate 2.048 MHz ± 50 ppm (can be either sync or data signal).
E1/T1 with an RJ-45 connector.
E1 with an SMB connector.
Trunk history counters
Ingress, per connection:
Number of received cells with CLP = 0.
Number of received cells with CLP = 1.
Egress, per connection:
Number of received cells.
Number of transmitted cells.
Number of received cells with EFCI bit set.
Number of transmitted cells with EFCI bit set.
Cisco MGX 8230 Installation and Configuration
A-4
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
AUSM/B-8T1E1 Interface Characteristics
Table A-2
PXM Specifications (continued)
Category
Description
Connection capacities
supported by PXM
Maximum number of connections:
16,000 bi-directional channels for local switching.
32,000 bi-directional channels for switching across uplink card.
Maximum aggregate bandwidth:
600 Mbps local switching (service module to service module).
1,200 Mbps switching across uplink.
Cell memory: 256K cells.
Processor clock speed
and memory specifics
Clock speed: 200 MHz internal, 50 MHz external.
Flash memory: 2 Mbytes.
DRAM: 64 Mbytes, upgradeable to 128 Mbytes.
Secondary cache: 512 Kbytes.
BRAM: 128 Kbytes.
Hard disk: 4 Gbytes.
Alarm indicators
(audible and visual)
Central office-compatible alarm indicators and controls through a DB15
connector.
Maintenance features
Internal isolation loopback.
External remote loopback.
Hot-pluggable.
Card dimensions
Front card: 15.65 inches by 16.83 inches (39.75 cm by
42.75 cm)
Back cards: 7.25 inches by 4.125 inches (18.42 cm by
10.48 cm)
Power
Requires –48 VDC, dissipates 150W.
AUSM/B-8T1E1 Interface Characteristics
This section contains details for the AUSM/B-8T1E1. For physical characteristics, see Table A-3. For
the T1 and E1 characteristics, see Table A-3 and Table A-5, respectively. For ATM interface
characteristics, see Table A-6. For statistics and counters, see Table A-7.l
Table A-3
Physical Characteristics of the AUSM/B-8T1E1
Category
Description
LED Indicators Per Card
Active (green), Standby (yellow), Fail (red)
LED Indicators Per Line
One per line: Active and OK (green)
Active and Local Alarm (red)
Active and Remote Alarm (yellow)
Maintenance/Serviceability Facility loopback via loop up/down per ANSI T1.408 and
ATT TR 62411 (T1), CCITT G.7xx (E1)
Facility Loopback via Management Console
Internal Problem Isolation Loopbacks
Hot pluggable
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-5
Appendix A
Technical Specifications
AUSM/B-8T1E1 Interface Characteristics
Table A-3
Physical Characteristics of the AUSM/B-8T1E1 (continued)
Category
Description
Card Size
Front card: 7.25" x 16.25" (18.43 cm x 41.28 cm)
Back cards: 7" x 4.5" (17.78 cm x 11.43 cm)
Power
–48 VDC, 30W
Safety
EN 60950 2nd edition (including EN 41003) UL 1950 2nd edition
Compliance
T1: G.703, G.824
E1: G.703, G.823
ESD
IEC 61000-4-2
Table A-4
T1 Interface Characteristics
Category
Description
Line Interface
RJ-48 (100 ohms) on the LM-RJ48-8T1 back card
Line Rate
1.544 Mbps ± 50 bps (T1)
Synchronization
Transmitter can be loop-timed, receiver, or synchronized to node (normal
mode)
Line Code
Bi-polar 8 Zero Substitution (B8ZS) per ANSI T1.408 (T1)
Line Framing
Extended Superframe Format (ESF 24 frame multi-frame) per ANSI T1.408
ESF Maintenance
Bit-oriented alarm and loopback messages of ESF Data Link per ANSI
T1.408
Input Jitter Tolerance Per ITU-T G.824
Output Jitter
Per ITU-T G.824 using normal mode synchronization.
Physical Layer
Alarms
LOS, OOF, AIS, RAI
Physical Layer
Performance
Statistics
LCV, LES, LSES, CV, ES, MGX 8230, SEFS, AISS, UAS
Table A-5
E1 Interface Characteristics
Category
Description
Line Interface
Connector
RJ-48 (120 ohms) on LM-RJ48-8E1, or SMB (75 ohms) on
LM-SMB-8E1
Line Rate
2.048 Mbps ± 100 bps
Synchronization
Transmitter can be: loop timed, receiver, or synchronized to shelf (normal
mode)
Line Code
HDB3 (E1)
Line Framing
16-frame multi-frame as in G.704
Input Jitter Tolerance
As specified in ITU G.823 for 2.048 Mbps
Output Jitter Generation As specified in ITU G.823 for 2.048 Mbps
Cisco MGX 8230 Installation and Configuration
A-6
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
AUSM/B-8T1E1 Interface Characteristics
Table A-5
E1 Interface Characteristics (continued)
Category
Description
Physical Layer Alarms
LOS, OOF, AIS, RAI
Physical Layer
Statistics
LCV, LES, LSES, CV, ES, MGX 8230, SEFS, AISS, UAS
Table A-6
ATM Interface Characteristics
Category
Description
Standards
ATM UNI v3.1, ITU-T G.804, per CCITT I.361.
Channel Configuration
1000 per card, across any of the T1 or E1 ports.
VPI/VCI Ranges
VPI: 0–255.
VCI: 0–4096.
Traffic Classes
CBR, VBR, VBR+.
UPC Parameters
PCR, SCR (VBR), CCDV (CBR).
Congestion Control
Support
ForeSight (toward Network for VBR+).
ForeSight Parameters
MIR, PIR, Rate Up, Rate Down, QIR, QIR Timeout, IBS.
Table A-7
AUSM/B-8T1E1 Statistics and Counters
Counter Type
Description
Per Port
Number of cells received from the interface.
Number of cells received with unknown VPI/VCI.
Last known VPI/VCI received from the port.
Number of cells discarded due to error in Cell Header.
Number of cells received with non-zero GRC field.
Number of cells transmitted to the interface.
Number of cells transmitted for which EFCI was set.
Number of egress cells discarded due to service interface physical
alarm.
Endpoint (channel)
Ingress
Number of cells received from port.
Number of cells received from the port with CLP = 1.
Number of cells received from the port with EFCI = 1.
Number of cells from the port discarded due to queue exceeded
QDepth.
Number of cells (with CLP) set) discarded due to queue exceeded
CLP threshold.
Number of cells from the port for which CLP was set due to UPC
violations.
ATMizer Channel Counters
Ingress
Number of cells transmitted to cell bus.
Number of cells to cell bus for which EFCI was set.
Number of cells to cell bus discarded due to shelf alarm.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-7
Appendix A
Technical Specifications
FRSM-2CT3 Specifications
Table A-7
AUSM/B-8T1E1 Statistics and Counters
Counter Type
Description
Egress
Number of cells received from the cell bus.
Number of cells discarded due to queue exceeded QDepth (per
Egress Q).
Number of cells discarded due to queue exceeded CLP threshold
(per Egress Q).
Number of cells received with CLP = 1.
Other Counters
Ingress
Number of OAM cells discarded.
Number of AIS cells received from the port.
Number of RDI (FERF) cells received from the port.
Number SegmentLpBk cells received from the port.
Number of SegmentLpBk cells transmitted to cell bus.
Egress
Number of OAM cells discarded.
Number of AIS cells transmitted to the port.
Number of SegmentLpBk cells transmitted to the port.
Number of SegmentLpBk cells received from the port.
Diagnostic Statistics
Peak Queue Depth (Ingress: per channel).
FRSM-2CT3 Specifications
This section provides details for the FRSM-2CT3. Topics consist of the following:
•
Transport technology standards with which the card complies (Table A-8)
•
General physical attributes of the card, such as LEDs on the faceplate (Table A-9)
•
Line and framer characteristics (Table A-10 and “FRSM-2CT3 Framer” section)
•
Line alarms (“FRSM-2CT3 Line Alarms”)
Table A-8
Frame Relay Interface Standards
Interface
Standard
Frame Relay Interface
ANSI T1.618, 2-octet header
ATM Layer
CCITT I.361 and ATM UNI v3.1
AAL Layer
AAL5 per ITU-T I.363
FR-Cell Interworking
Per ITU-T I.555 and I.36x.1, as summarized in “ATM-to-Frame Relay
Interoperability Implementation Agreement” v 1.0
Table A-9
FRSM-2CT3 Front Card Physical Characteristics
Feature
Significance or Value
Power
–48 VDC, 60W (estimated)
Cisco MGX 8230 Installation and Configuration
A-8
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
FRSM-2CT3 Specifications
Table A-9
FRSM-2CT3 Front Card Physical Characteristics (continued)
Feature
Significance or Value
Card Status Indicator
LEDs
Active (Green),
Failed (Red),
Standby (Yellow)
Line Status Indicator
LEDs
Active & Okay (Green),
Active & Local Alarm (Red),
Active & Remote Alarm (Yellow)
Reliability
> 85000 hours MTBF (target)
Card Size
7.25 inches by 16.5 inches
Table A-10 FRSM-2CT3 Line Level
Feature
Significance or Value
Number of T3 Lines
Two
Line Interface Connector
75 ohm BNC
Line Rate
44.736 Mbps +/- 20 ppm
Line Coding
B3ZS
Transmit Timing
Normal or Loop timed
Input Jitter Tolerance
Per GR-449-CORE, ITU-T G.824
Output Jitter
0.05 UI maximum with jitter-free input clock
Output Pulse
Per T1.102.1993
FRSM-2CT3 Framer
The FRSM-2CT3 line framer:
•
Supports M13 or C-bit parity format.
•
Performs required inversion of second and fourth multiplexed DS1 streams per ANSI T1.107.
•
Generates loop-up code to the far-end device to loop back any of the DS1s or entire DS3 signal
stream by way of the FEAC channel.
•
Automatically detects the incoming loop-up codes from the far-end device as well as loop back any
of the DS1s or entire DS3 signal stream back to the far-end device. The loopback occurs at the M13
framer chip.
FRSM-2CT3 Line Alarms
For line alarms, the FRSM-2CT3 supports:
•
Detection and generation of Remote Alarm Indicator (RAI) signal (also known as FERF and Yellow
signal)
•
Detection and generation of Alarm Indication Signal (AIS)
•
Detection of Out of Frame (OOF) condition
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-9
Appendix A
Technical Specifications
FRSM-2T3E3 Specifications
•
Detection of Loss of Frame (LOS) condition
•
Automatic generation of Far End Block Error (FEBE)
FRSM-2T3E3 Specifications
This section provides details for the FRSM-2T3E3. Where appropriate, it has separate sections for T3
and E3 technologies. Topics consist of the following:
•
Transport technology standards with which the card complies (Table A-11)
•
General physical attributes of the card, such as LEDs on the faceplate (Table A-12)
•
Line and framer characteristics for T3 operation (Table A-13 and “T3 Framer Level”)
•
Line and framer characteristics for E3 operation (Table A-14 and “E3 Framer Level”)
•
Line alarms (“FRSM-2T3E3 Line Alarms”)
Table A-11 Frame Relay Interface Standards
Interface
Standard
Frame Relay Interface
ANSI T1.618, 2-octet header
ATM Layer
CCITT I.361 and ATM UNI v3.1
AAL Layer
AAL5 ITU-T I.363
FR-Cell Interworking
Per ITU-T I.555 and I.36x.1, as summarized in ATM-to-Frame Relay
Interoperability Implementation Agreement v 1.0
Table A-12 FRSM-2T3E3 Front Card Physical Characteristics
Feature
Significance or Value
Power
–48 VDC, 60W (estimated)
Card Status Indicator LEDs
Active (Green),
Failed (Red),
Standby (Yellow)
Line Status Indicator LEDs
Active & Okay (Green),
Active & Local Alarm (Red),
Active & Remote Alarm (Yellow)
Reliability
> 85000 hours MTBF (target)
Card Size
7.25 inches by 16.5 inches
FRSM-2T3E3 T3 Line
The T3 line characteristics appear in Table A-13.
Table A-13 T3 Line Level
Feature
Significance or Value
Number of T3 Lines
Two
Cisco MGX 8230 Installation and Configuration
A-10
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
FRSM-2T3E3 Specifications
Table A-13 T3 Line Level (continued)
Feature
Significance or Value
Line Interface
Connector
75 ohm BNC
Line Rate
44.736 Mbps +/- 20 ppm
Line Coding
B3ZS
Transmit Timing
Normal or Loop timed
Input Jitter Tolerance
Per GR-499-CORE, ITU-T G.824
Output Jitter
0.05 UI maximum with jitter-free input clock
Output Pulse
Per ANSI T1.102
T3 Framer Level
For the framing characteristics of T3 operation, the FRSM-2T3E3:
•
Supports C-bit parity and M13 DS3 format.
•
Frames to a DS3 signal with a maximum average reframe time that meets the requirements set by
TR-TSY-000009 and GR-499-CORE.
•
Detects the alarm indication signal (AIS) in milliseconds in the presence of a 10-3 bit error rate.
•
When in-frame, indicates M-bit or F-bit framing errors as well as P-bit errors. In C-bit parity mode,
it also indicates both C-bit parity errors and far end block errors.
FRSM-2T3E3 E3 Line
For characteristics of the line on an FRSM-2T3E3 with an E3 back card see figure A14:
Table A-14 E3 Line Level
Feature
Significance or Value
Number of E3 Lines
Two
Line Interface Connector
75 ohm BNC
Line Rate
34.368 Mbps +/- 20 ppm
Line Coding
HDB3
Transmit Timing
Normal or Loop timed
Input Jitter Tolerance
Per ITU-T G.823
Output Jitter
0.05 UI maximum with jitter-free input clock per AT&T TR54014
Output Pulse
Per ITU-T G.703
E3 Framer Level
For line framing, the E3 operation of the FRSM-2T3E3 complies with ITU-T G.751.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-11
Appendix A
Technical Specifications
FRSM-HS2 Specifications
FRSM-2T3E3 Line Alarms
For line alarms, the FRSM-2T3E3 supports:
•
Detection and generation of Remote Alarm Indicator (RAI) signal (also known as FERF and Yellow
signal)
•
Detection and generation of Alarm Indication Signal (AIS)
•
Detection of Out of Frame (OOF) condition
•
Detection of Loss of Frame (LOS) condition
•
Automatic generation of Far End Block Error (FEBE)
Statistics and Counter Specifications
See the section titled “Counters and Statistics for FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2” for
lists of applicable statistics and counters.
FRSM-HS2 Specifications
The FRSM-HS2 is the Frame Relay module with two HSSI ports. The topics in this section are:
•
Transport technology standards with which the card complies (Table A-15)
•
General physical attributes of the card, such as LEDs on the faceplate (Table A-16)
•
Line and framer characteristics (Table A-17)
For lists of the counters and statistics that are available on the FRSM-VHS series of cards, see the
section titled “Counters and Statistics for FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2.”
Table A-15 Frame Relay Interface Standards
Interface
Standard
Frame Relay Interface
ANSI T1.618, 2-octet header
ATM Layer
CCITT I.361 and ATM UNI v3.1
AAL Layer
AAL5 per ITU-T I.363
FR-Cell Interworking
Per ITU-T I.555 and I.36x.1, as summarized in ATM-to-Frame Relay
Interoperability Implementation Agreement v 1.0
Table A-16 FRSM-HS2 Physical Characteristics
Feature
Significance or Value
Power
–48V, 75W (estimated)
The SCSI2-2HSSI back card consumes 5 watts at
5 VDC and 6 watts at -5 VDC.
Card Status Indicator LEDs
Active (Green),
Failed (Red),
Standby (Yellow)
Cisco MGX 8230 Installation and Configuration
A-12
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
Counters and Statistics for FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2
Table A-16 FRSM-HS2 Physical Characteristics (continued)
Feature
Significance or Value
Line Status
Indicator LEDs
Active & Okay (Green),
Active & Local Alarm (Red),
Active & Remote Alarm (Yellow)
Reliability
> 85000 hours MTBF (target)
Card Size
Front card: 7.25" x 16.25" (18.43 cm x 41.28 cm)
Back card: 7" x 4.5" (17.78 cm x 11.43 cm)
Table A-17 FRSM-HS2 Line Characteristics
Feature
Significance or Value
Number of HSSI Lines
Two
Connector Type
SCSI-2
Signaling Rate
52 Mbps max
Line Alarms
•
Control lead is inactive
•
Recovered clock does not match configured line rate
Synchronization
Transmitter may be either loop-timed to Receiver (DTE mode) or
synchronized to shelf (DCE mode)
Electrical Interchange
Characteristics
ITU-T V.12
Counters and Statistics for FRSM-2CT3, FRSM-2T3E3, and
FRSM-HS2
This section lists counters and statistics that apply to most types of cards in the FRSM-VHS group.
Table A-18 Counters per Line
Counter
Received frames lost due to aborts
Received frames lost due to illegal header (EA bit)
Received frames lost due to CRC errors
Received frames with bit alignment errors
Received frames with unknown DLCI
Received frames with illegal frame length
Received good frame
Transmit frames lost due to under-run/Abort count
Transmit good frame
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-13
Appendix A
Technical Specifications
Counters and Statistics for FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2
Table A-18 Counters per Line (continued)
Counter
LMI status inquiry request count
LMI signaling protocol (keep-alive time-out count)
LMI sequence number error count
LMI status transmit count (in response to request)
LMI update status transmit count (in response to configuration changes
Frames with FECN set count
Frames with BECN set count
DE frames discarded count
Number of frames reassembled but discarded due to service interface physical layer alarm
Table A-19 Service-Related Statistics
Service Statistic
Number of received frames
Number of bytes received
Number of frames received with DE=1
Number of frames received but discarded
Number of received bytes discarded
Number of frames received but discarded due to
•
CRC error
•
Illegal frame length
•
Alignment error
•
Abort
Number of frames reassembled and transmitted
Number of frames reassembled and transmitted with DE=1
Number of frames discarded due to reassembly errors
Number of frames transmitted
Number of bytes transmitted
Number of frames transmitted with DE set
Number of frames transmitted during LMI logical port alarm
Frames FECN set count
Frames BECN set count
Number of transmit frames discarded
Number of transmit bytes discarded
Cisco MGX 8230 Installation and Configuration
A-14
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
Counters and Statistics for FRSM-2CT3, FRSM-2T3E3, and FRSM-HS2
Table A-19 Service-Related Statistics (continued)
Service Statistic
Number of transmit frames discarded due to:
•
CRC error
•
Illegal frame length
•
Alignment error
•
Abort
•
DE egress queue threshold exceeded
•
Physical link failure
Table A-20 ATM Cell-Related Statistics
ATM Cell Statistic
Number of cells transmitted to PXM
Number of cells discarded due to intershelf link alarm
Number of cells transmitted with CLP bit set
Number of AIS cells transmitted
Number of FERF cells transmitted
Number of BCM cells transmitted
Number of end-to-end loop back cells transmitted
Number of segment loop back cells transmitted
Number of cells received from PXM
Number of cells received with CLP bit set
Number of AIS cells received
Number of FERF cells received
Number of BCM cells received
Number of end-to-end loopback cells received
Number of segment loopback cells received
Number of OAM cells discarded due to CRC-10 error
Table A-21 Diagnostic-Related Statistics
Diagnostic Statistic
Header of last cell with unknown LCN
Header of last received frame with unknown DLCI
ECN current queue depth
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-15
Appendix A
Technical Specifications
FRSM-8T1 Specification
Table A-22 Troubleshooting Statistics
Troubleshooting Statistic
ECN current queue depth, per channel
FRSM-8T1 Specification
This section provides information on the T1 operation of the FRSM-8T1E1 card set. Topics are
•
General physical information about the card set (Table A-23)
•
Information about the Frame Relay service (Table A-24)
•
System-level interface (Table A-25)
•
Statistics and counters (Table A-26)
Table A-23 General Card Specifications
Category
Description
Indicators per card
Active (Green), Standby (Yellow), Fail (Red)
Indicators per line
Active & Okay (Green)
Active & Local Alarm (Red)
Active & Remote Alarm (Yellow)
Line Interface connector
RJ-48 when used with RJ48-8T1 back card
Line Rate
1.544 Mbps ± 50 bps
Line Framing
ESF per ATT TR 54016
Maintenance/Serviceability
Features
Internal Problem Isolation Loopbacks
Hot-pluggable cards
Reliability, MTBF
> 65000 hours
Card Size
FRSM-8T1: 7.25" x 16.25"
LM-DB15-8T1: 7.0" x 4.5"
Power: –48 VDC, 30W with 8 active T1 lines
Table A-24 Frame Relay Service With T1 Lines
Category
Description
Synchronization
Transmitter may be either loop-timed to receiver or synchronized
to shelf (called normal mode)
Input Jitter Tolerance
Per ITU-T G.824
Output Jitter Generation
Per ITU-T G.824 using normal mode synchronization
Physical Layer Alarms
LOS, OOF, AIS, RAI
Number of Frame Relay Ports
One–a single Frame Relay stream occupying N consecutive time
slots
Cisco MGX 8230 Installation and Configuration
A-16
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
FRSM-8T1 Specification
Table A-24 Frame Relay Service With T1 Lines (continued)
Category
Description
Frame Relay Interface Rates
Either of the following:
•
56 Kbps
•
N x 64 Kbps (where N is the number of consecutive time slots)
Frame Relay Interface
Per ANSI T1.618, 2-octet header
Frame Relay Performance
Counters (per Port; N x DS0)
Received frames discarded due to Aborts
Received frames discarded due to illegal header (EA bit)(s)
Received frames discarded due to CRC errors (s)
Received frames discarded due to alignment errors (s)
Received frames discarded due to unknown DLCI (s)
Received frames discarded due to illegal frame length (s)
Received frames discarded due to DE threshold exceeded
Received frames with DE already set
Received frames with FECN already set
Received frames with BECN already set
Received frames tagged FECN
Received frames (s)
Received bytes (s)
Transmit frames discarded due to underrun
Transmit frames discarded due to Abort
Transmit frames discarded due to egress Q-depth exceeded (s)
Transmit bytes discarded due to egress Q-depth exceeded (s)
Transmit frames discarded due to egress DE threshold
exceeded Transmit frames (s)
Transmit bytes(s)
Transmit Frames with FECN set (s)
Transmit Frames with BECN set (s)
LMI receive status inquiry request count (s)
LMI transmit status inquiry request count
LMI invalid receive status count (s)
LMI signaling protocol (keep alive time-out count) (s)
LMI sequence number error count (s)
LMI receive status transmit count (in response to request)
LMI transmit status transmit count (in response to request)
Transmit frames during LMI alarm (s)
Transmit bytes during LMI alarm (s)
LMI update status transmit count (in response
to configuration changes)
Diagnostics (per port)
Last unknown DLCI received
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-17
Appendix A
Technical Specifications
FRSM-8T1 Specification
Table A-25 System Interface
Category
Description
ATM Layer
Per ITU-T I.361 and ATM UNI v3.1
AAL Layer
AAL5 per ITU-T I.363
FR-Cell Interworking
Per ITU-T I.555 and I.36x.1, as summarized in Frame Relay Forum,
FR/ATM PVC Interworking Implementation Agreement FRF.5
Table A-26 List of Counters
Category
Description
Channels (endpoints) per card
256, which you can allocate across any of the interfaces
Service Counters
Number of frames received (s)
Number of bytes received (s)
Number of frames received with DE already set (s)
Number of bytes received with DE already set (s)
Number of frames received with unknown DLCI
Number of frames received but discarded (s)
Number of received bytes discarded (s)
Number of received bytes discarded due to exceeded Q-depth (s)
Number of frames received and discarded due to: intershelf alarm
exceeded DE threshold (s)
exceeded Q depth (s)
Number of frames received with FECN set
Number of frames received with BECN set
Number of frames received tagged FECN
Number of frames received tagged BECN
Note that an (s) at the end of
the description means the
data in the counter is usable as
a statistic.
Number of frames transmitted (s)
Number of bytes transmitted (s)
Cisco MGX 8230 Installation and Configuration
A-18
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
FRSM-8E1 Specification
Table A-26 List of Counters (continued)
Category
Description
Number of frames transmitted with DE set (s)
Number of frames discarded due to reassembly errors (s)
Number of frames transmitted during LMI logical port alarm(s)
Number of frames transmitted with FECN set (s)
Number of frames transmitted with BECN set (s)
Number of transmit frames discarded (s)
Number of transmit bytes discarded
Number of transmit frames discarded due to: CRC error (s)
egress Q depth exceeded (s)
egress DE threshold exceeded source abort
physical link failure (T1)
ATM cells: Number of cells transmitted to PXM
Number of cells transmitted with CLP bit set
Number of OAM AIS cells transmitted (s)
Number of OAM FERF cells transmitted (s)
Number of BCM cells transmitted
Number of OAM end-to-end loopback cells transmitted (s)
Number of OAM segment loopback cells transmitted
Number of cells received from PXM
Number of cells received with CLP bit set
Number of OAM AIS cells received (s)
Number of OAM FERF cells received (s)
Number of BCM cells received
Number of OAM end-to-end loopback cells received (s)
Number of OAM segment loopback cells received
Number of OAM cells discarded due to CRC-10 error (s)
Statistics
If any of the counters in the preceding category of Service Counters
includes an “(s),” you can configure it for statistics usage
Diagnostics
Last unknown LCN received
Number of cells with unknown LCN
FRSM-8E1 Specification
This section provides information on the E1 operation of the FRSM-8T1E1 card set. Topics are:
•
General physical information about the card set (Table A-27)
•
Information about the Frame Relay service (Table A-28)
•
System-level interface (Table A-29)
•
Statistics and counters (Table A-30)
Table A-27 General Card Specifications
Category
Description
Line Interface connector
RJ-48 when used with RJ-48-8E1 line module.
SMB when used with SMB-8E1 line module
Line Rate
2.048 Mbps ± 100 bps
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-19
Appendix A
Technical Specifications
FRSM-8E1 Specification
Table A-27 General Card Specifications (continued)
Category
Description
Synchronization
Transmitter may be either loop-timed to receiver or synchronized to
shelf (normal mode)
Input Jitter Tolerance
Per ITU-T G.823
Output Jitter Generation
Per ITU-T G.823
Physical Layer Alarms
LOS, OOF, AIS, RAI
Indicators per card
Active (Green), Standby (Yellow), Fail (Red)
Indicators per line
Active & Okay (Green)
Active & Local Alarm (Red)
Active & Remote Alarm (Yellow)
Maintenance/Serviceability
Features
Internal Problem Isolation Loopbacks
Hot-pluggable cards
Reliability, MTBF
> 65000 hours
Card Size
FRSM-8E1: 7.25" x 16.25" (18.43 cm x 41.28 cm)
RJ48-8E1: 7.0" x 4.5" (17.78 cm x 11.43 cm)
SMB-8E1: 7.0" x 4.5" (17.78 cm x 11.43 cm)
Power
–48 VDC, 30W with 8 active E1 lines
Table A-28 Frame Relay Service With E1 Lines
Category
Description
Number of Frame Interfaces
1–31 occupying N, where 1 < N < 31. Sum of all < 31 for CCS or
1–30 for CAS.
Frame Relay Interface Rates
Either 56 Kbps orN x 64 Kbps, where N is the same as defined in
the preceding item the preceding item “Number of Frame
Interfaces.”
Ingress
8000-cell buffer shared between virtual channels/paths
standard usage parameter control (UPC)
Selective Cell Discard
Virtual Circuit Queuing
EFCI setting per VC
Egress
8000-cell storage capacity shared between four ports
Up to 12 user-selectable egress queues per port
Selective Cell Discard
EFCI setting per Queue
Frame Relay Interface
Per ANSI T1.618, 2-octet header
Cisco MGX 8230 Installation and Configuration
A-20
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
FRSM-8E1 Specification
Table A-28 Frame Relay Service With E1 Lines (continued)
Category
Description
Frame Relay Performance
Received frames discarded due to Aborts
Counters (per Port; N x DS0): Received frames discarded due to illegal header (EA bit)(s)
Received frames discarded due to CRC errors (s)
Received frames discarded due to alignment errors (s)
Received frames discarded due to unknown DLCI (s)
Received frames discarded due to illegal frame length (s)
Received frames discarded due to DE threshold exceeded
Received frames with DE already set
Received frames with FECN already set
Received frames with BECN already set
Received frames tagged FECN
Received frames (s)
Received bytes (s)
Transmit frames discarded due to underrun
Transmit frames discarded due to Abort
Transmit frames discarded due to egress Q-depth exceeded (s)
Transmit bytes discarded due to egress Q-depth exceeded (s)
Transmit frames discarded due to egress DE threshold exceeded
Transmit frames (s)
Transmit bytes(s)
Transmit Frames with FECN set (s)
Transmit Frames with BECN set (s)
LMI receive status inquiry request count (s)
LMI transmit status inquiry request count
LMI invalid receive status count (s)
LMI signaling protocol (keep alive time-out count) (s)
LMI sequence number error count (s)
LMI receive status transmit count (in response to request)
LMI transmit status transmit count (in response to request)
Transmit frames during LMI alarm (s)
Transmit bytes during LMI alarm (s)
LMI update status transmit count (in response to configuration
changes)
Diagnostics (per port):
Last unknown DLCI that arrived
Table A-29 System Interface
Category
Description
ATM Layer
Per ITU-T I.361 and ATM UNI v3.1
AAL Layer
AAL5 per ITU-T I.363
FR-Cell Interworking
Per ITU-T I.555 and I.36x.1, as summarized in Frame Relay Forum,
FR/ATM PVC Interworking Implementation Agreement FERF.5
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-21
Appendix A
Technical Specifications
FRSM-8E1 Specification
Table A-30 List of Counters
Category
Description
Channels (Endpoints)
256 per card—can be allocated across any of the Frame Relay
interfaces
Counters
Service Counters: Number of frames received (s)
Number of bytes received (s)
Number of frames received with DE already set (s)
Number of bytes received with DE already set (s)
Number of frames received with unknown DLCI
Number of frames received but discarded (s)
Number of received bytes discarded (s)
Number of received bytes discarded due to exceeded Q-Depth (s)
Number of frames received and discarded due to
•
intershelf alarm
•
exceeded DE threshold (s)
•
exceeded Q depth (s)
Number of frames received with FECN set
Number of frames received with BECN set
Number of frames received tagged FECN
Number of frames received tagged BECN
Number of frames transmitted (s)
Number of bytes transmitted (s)
Number of frames transmitted with DE set (s)
Number of frames discarded due to reassembly errors (s)
Number of frames transmitted during LMI logical port alarm(s)
Number of frames transmitted with FECN set (s)
Number of frames transmitted with BECN set (s)
Number of transmit frames discarded (s)
Number of transmit bytes discarded
Number of transmit frames discarded due to: CRC error (s)
egress Q depth exceeded (s)
egress DE threshold exceeded source abort physical link failure (T1)
Cisco MGX 8230 Installation and Configuration
A-22
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
Circuit Emulation Service Module for T1 Operation
Table A-30 List of Counters (continued)
Category
Description
ATM cells: Number of cells transmitted to PXM
Number of cells transmitted with CLP bit set
Number of OAM AIS cells transmitted (s)
Number of OAM FERF cells transmitted (s)
Number of BCM cells transmitted
Number of OAM end-to-end loopback cells transmitted (s)
Number of OAM segment loopback cells transmitted
Number of cells received from PXM
Number of cells received with CLP bit set
Number of OAM AIS cells received (s)
Number of OAM FERF cells received (s)
Number of BCM cells received
Number of OAM end-to-end loopback cells received (s)
Number of OAM segment loopback cells received
Number of OAM cells discarded due to CRC-10 error (s)
Statistics: All of the above counters followed by an (s) can be
configured as statistics.
Diagnostics: Last unknown LCN received
Cells with unknown LCN count
Card General
Circuit Emulation Service Module for T1 Operation
This section contains operational details for the CESM 8T1E1 with the RJ48-8T1 back card.
Table A-31 CESM 8T1 Card Information
Category
Description
Back Card
RJ48-8T1
Line Rate
T1: 1.544 Mbps ±50 bps
Transmit Clocking
Normal clock or SRTS generated
Line Coding
B8ZS
Frame mode
ESF
Line alarms
Loss or Signal (LOS)
Loss of Frame (LOF)
Loss of multiframe (LOMF)
Remote loss of signal or frame (RAI)
All ones received (AIS)
Bi-polar violation
Alarm indication times
Near end alarm up-count
Near end alarm down-count
Near end alarm maximum count
Far end alarm up-count
Far end alarm down-count
Far end alarm maximum count
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-23
Appendix A
Technical Specifications
Circuit Emulation Service Module for E1 Operation
Table A-31 CESM 8T1 Card Information (continued)
Category
Description
Supported OAM cells
AIS
FERF
End-to-end loopback
Segment loopback
RTD loopback
BCM
Physical Layer Performance
Statistics
N/A
LED Indicators Per Card
Active (green), Failed (red), Standby (yellow)
BERT
Active (green), Errors (yellow)
1:N Redundancy
Active (green)
Indicator for each T1
Active (green)
Reliability, MTBF
Card Size
Front card: 7.25" x 16.25" (18.43 cm x 41.28 cm)
Back card: 7" x 4.5" (17.78 cm x 11.43 cm)
Power
48 VDC, 30W
Loopbacks
On or Off
Circuit Emulation Service Module for E1 Operation
This section contains operational details for the CESM-8T1E1 with an E1 back card.
Table A-32 CESM 8E1 Card Set Details
Category
Description
Back Card
RJ48-8E or SMB-8E1
Line Rate
E1: 2.048 Mbps ± 100 bps (50 ppm)
Transmit Clocking
Normal clock or SRTS generated
Line Coding
HDB3
Frame mode
single-frame
multi-frame
Line alarms
Loss or Signal (LOS)
Loss of Frame (LOF)
Loss of multi-frame (LOMF)
Remote loss of signal or frame (RAI)
All ones received (AIS)
Bi-polar violation
Cisco MGX 8230 Installation and Configuration
A-24
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
Physical and Electrical Characteristics for Cards
Table A-32 CESM 8E1 Card Set Details (continued)
Category
Description
Alarm indication times
Near end alarm up-count
Near end alarm down-count
Near end alarm maximum count
Far end alarm up-count
Far end alarm down-count
Far end alarm maximum count
Supported OAM cells
AIS
FERF
End-to-end loopback
Segment loopback
RTD loopback
BCM
Physical Layer Performance
Statistics
N/A
Indicators
Card-level
Active (green), Failed (red), Standby (yellow)
BERT
Active (green), Errors (yellow)
1:N Redundancy
Active (green)
Indicator for each T1
Active (green)
Reliability, MTBF
Card Size
Front card: 7.25" x 16.25" (18.43 cm x 41.28 cm)
Back card: 7" x 4.5" (17.78 cm x 11.43 cm)
Power
-48VDC, 30 W
Loopbacks
On or Off
Physical and Electrical Characteristics for Cards
For quick reference, Table A-33 shows physical dimensions and power consumption for each card.
Detailed information for each card appears in the section of this appendix for a specific card.
Table A-33 Physical Characteristics and Power Consumption by Card
Module
Back Cards
Front Card
Dimensions
(inches)
Back Card
Dimensions
(inches)
FRSM-8T1
8 T1, 8 E1
7.25 x 16.25
7.00 x 4.50
1.74 lbs/
0.76 lbs
30 Watts
2 T3
7.25 x 16.25
7.00 x 4.50
1.74 lbs/
0.76 lbs
60 Watts
FRSM-8E1
Weight (front and Power
back card)
Consumption
FRSM-8T1c
FRSM-8E1c
FRSM-2CT3
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-25
Appendix A
Technical Specifications
Electromagnetic Compatibility
Table A-33 Physical Characteristics and Power Consumption by Card (continued)
Module
Back Cards
Front Card
Dimensions
(inches)
FRSM-2T3E3
2 T3, 2 E3
7.25 x 16.25
7.00 x 4.50
1.74 lbs/
0.76 lbs
60 Watts
FRSM-HS2
2 HSSI
7.25 x 16.25
7.00 x 4.50
1.74 lbs/
0.6 lbs
75 Watts
CESM-8T1E1
8 T1, 8 E1
7.25 x 16.25
7.00 x 4.50
1.74 lbs
0.76 lbs
30 Watts
AUSM/B-8T1E1 8-T1, 8-E1
7.25 x 16.25
7.00 x 4.50
1.74 lbs
0.76 lbs
30 Watts
PXM1
15.65 x 15.83
7.00 x 4.5
4.80 lbs
100 Watts
OC-3c/STM-1
Back Card
Dimensions
(inches)
Weight (front and Power
back card)
Consumption
Electromagnetic Compatibility
This section lists the national and international standards for electromagnetic compatibility to which
the MGX 8230 complies. It consists of a list of reference documents, a table (Table A-34) that indicates
applicability of the standards, and the test levels for CE mark immunity.
The applicable standards for electromagnetic compatibility are
•
NEBS Systems Requirements (GR-1089-CORE)
•
EN 55022/08.94
•
EN 50081-1/01.92 and EN 50082-1/01.92 (Generic Immunity Requirements), International
Electromechanical Commission (IEC 61000-4-2 through IEC 61000-4-5) European Norm
designation EN 61000-4-2 through EN 61000-4-5
Details on how each standard applies in this Cisco product appear in Table A-34.
Table A-34 Electromagnetic Compatibility and Immunity
Category
AC-Powered (110/220 VAC
DC-Powered (-48V)
U.S.A EMC
FCC Part 15, Class A
not applicable
Japan EMC
Austel 3548 Class A
not applicable
Australia EMC VCCI Class A
not applicable
CE mark
not applicable
Immunity
EMC: EN 55022 Class A
•
EN 50082-1 (generic
immunity)
•
EN 61000-4-2 through -5
Cisco MGX 8230 Installation and Configuration
A-26
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
Conformance
Table A-34 Electromagnetic Compatibility and Immunity (continued)
Category
AC-Powered (110/220 VAC
DC-Powered (-48V)
NEBS
not applicable
EMC:
GR-1089-CORE Class A (radiated and
magnetic fields) and line conductance.
(EMC)
GR-1089-CORE ESD (8 KV contact) RS
(10 V/meter) CS (clause 3.3.3)
European Telecom Standards (ETSI) for Surge:
ETSI 300 386-1, DC power leads only
(200 VAC–1000 VAC)
The levels for the mandatory CE mark immunity tests are
•
For IEC 61000-4-2 (ESD), the test level is 4.
•
For IEC 61000-4-3 (RS), the test level is 3.
•
For IEC 61000-4-4 (EFT), the test level is 4.
•
For IEC 61000-4-5 (Surge), the test level is 3.
Conformance
This section contains standards compliance information for features on the MGX 8230.
ATM UNI
The ATM specifications for the User-Network Interface to which the MGX 8850 complies are
•
ATM Forum–ATM UNI, V3.1, 1995.
•
ITU Recommendation I.361–B-ISDN ATM Layer Specification, March 1993.
•
ITU Recommendation I.371–Traffic Control and Congestion Control in B-ISDN, March 1993.
•
ITU Recommendation I.432–B-ISDN User Network Interface—Physical Interface Specification,
March 1993.
•
ITU Recommendation I.610–B-ISDN Operation and Maintenance Principles and Functions,
Specification, November 1995.
•
ANSI T1E1.2/94-002R1, Draft–B-ISDN and DS1/ATM User Network Interfaces: Physical Layer
Specification.
•
ANSI T1E1.2/94-020, Draft–B-ISDN Customer Installation Interfaces, Physical Media Dependent
Specification.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-27
Appendix A
Technical Specifications
Conformance
SONET/SDH
The standards and responsible organizations with which MGX 8850 SONET technology complies are
as follows:
•
Bell Communications Research–SONET Transport Systems: Common Generic Criteria,
GR-253-CORE, Issue 2, 1995.
•
Bell Communications Research–Broadband Switching System Generic Requirements,
GR-1110-CORE, Issue 1, Sept. 1994.
•
Bell Communications Research–ATM and ATM AAL Protocols, GR-1113-CORE, Issue 1, July
1994.
•
Bell Communications Research–Generic Requirements for Operations of Broadband Switching
Systems, GR-1248-CORE, Issue 2, Rev 1.
•
ITU-T G.707–Network Node Interface for the Synchronous Digital Hierarchy.
•
ITU Recommendation G.782–Types and General Characteristics of Synchronous Digital Hierarchy
(SDH) Equipment, January 1994.
•
ITU Recommendation G.783–Characteristics of Synchronous Digital Hierarchy (SDH) Equipment
Functional Blocks, January 1994.
•
ITU Recommendation G.832–Transport of SDH Elements on PDH Networks: Frame and
Multiplexing Structures, November 1993.
•
ITU Recommendation G.958–Digital Line Systems based on the Synchronous Digital Hierarchy
for use on Optical Fibre Cables, November 1994.
•
ANSI T1.105–Digital Hierarchy–Optical Interface Rates and Formats Specifications (SONET),
1991.
•
ANSI T1.231–Digital Hierarchy–Layer 1 In-Service Digital Transmission Performance Monitoring
(SONET), 1993.
Frame Relay
The standards and responsible organizations with which MGX 8230 Frame Relay technology complies
are as follows:
•
FRF.1.1
•
FRF.2.1
•
FRF.3.1
•
FRF.5
•
FRF.6
•
FRF.8
Circuit Emulations Service
ATM Forum CES 2.0.
Cisco MGX 8230 Installation and Configuration
A-28
Release 1.0, Part Number 78-10616-01, June 2000
Appendix A
Technical Specifications
Conformance
Safety
The MGX 8230 enclosure meets all applicable regulatory agency Product Safety requirements.
•
UL 1950, Third Edition (Standard for Safety, Information Technology Equipment, Including
Electrical Business Equipment).
•
CSA C22.2-#950- M95, (Standard for Safety, Information Technology Equipment, Including
Electrical Business Equipment).
•
EN 60 950 (Safety of Information Technology Equipment, Including Electrical Business
Equipment).
•
TS001 Austel-Safety Requirements for Customer Equipment. (Including AS3260, Safety of
Information Technology Equipment)-Australia.
•
EN 41003 (European Product Safety Standard for Telecommunications Equipment).
Environmental
The MGX 8230 adheres to the Bellcore GR-63-CORE environmental standard.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
A-29
Appendix A
Technical Specifications
Conformance
Cisco MGX 8230 Installation and Configuration
A-30
Release 1.0, Part Number 78-10616-01, June 2000
A P P E N D I X
B
Cable Specifications
This appendix contains details on the MGX 8230 cabling. It includes the following sections:
Note
•
T3 Trunk Cabling
•
Frame Relay Cabling
•
DC Power Cabling
•
AC Power Cabling
•
Control and Clock Cabling
•
External Alarm Cabling
In all cable references, the transmit direction is away from the MGX 8230, and the receive
direction is toward the MGX 8230.
T3 Trunk Cabling
A trunk cable connects each T3 port on the BNC-2T3 back card to a T3 port on other equipment. See
Table B-1 and Table B-2 for details.
Table B-1
Trunk Cables
Cable Parameter
Description
Type
75-ohm coax cable (RG-59 B/U for short runs, AT&T 734A for longer runs).
Two per T3 line (XMT and RCV).
Max. Length
450 feet maximum between the MGX 8230 and other equipment.
Connector
Terminated in male BNC; Rx is received from trunk, Tx is transmitted to
trunk.
Table B-2
T3 Connector Pin Assignments
Connector
Description
Rx BNC
Receive T3 from trunk
Tx BNC
Transmit T3 to trunk
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
B-1
Appendix B
Cable Specifications
Frame Relay Cabling
Frame Relay Cabling
T1 Cabling
Trunk cables connect the customer DSX-1 cross-connect point or T1 Channel Service Unit (CSU) to
the MGX 8230 at the T1 back card. See to Figure B-1 and Table B-3 for details.
Cable Parameter
Description
Cable Type
Western Electric 22 AWG, ABAM individually shielded twisted pair
(100 ohm balanced). Two pair per T1 line (1 transmit and 1 receive).
Cable Connector
RJ-48C male. (Figure B-1 illustrates the RJ-48 connector pin out.)
Max. Cable Length
655 ft. (199.664 m) maximum between the MGX 8230 node and the
first repeater or CSU. Selection of cable length equalizers.
Table B-3
Note
RJ-48C T1/E1 Connector Pin Assignments
Pin No.
Description
1
Transmit Tip
2
Transmit Ring
3
Transmit Shield
4
Receive Tip
5
Receive Ring
6
Receive Shield
Transmit direction is toward the T1 trunk.
Cisco MGX 8230 Installation and Configuration
B-2
Release 1.0, Part Number 78-10616-01, June 2000
Appendix B
Cable Specifications
Frame Relay Cabling
Figure B-1
RJ-48 Connectors
RJ-48 Pins
IN
IN
TTIP
TRNG
2
1
5
4
RTIP
RRNG
OUT
OUT
3
shield
shield
26270
6
E1 Cabling
SMB Connector
E1 trunk cables connect the customer DSX-1 cross-connect point or E1 Channel Service Unit (CSU) to
the node at the FRSM E1 back card (SMB-8E1). See Table B-4 and Table B-5.
Table B-4
E1 Trunk/Circuit Line Cabling Specification
Cable Parameter
Description
Cable Type
(BNC-8E1)
75-ohm coax cable for unbalanced connection. Two cables/pairs (1 transmit,
1 receive) per E1 line.
Cable Connector
16 female SMB for unbalanced connection. See Tables A-2 and A-4 for
pinouts.
Max. Cable Length
Approximately 100 meters maximum between the MGX 8230 node and the
first repeater or CSU. Equalizer for cable length.
Table B-5
E1 Connector Pin Assignments (unbalanced)
Connector
Description
Rx BNC
Receive E1 from trunk
Tx BNC
Transmit E1 to trunk
HSSI Port Connectors
The High Speed Serial Interface (HSSI) port connects through a female SCSI-II connector This
connector accords with ANSI/TIA/EIA-613. See Table B-6 for the pinouts.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
B-3
Appendix B
Cable Specifications
DC Power Cabling
Table B-6
Pinouts for SCSI-II Connector
Pin No.
Name
Signal Function
Polarity
Signal Source
11
SD
Send Data
+
DTE
36
-
4
RD
Receive Data
29
+
DCE
-
6
ST
Send Timing
31
+
-
2
RT
Receive Timing
27
+
_
6
TT
Terminal Timing
13
+
DCE
-
3
CA
DCE Available
28
+
DCE
-
8
TA
DTE Available
33
+
DTE
-
10
LA
Loop Ckt A
35
+
DTE
-
12
LB
Loop Ckt B
37
+
DTE
-
5
LC
Loop Ckt C
30
+
DCE
SG
Signal Ground
DC Power Cabling
DC Power connections are made to the DC Power Entry Modules at the rear of the MGX 8230. See
Table B-7 and Table B-8 for acceptable cable and wire types. Cisco normally does not provide wiring
for DC-powered systems. See Table B-7 for details on DC wiring.
Table B-7
DC Power Wiring
Cable Parameter
Description
Wiring
Three conductor, 10 AWG recommended wire gauge, min. 60°C insulation
rating, copper conductors only. Solid or stranded wires. Wire insulation
stripped back 0.25” (6 mm) at the MGX 8230 connector end.
Connection
EURO Block.
Cisco MGX 8230 Installation and Configuration
B-4
Release 1.0, Part Number 78-10616-01, June 2000
Appendix B
Cable Specifications
AC Power Cabling
AC Power Cabling
Either Cisco Systems or the customer can provide the AC power cord. See Table B-8 for the power cords
that Cisco can supply. In addition, you can special-order AC cables with other plugs or different lengths.
If you want to construct the power cord, it must mate with an IEC320 (C-14) 10/15A male receptacle
on the back of the AC power module.
Table B-8
AC Power Cables
Cable Parameter
Description
Cable
Provided with 8 feet (2.3 m) of 3-conductor wire with plug.
Plug (customer end) 20 A NEMA L620, 3-prong plug (domestic U.S.)
Need 15A NEMA 5-15 for US and Canada.
13 A 250 Vac BS1363, 3-prong fused plug (UK, Ireland)
CEE 7/7 (Continental Europe)
AS3112 (Australia/New Zealand)
CEI23-16/VII (Italy)
125V/15A North America
Control and Clock Cabling
This section describes the cables that can connect to the PXM-UI card.
Maintenance and Control Ports
The Maintenance (or Modem) port and the Control (or Console) port connect an MGX 8230 to an ASCII
terminal, workstation, or modem for remote alarm reporting or system monitoring. Refer to Table B-9
for a description of the cabling and Table B-10 for the pinout of the associated RJ45 connector.
Table B-9
Maintenance and Control Port Cabling
Cable Parameter
Description
Interface
EIA/TIA-232—both are DTE ports.
Suggested Cable
24 AWG, 8-wire. A straight-through EIA/TIA-232 cable provides a terminal
or printer connection. For an interface with modems on either port, a null
modem cable may be necessary.
Cable Connector
RJ45, subminiature, male. Table B-10 contains a list of the port pin
assignments.
Max. Cable Length
50 feet (15 m)
Table B-10 RJ-45 Maintenance and Control Port Pin Assignments
Pin No.
Name
Description
1
RTS out
Request to Send
2
DTR out
Data Terminal Ready
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
B-5
Appendix B
Cable Specifications
Control and Clock Cabling
Table B-10 RJ-45 Maintenance and Control Port Pin Assignments (continued)
Pin No.
Name
Description
1
RTS out
Request to Send
3
TxD
Transmit Data
4
GND
Signal Ground
5
GND
Signal Ground
6
RxD
Receive Data
7
DSR
Data Set Ready
8
CTS
Clear to Send
External Clock Input Cabling
The MGX 8230 has two external clock input connectors: a T1 RJ-45 connector and E1 SMB connector.
T1 Clock Cabling
The clock port can accept a T1 or E1 BITS clock input. (See Table B-11)
Table B-11 7T1 Clock Cabling
Pin No.
Name
1
Tx ring out
2
Tx tip out
3
Ground
4
Rx ring in
5
Rx tip in
6
No comment
7
Test point ring out
8
Test point tip out
Cisco MGX 8230 Installation and Configuration
B-6
Release 1.0, Part Number 78-10616-01, June 2000
Appendix B
Cable Specifications
External Alarm Cabling
External Alarm Cabling
The external alarm cable connects to the Alarm connector on the PXM-UI card. See Table B-12 for
physical characteristics of the cable and Table B-13 for the pinouts.
Table B-12 External Alarm Cabling
Cable Parameter
Description
Interface
Dry-contact relay closure.
Wire
24 AWG, shielded, 6-pair.
Connector
DB-15, Subminiature, male.
Table B-13 Network Alarm Pin Assignments
Pin No.
Alarm
Description
1
Audible—Major
Normally open
2
Common
9
Normally closed
4
Visual—Major
Normally open
5
Common
12
Normally closed
7
unused
n.c.
8
unused
n.c.
3
Audible—Minor
Normally open
11
Common
10
Normally closed
6
Visual—Minor
Normally open
14
Common
13
Normally closed
15
unused
n.c.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
B-7
Appendix B
Cable Specifications
External Alarm Cabling
Cisco MGX 8230 Installation and Configuration
B-8
Release 1.0, Part Number 78-10616-01, June 2000
G L O S S A R Y
A
ABR
Available Bit Rate is a Class of Service defined for ATM connections by the ATM Forum.
Devices using ABR are guaranteed no more than a certain rate of throughput. This rate
dynamically changes and the current value is relayed to the sending device by way of Resource
Management (RM) cells.
B
BCC
The switch control card in the BPX is the Broadband Control Card, which has a 68040
processor.
BPX switch
The Broadband Packet Exchange (BPX) is Cisco’s high-end ATM switch developed for the
service provider market. The BPX 8600 series switch is a carrier-quality switch, with trunk and
CPU hot-standby redundancy.
BXM
The Broadband Switch Module (BXM) cards are ATM port cards for the BPX switch that use
the Monarch chip set.
C
Cell bus
The cell bus in the MGX 8230 is the way that the service modules exchange data with the
switching fabric on the PXM.
CiscoView
GUI-based device-management software application that provides dynamic status, statistics,
and comprehensive configuration information for Cisco internetworking products, such as the
MGX 8230, or IGX switch or BPX switch.
Cisco WAN Manager
The Cisco WAN Manager (CWM) is the network management application for the Cisco wide
area switches, such as the BPX switch or the IGX switch. CWM was previously known as
StrataView Plus.
Class of Service (CoS)
Buffer
A buffer or queue which serves connections with similar QoS requirements.
A component of a Service Class Template that contains Class of Service Buffer configurations
Class of Service (CoS)
Buffer Descriptor Template indexed by CosB number. Note: A Qbin is a platform-specific (BXM in this case) instance of
the more general Class of Service Buffer (or CosB).
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1
Glossary
C
ComBus
The ComBus is the BPX’s internal messaging bus.
Community
In the context of SNMP, a relationship between an agent and a set of SNMP managers that
defines security characteristics. The community concept is a local one, defined at the agent.
The agent establishes one community for each desired combination of authentication, access
control, and proxy characteristics. Each community is given a unique (within this agent)
community name, and the management stations within that community are provided with and
must employ the community name in all get and set operations. The agent may establish a
number of communities, with overlapping management station membership.
E
Enterprise MIB
A MIB module defined in the enterprise-specific portion of the Internet management space
F
A feeder is a small switch which acts as an extension shelf, typically with lower-bandwidth
interfaces, for a larger switch. The larger switch is referred to as the Routing Node for the
Feeder(s). The MGX 8230 acts as a feeder to the IGX 8400 series switch.
Feeder
I
The Cisco IGX 8400 series wide area switch designed to provide backbone for enterprise data,
voice, fax, and video applications. The Cisco IGX switch was formerly referred to as the Cisco
StrataCom IGX switch.
IGX switch
M
Managed device
A device containing a network management agent implementation.
MGX 8230
An 7-slot chassis build with MGX 8850 style architecture that currently is used as a feeder shelf
for the IGX. Used as a an IGX feeder, the MGX 8230 supports MGX 8850/MGX 8250 service
modules.
MIB
Management Information Base, a structured set of data variables, called objects, in which each
variable represents some resource to be managed.
MIB-II
Internet-standard MIB, RFC 1213
Cisco MGX 8230 Installation and Configuration
2
Release 1.0, Part Number 78-10616-01, June 2000
Glossary
P
PXM
Processor Switch Module. The processor card used in MGX 8850 series switches. The PXM is
the processor used in the MGX 8230 product. Although functionally equivalent to a PXM, the
PXM is not interchangeable with a PXM and will not fit in an MGX 8850 card slot.
Q
Qbin
A Qbin is a platform-specific (BXM in this case) instance of the more general Class of Service
Buffer (or CosB).
R
Routing Node
In tiered networks terminology, a Routing Node is a larger switch to which one or more feeders
or controllers are attached. The IGX switch serves as the routing node for an MGX 8230 feeder.
S
SNMP
Simple Network Management Protocol.
U
UBR
Unspecified Bit Rate is a Class of Service for ATM networks defined by the ATM Forum.
Traffic in the UBR class is not guaranteed any particular throughput or delay performance. In
this regard, UBR is similar to “traditional” IP service.
Uplink back card
The back card that mates with an PXM and provides ATM trunking. The MGX 8230 supports
only an OC-3 uplink back card.
User interface back card
The back card (PXM-UI) that mates with the PXM and provides interfaces for control or
maintenance terminals, LAN connections, T1 or E1 clock inputs, and alarm outputs.
V
Virtual Switch Interface
See VSI.
VSI
Virtual Switch Interface is a master/slave protocol that allows Cisco WAN switches, such as
the BPX 8600 series switch or the MGX 8850/8250 node, to be controlled by more than one
network application. MPLS, or AutoRoute are examples of network applications.
VSI Controller
A controller, such as a Tag Switch Controller, which controls a switch using the VSI.
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3
Glossary
V
VSI Master
A VSI Master process implementing the master side of the VSI protocol in a VSI Controller.
Sometimes the whole VSI Controller might be referred to as a “VSI Master,” but this is not
strictly correct.
VSI Platform
A VSI Platform is a switch with one or more VSI Slaves allowing connections to be set up using
the VSI.
VSI Slave
A VSI Slave process implementing the slave side of the VSI protocol within a VSI Platform.
Sometimes a whole VSI Platform might be referred to as a “VSI Slave,” but this is not strictly
correct.
Cisco MGX 8230 Installation and Configuration
4
Release 1.0, Part Number 78-10616-01, June 2000
I N D E X
faceplate
A
1-22
BNC-2T3 back card
AAL5
1-27, 3-35
faceplate
1-21
AC Power Supply Module
2-27, 2-28
bootChange command
AC Power Supply module
1-6
BPX Reference Manual
AC power supply tray
addaimgrp
BRAM
3-19
addport command
1-15
bulk distribution
1-35
3-19
3-27
Alarm outputs
C
1-16
alarm outputs, PXM-UI
ATM cells
3-11
cable management
1-4
3-28
ATM UNI card
AUSM
1-22,
AC power
clock
ATM IP address
2-30
cabling
ATM Inverse Multiplexing, see IMA and AUSM/B
3-15
B-5
DC power
1-32
E1
B-5
B-5
control
1-23
AUSM/B
B-4
B-3
external alarm
as a clock source
1-23, 3-28
feature list, 8-port version
IMA
xvii
See Related documentation
3-30
addln command
addred
1-6, 2-27
3-12
T1
1-22, 3-28
1-22, 3-28
B-7
B-2
Cell bus
1-10
Cell bus controllers
AUSM/B-8T1E1
Cell Loss Priority
list of back cards
1-25
1-9
3-39, 3-40
center mounting in a rack
AX-FRSM-8E1
3-36, 3-38, 3-42, 3-43, 3-45
AX-FRSM-8T1
3-36, 3-38, 3-42, 3-43, 3-45
2-23
CESM
adding and modifying connections
configuring the card, lines, and ports
B
backplane
BERT
1-9
3-47
MGX-CESM-8T1
3-47
structured data transfer
4-11
bit error rate test, see BERT
MGX-CESM-8E1
unstructured data transfer
4-11
BNC-2E3 back card
3-49
3-48
3-47
3-48
CIR
FRSM cards
3-44
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
1
Index
Circuit Emulation Service Module
1-31, 1-32, 3-47
Circuit Emulation Service Module—8-Port
Circuit emulation services
Cisco documentation
xviii
DC PEM
CiscoView application
3-20
1-35, 3-4
3-19
bootChange
3-12
cnfchanmap
3-39
cnfifip
3-15
2-23
dspcds commands
3-15
dspifip commands
3-15
E1 clock input
3-15
cnfportrscprtn
cnfstatsmgr
1-7
1-3
E
3-20
cnfname
Also see DC PEM
Double-height modules
3-19
cnfifastrk
1-7, 2-23
DC power to the shelf
CLI commands
addport
1-5
DC power entry modules
configuring the MGX 8230 feeder
addln
Converting MGX 8230 slots
D
xviii
xvii
Cisco WAN Manager
1-35, 3-4
1-4
Cisco Documentation CD-ROM
Cisco publications
1-32
control port
1-16
external clock connections
3-20
3-11
external clock connections, through PXM-UI
3-16
cnfswfunc
3-16
cnftime
3-15
cnftmzn
3-16
cnftmzngmt
F
facility codes, definitions
3-16
fan tray
3-10
1-8
cnfupcabr
3-32
FEAC channel
cnfupccbr
3-31
feeder
cnfupcvbr
3-32
feeder, specifying the node as
dspcds
3-15
dspifip
3-15
reboot
3-13
scnfifastrk
1-16
A-9
Glossary-2
3-16
firmware dowload
runtime firmware
3-12
firmware download
3-20
firmware release numbers
Command Reference Manual
xvii
outline of steps
See Related documentation
3-44
3-40
congestion indication, FRSM
3-11
firmware downloading
committed information rate, see CIR
Congestion Indication
3-13
CESM and FRSM examples
service module versions
3-39
firmware version
3-17
3-17
connecting power for AC Systems
2-27
Frame Forwarding
connecting power for DC systems
2-23
Frame Relay connections
Control port
3-18
1-4
3-41
Frame Relay-to-ATM service interworking
communication parameters
1-4
1-16
Cisco MGX 8230 Installation and Configuration
2
Release 1.0, Part Number 78-10616-01, June 2000
Index
Frame Service Module
1-29
MGX-FRSM-2E3T3
L
3-5
Frame Service Module, see FRSM
LAN port
1-30
Frame Service Modules—Very High Speed
Light pipes
1-1
line activation
FRSM
ATM layer status management
cell loss priority, NIW
congestion indication
list of models
PXM uplink
3-39
3-19
logical port creation
3-39
PXM
3-39
3-19
logical ports
1-30
PVC status management
redundancy support
SIW
3-36
1-16
configuring through CLI
3-39
creating on the PXM
1-31
3-18
3-18
3-39
FRSM-VHS, basic descriptions
1-30
M
Maintenance port
G
communications parameters
gateway IP address
1-16
Management
3-12
MGX 8230
1-35
management of MGX 8800 switches
H
message structure
heat dissipation
MGX 8230
2-13
High Speed Frame Service Module
3-36
3-9
1-1, 3-1
alarm and error handling
and MGX 8850
architecture
I
backplane
IGX feeder
IMA
CLI
3-6
PXM logical port
inband ATM PVC
3-7
1-3, 1-9, 3-3
3-7
1-4
fan tray assembly
inband ATM connections
features
3-19
1-8
3-2
feeder to the IGX
3-20
3-7
Installing back cards
2-18
Hard drive
Installing front cards
2-18
IGX feeder application
gateway for PXM
1-15
management
IP address
Modules
3-12
for PXM with no run-time firmware
3-12
3-6
1-35, 3-4
3-4
power system
IP addresses
1-38, 3-4
1-9
dimensions
1-22, 3-28
3-4
1-6
processor slots
1-5
redundancy features
statistics counters
uplink back card
1-34
1-38, 3-4
3-6
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
3
Index
weight
number of cards required
2-22
wiring block
Mounting kit
2-25
MGX 8230 chassis
1-35
1-5
MGX 8230 fan tray assembly
MGX 8230 IGX feeder
1-8
for 19-inch rack
2-20
for 23-inch rack
2-20
mounting with IGX or BPX switch
1-3
2-13
MGX 8230 Installation and Configuration
manual organization
xvi
N
MGX 8230-MNT19
See mounting kit
2-20
network interworking
MGX 8230-MNT23
network managment
See mounting kit
2-20
over inband ATM PVCs
MGX 8230 Processor Switch Module
MGX 8230-PXM
back cards
3-38
1-12
3-20
network synchronization
1-12
from AUSM/B line
1-23, 3-28
1-12
LEDs and indicators
1-14
removing from system
MGX 8230-PXM1
O
2-17
3-2
on-line firmware, see run-time firmware
MGX-CESM-8E1
3-47
P
MGX-CESM-8T1
3-47
PAR
3-12
MGX 8800
management
3-4
MGX-FRSM-2CT3
resource partitioning on PXM
1-to1 Y-cable redundancy
1-31
physical line
MGX-FRSM-2T3E3
activating through the CLI on PXM
1-to1 Y-cable redundancy
1-31
Portable AutoRoute, see PAR
MGX-FRSM-HS2
1-to-1 Y-cable redundancy
MGX-MMF-4-155
1-31
1-12, 1-16
3-5
power requirements
2-13
1-6
1-12
port 34
3-5
MGX-SRM-3T3
specifying IP addresses
PXM1
1-35
3-18
3-19
port-level resource partitioning
SONET OC12/STM4 ATM interface
3-18
3-14, 3-24
creating logical ports through the CLI
1-12, 1-16
MGX-SMFLR-1-622
bulk distribution
1-7
PXM
Broadband Network Module
BERT
power entry module
Power system in MGX 8230
MGX-SMFIR-1-622
MGX-SMFIR-4-155
3-14, 3-24
3-20
3-12
1-3
PXM cell bus
1-35
Also see PXM
1-10
MGX-SRM-3T3/B
faceplate
1-37
list of capabilities
1-35
Cisco MGX 8230 Installation and Configuration
4
Release 1.0, Part Number 78-10616-01, June 2000
Index
PXM-UI
service interworking, SIW
1-12
alarm outputs
faceplate
Service modules
3-11
3-39
1-1
Service Resource Module-3T3, see SRM-3T3
1-16
1-35
shutdisk command
for PXM
R
2-17
Single-height modules
rack mounting the modules
reboot command
SIW
2-22
FRSM
3-13
receive direction, relative to MGX 8230
B-1
3-39
SLIP protocol
1-35, 3-4
Slot numbering in MGX 8230
redundancy
1-to-1 for AUSM E1 mode
FRSM E1 mode
faceplate
3-38
R-RJ48-8E1
3-47
R-RJ48-8T1
3-47
1-18
SMFLR-1-622 uplink card
faceplate
1-17
SNMP Management Information Base
Related documentation for IGX 8450
OC12/STM4 ATM interface
2-17
2-18
space requirements
Removing front cards
2-17
SRM-3T3
port-level, PXM
standards based conversion
3-20
3-47
statistics counters
RJ48-8T1
3-47
StrataView Plus
structured data transfer
1-12, 3-6
3-47
R-RJ48-8T1
3-47
run-time firmware, see firmware download
3-12
1-35, 3-4
2-17
T
T1
B-2
T1 clock input
S
1-4, 3-3
3-47
syncdisk command for PXM
1-12, 3-6
1-16
telecommunications requirements
Translation
safety
1-35
1-38, 3-4
See Cisco WAN Manager
Route Processor Module
R-RJ48-8E1
1-35
requirement for BNC-3T3 back card
3-14
RJ48-8E1
RPM
1-35
de-multiplexing to T1 channels
3-24
Also see RPM
3-5
2-13
bulk distribution
resource partitioning
definition for PXM
1-35, 3-4
SONET
xvii
Removing back cards
definition
1-1
SMFIR-1-622 uplink card
1-23
redundancy back cards
Removing
1-3
2-15
3-41
power and ground
2-14
Translation and Transparent Modes
SAFETY GROUND
2-25
transmit direction, relative to MGX 8230
seismic mounting
3-41
B-1
2-14
Cisco MGX 8230 Installation and Configuration
Release 1.0, Part Number 78-10616-01, June 2000
5
Index
U
unstructured data transfer
Uplink back cards
3-48
1-12
User interface back card
User Interface card
1-12
1-16
V
VPI range, PXM interface
3-22
W
warning
class 1 laser product
definition
2-11
2-3
grounding equipment
installation
2-10
2-10
jewelry removal
lightning activity
2-6
2-5
power disconnection
power supply
2-9
2-7
power supply, disconnection
product disposal
weight
2-8
2-4
2-13
World Wide Web
Cisco
xviii
Cisco MGX 8230 Installation and Configuration
6
Release 1.0, Part Number 78-10616-01, June 2000