FLEXmaster User Manual 4 02

FLEXmaster
USER MANUAL
Part Number: 770-0149-AB

Product Release: 4.02
April 2005
Copyright© 2005 Carrier Access Corporation. All rights reserved.
The information presented in this manual is subject to change without notice and does not represent a commitment on the
part of Carrier Access Corporation. The hardware and software described herein are furnished under a license or non-
disclosure agreement. The hardware, software, and manual may be used or copied only in accordance with the terms of this
agreement. It is against the law to reproduce, transmit, transcribe, store in a retrieval system, or translate into any medium
- electronic, mechanical, magnetic, optical, chemical, manual, or otherwise - any part of this manual or software supplied
with MASTERseries for any purpose other than the purchaser’s personal use without the express written permission of
Carrier Access Corporation.
The Carrier Access Logo is a registered trademark of Carrier Access Corporation. FLEXengine, FLEXmaster,
MASTERseries and MASTERview are trademarks of Carrier Access Corporation. All other brand or product names are
trademarks or registration trademarks of their respective companies or organizations.
Contact Information:
Carrier Access Corporation
5395 Pearl Parkway
Boulder, CO 80301-2490
Corporate Phone: (303) 442-5455
Fax: (303) 443-5908
www.carrieraccess.com
Customer Support Direct: (800) 786-9929
E-mail: tech-support@carrieraccess.com
Supporting Software Version:

MASTERseries 4.02
PREFACE
Preface
Compliance
Safety of Information Technology Equipment
MASTERseries is safety certified by an independent laboratory and is compliant with the following
safety standards:
UL60950, 3rd Edition / CSA C22.2 No. 60950
EN60950
FCC Requirements, Part 15

This device complies with Part 15 of the FCC Rules. Operation is subject to the following two
conditions:
This device may not cause harmful interference, and
This device must accept any interference received, including interference that may cause
undesired operation
This equipment has been tested and found to comply with the limits for a Class A digital device pursuant
to Part 15 of the Federal Communications Rules. These limits are designed to provide reasonable
protection against harmful interference when 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
the user will be required to correct the interference at the user’s own expense.
NOTE: Changes or modifications to any unit not expressly approved by the party responsible for
compliance may cause damage to the equipment and could void your authority to operate the
equipment.
Preface
Compliance
FCC Requirements, Part 68

The following instructions are provided to ensure compliance with the Federal Communications
Commission (FCC) Rules, Part 68.
1. This equipment complies with Part 68 of the FCC rules and the requirements adopted by the
ACTA. On the rear of this equipment is a label that contains, among other information, a
product identifier in the format US:AAAEQ##TXXXX. If requested, this number must be
provided to the telephone company.
2. This equipment uses the following standard jack types for network connection:
Port ID REN/SOC FIC USOC
(8) T1 Ports 6.0N 04DU9-BN RJ-48C
(A1–D8) 04DU9-DN
04DU9-1KN
04DU9-1SN
04DU9-1ZN
3. This equipment is designed to be connected to the telephone network or premises wiring using
cabling that complies with the requirements of FCC Part 68 rules.
4. In the unlikely event that this equipment causes harm to the telephone network, the telephone
company will notify you in advance that temporary discontinuance of service may be required.
But if advance notice isn't practical, the telephone company will notify the customer as soon as
possible. Also, you will be advised of your right to file a complaint with the FCC if you believe
it is necessary.
5. The telephone company may make changes in its facilities, equipment, operations or
procedures that could affect the operation of the equipment. If this happens the telephone
company will provide advance notice in order for you to make necessary modifications to
maintain uninterrupted service.
6. This equipment must not be used on party lines. Connection to party line service is subject to
state tariffs. Contact the state public utility commission, public service commission or
corporation commission for information.
7. Repair service and warranty information can be obtained from:
Carrier Access Corporation
5395 Pearl Parkway
Boulder, CO 80301-2490
(800) 786-9929 or (303) 442-5455
If the equipment is causing harm to the telephone network, the telephone company may
request that you disconnect the equipment until the problem is resolved.
8. All repairs should be performed by Carrier Access or an authorized agent. It is the responsibility
of the users requiring service to report the need for service to Carrier Access or an authorized
agent.
iv FLEXmaster - Release 4.02

Preface
Compliance
9. Data Equipment:
For permissive, programmable and (or) fixed loss loop operation data equipment, in
addition to the general requirements for all equipment, information must be provided
explaining which jack is associated with each operation.
Permissive, use RJ-11C
Programmable, use RJ-41S and RJ-45S
Fixed Loss Loop, use RJ-41S
Refer to ATIS Technical Report No. 5 for details on these connectors.
For Private (Leased) Line (Analog Data Format) equipment, the type JM8 jack is required.
Refer to ATIS Technical Report No. 5 for details on this connector. For Private (Leased)
Line (Digital Format) equipment, in addition to the general requirements for all equipment,
certain digital connections require that an encoded analog content and billing protection
affidavit be provided the telephone company. Customer instructions must contain
information on the preparation and submission of the affidavit.
FLEXmaster - Release 4.02 v

Preface
Compliance
Industry Canada ICES-003

English
This class A digital apparatus complies with Canadian ICES-003.
French
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
Industry Canada CS-03

This equipment meets the applicable Industry Canada Terminal Equipment Technical Specifications.
This is confirmed by the registration number. The abbreviation, IC, before the registration number
signifies that registration was performed based on a Declaration of Conformity indicating that Industry
Canada technical specifications were met. It does not imply that Industry Canada approved the
equipment.
Before installing this equipment, users should ensure that it is permissible to be connected to the
facilities of the local telephone company. The equipment must also be installed using an acceptable
method of connection. The customer should be aware that compliance with the above conditions may
not prevent degradation of service in some situations.
Repairs to certified equipment should be coordinated by a representative designated by the supplier.
Any repairs or alternations made by the user to this equipment, or equipment malfunctions, may give
the telecommunications company cause to request the user to disconnect the equipment.
Users should ensure for their own protection that the electrical ground connections of the power utility,
telephone lines and internal metallic water pipe system, if present, are connected together. This
precaution may be particularly important in rural areas.
CAUTION! USERS SHOULD NOT ATTEMPT TO MAKE SUCH CONNECTIONS THEMSELVES, BUT
SHOULD CONTACT THE APPROPRIATE ELECTRIC INSPECTION AUTHORITY, OR ELECTRICIAN, AS
APPROPRIATE.
vi FLEXmaster - Release 4.02

Preface
Safety Information
Safety Information
CAUTION! ALWAYS USE CAUTION WHEN INSTALLING TELEPHONE LINES. READ THE
CAUTIONS BELOW FOR DETAILS ON SAFETY GUIDELINES TO PREVENT INJURY.
Never touch uninsulated telephone wires and terminals unless the telephone line has
been disconnected at the Network Interface (NI) as voltage potentials as high as 300 VAC
may be present across the transmit and receive pairs.
Only use No. 26 AWG or larger telecommunication line cord, to reduce the risk of fire.
Never install telephone wiring during a lightning storm.
Never install telephone jacks in wet locations unless the jack is specifically designed for
wet locations.
Refer to the installation section of this manual for a safe and proper installation procedure.
All wiring external to this equipment should follow the current provision of the National
Electrical Code.
Notices
This manual contains important information and warnings that must be followed to ensure safe
operation of the equipment.
DANGER! A DANGER NOTICE INDICATES THE PRESENCE OF A HAZARD THAT CAN OR

WILL CAUSE DEATH OR SEVERE PERSONAL INJURY IF THE HAZARD IS NOT AVOIDED.
CAUTION! A CAUTION NOTICE INDICATES THE POSSIBILITY OF INTERRUPTING NETWORK

SERVICE IF THE HAZARD IS NOT AVOIDED.
WARNING! A WARNING NOTICE INDICATES THE POSSIBILITY OF EQUIPMENT DAMAGE IF

THE HAZARD IS NOT AVOIDED.
NOTE: A Note indicates information to help you understand how to perform a procedure or
how the system works. Notes should be read before performing the required action.
FLEXmaster - Release 4.02 vii

Preface
Electrostatic Discharge (ESD) Precautions
Electrostatic Discharge (ESD) Precautions

ESD can damage processors, circuit cards, and other electronic components. Always observe the
following precautions before installing a system component.
1. Do not remove a component from its protective packaging until ready to install.
2. Wear a wrist grounding strap and attach it to a metal part of the system unit before handling
components. If a wrist strap is not available, maintain contact with the system unit throughout
any procedure requiring ESD protection.
WARNING! INTEGRATED CIRCUITS (ICS) ARE EXTREMELY SUSCEPTIBLE TO ELECTROSTATIC

DISCHARGE. UNLESS YOU ARE A QUALIFIED SERVICE TECHNICIAN WHO USES TOOLS AND
TECHNIQUES THAT CONFORM TO ACCEPTED INDUSTRY PRACTICES, DO NOT HANDLE ICS.
The ESD warning label appears on packages and storage bags that contain
static-sensitive products and components.
viii FLEXmaster - Release 4.02

Preface
Warranty
Warranty
Carrier Access warrants to BUYER that Product Hardware will be free from substantial defect in material and
workmanship under normal use in accordance with its Documentation and given proper installation and maintenance
for period of two years from the date of shipment by Carrier Access.
Carrier Access warrants that the Licensed Software, when used as permitted under its License Terms and in
accordance with the instructions and configurations described in the Documentation (including use on Carrier
Access product or a computer hardware and operating system platform supported by Carrier Access), will operate
substantially as described in the Documentation for a period of ninety (90) days after date of shipment of the
Licensed Software to BUYER.
This warranty shall not apply to Products or Software that have been either resold or transferred from BUYER to any
other party. Any such transfer voids the above warranty and related licenses. Carrier Access offers expanded product
care beyond what is covered by the warranty through different support plans. The plans are designed to maximize
network availability through advance replacement for defective equipment. Please contact your Carrier Access
representative for support program details.
Warranty Procedure
BUYER must promptly notify Carrier Access of any defect in the Product or Software and comply with Carrier
Access' return/repair policy and procedures. Carrier Access or its agent will have the right to inspect the Product or
workmanship on BUYER's premises. With respect to a warranty defect in Product hardware reported to Carrier
Access by BUYER during the warranty period, Carrier Access, as its sole obligation and BUYER's exclusive remedy
for any breach of warranty, will use commercially reasonable efforts, at its option, to:
a. repair, replace, or service at its factory or on the BUYER's premises the Product, or component
therein, or workmanship found to be defective so that the Product hardware operates substantially
in accordance with Carrier Access Documentation; or
b. credit BUYER for the Product in accordance with Carrier Access's depreciation policy.
With respect to a warranty defect in the Licensed Software reported to Carrier Access by BUYER during the 90-day
software warranty period, Carrier Access, at its own expense and as its sole obligation and BUYER's exclusive
remedy for any breach of the software warranty, will use commercially reasonable efforts to, at its option,
a. correct any reproducible error in the Licensed Software, or
b. replace the defective Licensed Software, as follows: Should a Severity 1 or 2 warranty defect with
the Software occur during the 90-day warranty period, Carrier Access will provide, in its sole
determination, either
1. software to resolve the defect to be downloaded into the affected units by the BUYER or
2. a documented workaround to address the issue.
Severity 1 issues are failures of the Licensed Software to comply with the Carrier Access software
specifications and that completely or severely affect the Carrier Access Product and its traffic or service
capacity, or maintenance or monitoring capabilities.
Severity 2 issues are failures of the Licensed Software to comply with the Carrier Access software
specifications and that result in a major degradation of the Carrier Access Product so as to impact its system or
service performance, or significant impairments to network operator control or effectiveness. Should a Severity
3 warranty defect with the Licensed Software occur during the 90-day warranty period, Carrier Access will
provide assistance to Buyer to determine if a solution or workaround will be provided in a subsequent software
release following the reported issue.
Severity 3 issues are defined as failures of the Licensed Software to comply with the Carrier Access software
specifications but that do not significantly impair the function or service of the Carrier Access Product or the
system.
Determination of Severity 1, 2 or 3 shall be made solely by Carrier Access following receipt of the reported
problem. Refurbished material may be used to repair or replace the Product. BUYER shall bear the risk of loss
for Products or Software returned to Carrier Access for repair, replacement, or service, and the same must be
shipped pre-paid by BUYER.
FLEXmaster - Release 4.02 ix

Preface
Warranty
Requests for warranty services and troubleshooting must be made to, and will be provided by, the Carrier Access
Customer Support Center via telephone during the warranty period and during normal business hours. Normal business
hours for Carrier Access Customer Support Center are 7:00 a.m. to 6:00 p.m. Mountain Standard Time, Monday through
Friday, excluding weekends and standard Carrier Access recognized holidays.
Limitation of Warranty & Limitation of Remedies

Correction of defects by repair, replacement, or service will be at Carrier Access's option and constitute Carrier Access'
sole obligation and BUYER's sole and exclusive remedy under the limited warranty. Any such error correction or
replacement provided to BUYER does not extend the original warranty period for hardware or software, respectively.
Carrier Access assumes no warranty or other liability with respect to defects in the Product or Software caused by:
a. modification, repair, storage, installation, operation, or maintenance of the Product or Software by
anyone other than Carrier Access or its agent, or as authorized and in accordance with the Carrier
Access Documentation; or
b. the negligent, unlawful or other improper use or storage of the Product or Software, including its use
with incompatible equipment or software; or
c. fire, explosion, power failures, acts of God, or any other cause beyond Carrier Access' reasonable
control; or
d. handling or transportation after title of the Product passes to BUYER.
Other manufacturer's equipment or software purchased by Carrier Access and resold to BUYER will be limited to that
manufacturer's warranty. Carrier Access assumes no warranty liability for other manufacturer's equipment or software
furnished by BUYER.
BUYER UNDERSTANDS AND AGREES AS FOLLOWS: Except for the limited warranty set forth above, the Product,
License Software and all services performed by Carrier Access hereunder are provided "as is," without representations or
warranties of any kind. Carrier Access does not warrant that the Product, License Software, any hardware or software, or
any update, upgrade, fix or workaround furnished to BUYER will meet BUYER's requirements, that the operation thereof,
including any maintenance or major releases thereto will be uninterrupted or error-free.
THE WARRANTIES IN THIS AGREEMENT REPLACE ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED,
AND ALL OTHER OBLIGATIONS OR LIABILITIES OF CARRIER ACCESS, INCLUDING ANY WARRANTIES
OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRINGEMENT AND/OR ANY
IMPLIED WARRANTIES ARISING OUT OF COURSE OF PERFORMANCE OR COURSE OF DEALING. ALL
OTHER WARRANTIES ARE DISCLAIMED AND EXCLUDED BY CARRIER ACCESS.
THE REMEDIES CONTAINED IN THIS AGREEMENT WILL BE THE SOLE AND EXCLUSIVE REMEDIES
WHETHER IN CONTRACT, TORT, OR OTHERWISE, AND CARRIER ACCESS WILL NOT BE LIABLE FOR
INJURIES OR DAMAGES TO PERSONS OR PROPERTY RESULTING FROM ANY CAUSE WHATSOEVER,
WITH THE EXCEPTION OF INJURIES OR DAMAGES CAUSED BY THE GROSS NEGLIGENCE OF CARRIER
ACCESS. THIS LIMITATION APPLIES TO ALL SERVICES, SOFTWARE, AND PRODUCTS DURING AND
AFTER THE WARRANTY PERIOD. IN NO EVENT WILL CARRIER ACCESS BE LIABLE FOR ANY SPECIAL,
INCIDENTAL, OR CONSEQUENTIAL DAMAGES, LOSS OF DATA, OR COMMERCIAL LOSSES EVEN IF
CARRIER ACCESS HAS BEEN ADVISED THEREOF.
No agent, BUYER, or representative is authorized to make any warranties on behalf of Carrier Access or to assume for
Carrier Access any other liability in connection with any of Carrier Access's Products, software, or services.
The foregoing summarizes Carrier Access' entire product and software warranties, which are subject to change without
notice.
Warranty Product Returns

Before returning any equipment to Carrier Access Corporation, first contact the distributor or dealer from which you
purchased the product.
A Return Material Authorization (RMA) number is required for all equipment returned to Carrier Access Corporation.
Call Carrier Access Corporation Customer Support at (800) 786-9929 or (303) 442-5455 for RMA number, repair/
warranty information and shipping instructions. Be prepared to provide the following information:
Carrier Access Corporation serial number(s) from the system chassis or circuit card(s)
Name of distributor or dealer from which you purchased the product
Description of defect
x FLEXmaster - Release 4.02

Table of Contents
TABLE OF CONTENTS
Preface
Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii
Electrostatic Discharge (ESD) Precautions . . . . . . . . . . . . . . . . . . . . . . . . viii
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
1 Introduction
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
MASTERseries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
FLEXmaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
2 Physical Installation
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Application Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
FLEXmaster Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
FLEXmaster Adapter Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Two-Slot Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Installing a Two-Slot Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
Installing Application Modules in a Two-Slot Chassis . . . . . . . . . . 2-10
DC Powered Two-Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Two-Slot Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Contents of Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Hardware Upgrade Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Fan Replacement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Eight-Slot Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21
Adjusting the Brackets for a 23-Inch Rack. . . . . . . . . . . . . . . . . . . . 2-22
Installing an Eight-Slot Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
Adapter Strips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23
Installing the FLEXmaster Module in an Eight-Slot Chassis. . . . . . 2-25
Powering the Eight-Slot Chassis. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28
Configuring a Modem for Remote Access . . . . . . . . . . . . . . . . . . . . . . . 2-31
3 Configuration
Accessing the FLEXmaster Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Port Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Navigating the Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Table of Contents
Keyboard Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Interface Identifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Recommended Configuration Sequence . . . . . . . . . . . . . . . . . . . . . 3-11
Local Access to the FLEXmaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Accessing Two Standalone Units from a
Single Ethernet Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13
Setting the Date and Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Configuring the Configuration Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Creating a New Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Specifying the Link Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
T1 Link Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Configuring System Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Setting the System Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Configuring the DACS Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Navigating through the DACS screen . . . . . . . . . . . . . . . . . . . . . . . 3-20
Configuring the Management Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
ABCD/abcd Signaling Patterns. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
Configuring the Data Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Configuring Internal Timeslot Connections . . . . . . . . . . . . . . . . . . . . . . 3-25
Entering Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28
Using the Timeslot Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Full Duplex Cross Connects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30
Configuring APS for Link Failures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Password Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33
Error Checking, Saving, and Activating the Configuration . . . . . . . . . . 3-34
Using Save Versus Using CoMmit . . . . . . . . . . . . . . . . . . . . . . . . . 3-35
Configuring Links for Threshold Alarms . . . . . . . . . . . . . . . . . . . . . . . . 3-37
Configuring Minor Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Configuring the Idle Signaling Patterns . . . . . . . . . . . . . . . . . . . . . . . . . 3-39
Telnet Access to FLEXmaster. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40
Setting the System Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41
4 CLI Commands
Accessing the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Command Line Interface Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
? or help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
[TAB] usage for word or command completion . . . . . . . . . . . . . . . . 4-2
CLI Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
CLI navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
CLI Command Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
xii FLEXmaster - Release 4.02

Table of Contents
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
all modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
dhcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-32
dhcpc (DHCP Client) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
dhcprelay (DHCP Relay) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
Interface Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Interface: ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46
Interface: hdlc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Interface: ppp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56
ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-69
ppp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-81
relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
rip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
rtm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99
snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103
sntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109
5 CLI Configuration
Accessing the CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Basic Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
6 Diagnostics
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
The Diagnostics Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Performing Diagnostics on Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Linkdiag Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Link Loopback Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9
Performing Diagnostics on Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Resetting the Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
7 Maintenance
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Displaying the Version Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Alarms Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Alarm Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Link and Port Status. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Alarm Contact Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10
Link Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-11
History Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12
FLEXmaster - Release 4.02 xiii

Table of Contents
Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Performance Monitoring Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Displaying the Local Performance Statistics . . . . . . . . . . . . . . . . . . 7-19
Remote Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Individual Performance Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Using the Help Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Sending a Copy of the System and Alarm Events . . . . . . . . . . . . . . . . . 7-24
Uploading the Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Downloading Application and Configuration Files . . . . . . . . . . . . . . . . 7-27
Dowloading Application Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Downloading Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28
8 Troubleshooting
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Interpreting Alarm indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Red Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Yellow Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Trunk Conditioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
AIS Blue Alarm Propagation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Removing and Replacing Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Diagnosing a Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Preliminary Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Fault Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Loopback Test Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Fault Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Troubleshooting Flow Charts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
A Data Port Interfaces

Data Port Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Adapter Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Network Management Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
B SNMP Trap List

SNMP Trap List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Glossary
Index
xiv FLEXmaster - Release 4.02

CHAPTER
1
Introduction
This manual focuses on the FLEXmaster™ module. For more information on MASTERseries™ and
the other Modules, please refer to the MASTERseries User Manual, or the specific manual for the
Module.
In this Chapter
Overview
- MASTERseries
- FLEXmaster
Introduction
Overview
Overview
MASTERseries
The MASTERseries product line is an integrated access platform that provides cell site integrated
access, narrowband Local Area Network (LAN) hubbing, Public Switched Telephone Network (PSTN)
bypass interconnection, Signaling System no. 7 (SS7) network aggregation and grooming, and building
Point of Presence (POP) voice and data networking.
The MASTERseries line consists of several application modules and plug-on adapter modules, and uses
MASTERview for network management. The FLEXmaster8 modules can be housed in a dual-slot
enclosure that supports up to sixteen T1/E1 interfaces with two V.35 interfaces with redundant power
supplies and alarm contacts, or an eight-slot enclosure that supports up to 32 T1/E1 interfaces with four
V.35 interfaces also with redundant power supplies and alarm contacts.
Modules and Adapters
There are a wide variety of Modules and Adapters for MASTERseries. The following table gives a
brief description of them.
Application Modules
FLEXmaster See FLEXmaster on page 1-3.
PATHmaster A T1/E1 compact digital crossconnect switch with integrated DSU/CSU
functionality. Available in 2, 3 or 4 port configurations.
LINKmaster A multilink CSU that provides connections for up to 2 full or fractional T1/E1
circuits. Can be upgraded to PATHmaster level.
TRANSmaster Expands the capabilities of the PATHmaster by adding 2:1 ADPCM voice
compression.
BANDmaster T1 or E1 four link inverse multiplexer (IMUX) module with integral CSUs and
dual V.35 or RS530-A ports.
DATAmaster Quad port module with software configurable V.35, V.36, RS232, RS530-A,
RS449, or X.21 ports
CLOCKmaster E1 TRANSmaster with a 2 Mhz GPS clock input and available output for
cascading to adjacent shelves
PORTmaster A four port Ethernet 10/100 hub with a quad port asynchronous terminal server
that expands the capabilities of the PACKETcore IP bridge/router module.
HUBmaster A five port 10/100 MB Ethernet hub.
Plug-on Adapter Modules
PACKETport Portable plug-on IP edge router with DHCP support
TELEport Portable plug-on FXS telephone adapter module
Optional Plug-on Card
(all application modules except DATAmaster, HUBmaster and FLEXmaster)
PACKETcore Optional plug-in card for Ethernet and WAN interfaces that provides
management and user connectivity
1-2 FLEXmaster - Release 4.02

Introduction
Overview
There are three chassis available for the MASTERseries:

Single-slot chassis that can support up to four T1/E1 interfaces with two DSU interfaces
Two-slot chassis that supports up to eight T1/E1 interfaces with up to six DSU interfaces with
redundant power supplies and alarm contacts, or
Eight-slot chassis that supports up to 32 T1/E1 interfaces also with redundant power supplies
and alarm contacts.
FLEXmaster
Note: This release of the FLEXmaster is for a limited configuration. The limited configuration is
as follows:
Two- and Eight-slot chassis only (not supported in a single-slot chassis)
24/-48 VDC Power Supply only
Maximum two standalone FLEXmasters in a chassis. Each module runs independently and
does not communicate over the mid-plane. No other modules or FLEXmasters are supported.
No E1 Support
8-Port T1 Cell Site Access Module with IP Router for MASTERseries
The FLEXmaster module for the Carrier Access MASTERseries platform is an intelligent compact
device that provides wireless mobile transport networking solutions for: voice and data T1
integrated access; wireless cell site traffic grooming, concentration, backhaul and LAN extension.
The FLEXmaster functions as an 8-T1 micro-DCS and multi-link T1 DSU/CSU with router and
features the powerful Carrier Access FLEXengine™ processor for ATM-based transport migration.
The FLEXmaster eliminates the uncertainty of cell site backhaul network protocol migration to
ATM or IP by offering unparalleled backhaul networking flexibility for both UMTS and
CDMA2000 migration paths. ATM, IP and GSM Abis compression options will be remotely
upgradeable to the FLEXmaster module via simple software loads once available.
Key Features
8 DS1/DSX1 interfaces with integrated CSUs
V.35 data port with integral DSU
Dual 10/100 Ethernet ports
DS0 cross-connect
D4 - ESF conversion
Performance monitoring of all network ports
Drop-and-Insert multiplexing
SNMP or VT100 managed, Telnet supported
Environmentally hardened (-40° C to 65° C)
Two-slot or Eight-slot chassis configurations
Integrated IP router
High performance IP routing
Carrier-grade design, features and performance at a disruptive price
FLEXmaster - Release 4.02 1-3

Introduction
Overview
T1 Scalability and Processing to Grow with Future Demands

The FLEXmaster Module is designed to fit in the two-slot and eight-slot MASTERseries chassis.
The FLEXmaster can switch, groom or bypass any combination of 56/64 Kbps T1 timeslots. The
module supports 8 T1 circuits and provides one V.35 high-speed data port, with integral T1 DSU
support to drop-and-insert local data into available T1 NxDS0 timeslots. In addition, it supports 2
Ethernet 10/100Base-T ports and a router option. The router option provides extending Ethernet
LAN access to the remote cell site for remote management, internet and intranet access.
Cell Site Access Flexibility
The FLEXmaster module is a highly integrated solution that functions as a stand-alone unit. Later
software releases will allow the FLEXmaster to be fully integrated with additional MASTERseries
modules in two-slot and eight-slot chassis.
Consolidates traffic to eliminate excess T1 access charges and equipment costs
Integrates DSU, DCS, IP router and multiple CSUs for a variety of networking solutions
Provides any to any channel cross-connect and grooming
Eliminates the need for multiple equipment platform solutions by consolidating
functionality and cost
Maintains network reliability with robust performance monitoring and automatic
protection switching
Remotely upgradeable via software load to ATM for 3G migration flexibility (ATM
upgrade available in future release)
Simplified Configuration and Management
All features are soft programmable, eliminating the need to set or change any switch settings to
reconfigure the unit. Configurations can be stored in non-volatile memory and invoked manually or
upon user defined conditions. This provides the ability to automatically reroute and/or vary T1 or
unit parameters based on link failure or user defined error thresholds.
The FLEXmaster module has been designed for easy configuration and management with flexible
provisioning options. Any SNMP based element manager, VT100 terminal, or PC with terminal
emulator can access all management functions, including alarm screens, configuration commands,
and diagnostics. The intuitive user interface reduces training and provisioning time for technicians.
FLEXmaster Modules are shipped configured for quick turn-up and operation. There are no
complex hardware modules or software packages to select. New features can be activated remotely
through software download.
Configuration and maintenance is performed locally or remotely. The command line interface is
accessed locally through the serial port on the unit or remotely through Telnet. SNMP is used for
alarm and performance monitoring. Best of all, no site visits are required to increase the capabilities
or manage the system; thereby reducing cost and personnel required to support the system.

Introduction
Overview
FLEXmaster Technical Specifications

Special Requirements:
Two-slot VDC chassis requires two-slot VDC power supply (P/N 8662D), and fan
assembly (P/N 8663) - Required for installing FLEXmaster Module in the two-slot
chassis
MASTERseries Release 4.0 or higher
T1 Network Ports
8 T1 Ports
Line rate: 1.544 Mbps
Framing: SF/ESF compatible per TR54016, TR62411 for T1 CRC-4
Coding: AMI or B8ZS for T1, HDB3 for E1
FLEXmaster: Female 8-pin RJ-48C Jack
Timing: Internal or external from T1 port
LED indicators: YEL/TEST, OOF/LOS, SYNC, AIS
Line interface: T1-CSU or T1-DSX
Line build out (DSX-1): 655 ft
Receive sensitive (DS1): 0 to -22 dB @ 772KHz ALBO
Output level (DS1): selectable at 0 to -22dB
Jitter: meets AT&T Pub. TR-62411, G.832
Solid-state fuse-less, over voltage and over current T1 line protection
Data Port
Data rate: N x 56/64Kbps for N = 1-24
Interface: CCITT V.35 DCE Synchronous Data
Connector: Female DB-25 pin connector
Indicators: RxD, TxD

Introduction
Overview
Ethernet Ports
2 10/100 Ports, RJ-45 jacks, front access
LED indicators: links activity, link status
Management
Front access from RS-232 (RJ-45) or 10/100Base-T Ethernet ports (RJ-45)
VT100 RS-232 port, 4,800-19,200 bps; RJ-45 connector, external modem supported
SNMP DS1 MIB and MIB II via PPP, Private MIB
In-band Remote Access via DS0s, Telnet supported
3-level password control
Diagnostics
Loopback types: Bi-directional, fractional DS0, line, local, payload, dataport, remote
loopback, fixed or timed loopback option
Performance Monitoring
Data storage: Last 24 hours of data in 15-min. increments, 72-hour summary
Monitors: All network interfaces
Reports: Based on T1.403 for T1 alarm history and network interface statistics
Routing Features
PPP Nx64K WAN data rates
Static, RIPv1, RIPv2, Routing, Route Redistribution
Un-numbered interface support
DHCP - Client, Relay and Server
Ethernet Interface 1 and 2 support
Ping, Trace Route
DNS relay and DNS resolver
Power
+24 VDC/-48 VDC power supply
VDC input range (+/- 20 to 65 VDC)
Regulatory
USA
- UL60950-1
- FCC Part 15, Class A
- FCC Part 68 and TIA-968-A
Canada
- CSA 60950-1
- ICES-003 Class A
- CS-03

Introduction
Overview
Physical Information
Two-slot chassis
- 1.75 in (H) x 19 in (W) x 10.2 in (D)
- 4.4 cm (H) x 48.3 cm (W) x 25.9 cm (D)
Eight-slot chassis
- 5.25 in (H) x 19 in (W) x 10.2 in (D)
- 13.3 cm (H) x 48.3 cm (W) x 25.9 cm (D)
Environment
Ambient temperature: -40 to 149 °F (-40 to 65 °C) extended temperature range
Relative humidity (non-condensing) range: 0 to 95%
Maximum Operating Altitude: 10,000 ft (3,048 m)

Introduction
Overview

CHAPTER
2
Physical Installation
In this Chapter
Overview
Unpacking
Physical Description
LEDs
Two-Slot Chassis
Two-Slot Upgrade
Eight-Slot Chassis
Configuring a Modem for Remote Access
Overview
Overview
This chapter contains a description of the MASTERseries components and how to install them.
FLEXmaster modules can be installed in an eight- or a two-slot chassis. The modules operate the same
in each chassis, but details of the physical description and installation vary.
Unpacking
WARNING! OBSERVE PRECAUTIONS FOR HANDLING ELECTROSTATIC DEVICES.
1. Inspect containers for damage during shipment. Report any damage to the freight carrier for
possible insurance claims.
2. Compare packing list with office records. Report any discrepancies to the office.
3. Open shipping containers, being careful not to damage contents.
4. Inspect contents and report any damage.
5. If equipment must be returned for any reason, carefully repack equipment in the original
shipping container with original packing materials if possible.
6. If equipment is to be installed later, replace equipment in the original shipping container and
store in a safe place until ready to install.

This section describes the physical parts of the MASTERseries hardware: the application modules and
the plug-on adapter modules.
Application Modules
The application modules consist of the following components:
An engine
An engine faceplate adapter strip
An adapter module
An adapter module adapter strip
The engine is the largest component and has the LEDs. This component is installed into the front of the
chassis. The adapter module incorporates the port and link interfaces. This component is installed at the
rear of the chassis, directly behind the associated engine. See the following figure.

If it becomes necessary to swap an adapter module, replace it with one that has the same part number.
The part number label can be seen on the inside bottom corner of each module. See the following figure.
NOTE: All application modules are hot-swappable. After a module has been configured,
if it is moved to a different slot or shelf, the configuration will be defaulted to a new
configuration. If the module is moved back before doing a commit, (see Error Checking,
Saving, and Activating the Configuration on page 3-34) the original configuration will be
restored. If the module remains in the new location, a new configuration can be entered or
a saved configuration can be downloaded.

FLEXmaster Engine
-
8608 Ejector/Top Handle.

FLEXmaster8 Lift to eject module.
RxD TxD PST ALM

TxD and RxD PST and Alarm
Indicators Indicators
NMS
T1/E1
1 2
2 SLOT DOWN
3 4
Link Status
LEDs
5 6
7 8
ENET 2 Ethernet Port 2
Ethernet Port 1
ENET 1
Fixed Knob.
Pull straight out to
remove module
Up to 8 T1

LEDs
RxD and TxD
LED State Description
-
RxD TxD RxD solid Receiving data
off Idle or not used
TxD solid Transmitting data
off Idle or not used
Link Status
State Description
solid red OOF, AIS
-
T1/E1 Check the status screen for more information
1 2 solid green Link is up.
blinking red LOS.
3 4
blinking red and green Yellow sync alarm or RAI. Indicates red alarm on the
far end.
alternating green and Diagnostic function present. Also known as “yellow
orange alarm”.
off Link is disabled.
Ethernet Status
-
Ethernet status light solid yellow Indicates ethernet cable is
connected to a device.
(If connecting directly to a NIC
card, use a crossover cable.)
ENET 1
Ethernet activity light blinking green Ethernet activity.
Module Status
-
PST ALM PST blinking Passed power system test
ALM Alarm - did not pass power system test.

FLEXmaster Adapter Module

The adapter module is the I/O unit for the FLEXmaster. The rear adapter has RJ-48C connectors and
supports up to eight T1 link interfaces.
8-pin RJ-48C Connectors

T1/E1 T1/E1
one for each link
R1 1
1 8
T1 2 Rec
3
R 4
T 5 Trans
2 7 6
7
Chassis Gnd 8
2 SLOT DOWN
P
4 O
R
T
Port E Connections
DB-25 (25 pin)
E
5 Not Used - 13 25 - Not Used
TX Clock B - 12 24 - Ext Clock A
Ext Clock B - 11 23 - Not Used
6 Not Used - 10 22 - Not Used
RX Clock B - 9
21 - Not Used
Carrier Detect - 8
20 - Data Term Ready
T1/E1 Signal Ground - 7 19 - Not Used
Data Set Ready - 6 18 - Not Used
Clear to Send - 5
17 - Rcv Clock A
Request to Send - 4
16 - Rcv Data B
Up to 8 T1 RX Data A - 3
15 - TX Clock A
TX Data A - 2
14 - TX Data B
Shield (Prot. Gnd) - 1

Power Supplies
There FLEXmaster 4.02 supports the 24/-48 VDC power supplies only. All power supplies are
redundant and load sharing. The following describes the LED states of both power supplies.

DC Input Off DC input missing or failure
Green DC input present
24/-48 VDC Power Supply (eight-slot)

The eight-slot 24/-48 VDC Power Supply configured for use with the FLEXmaster
4.02.
Power Supply
POWER DC Configuration Power Feed(s) Fuse
Wattage
±20 to 60 VDC 75W dual 5A, 250 V
24/48 VDC
75 W
24/-48 VDC Power Supply (two-slot)

The two-slot 24/-48 VDC Power Supply configured for use
with the FLEXmaster 4.02.
Power Supply Input Power

DC Configuration Fuse
Wattage Feed(s)
+24/-48VDC (20–70V) 30W dual 3.15A

Two-Slot Chassis
Two-Slot Chassis
The two-slot chassis provides two power supply slots for redundant power and two slots for
MASTERseries modules. The dimensions are: 1.75 inches high, 10.2 inches deep, and 19 inches wide.
Blank plates should be installed over each open slot to be in compliance with product emission
standards.
Installing a Two-Slot Chassis

Installation of the two-slot chassis is completed as follows:
1. Unpack the two-slot chassis.
2. Mount the chassis into an equipment rack.There must be 1 inch clearance space for the side vent
holes.
When the chassis is shipped it is configured for installation into a 19-inch rack. If you need to
install the unit into a 23-inch rack, remove the four screws from the rack mounting supports and
remove the supports. Then attach the rack mounting supports that were shipped with the
chassis.
23–inch mounting ears
3. If you are upgrading a series 2 or 3 chassis, you must install a new power supply and fan unit.
For more information see Two-Slot Upgrade on page 2-13.
4. Insert the power supplies.
Slide the first power supply into power slot #2. If you have redundant power supplies, remove
blank plate from the slot and slide the second power supply into power slot #1. Make sure that
the fan is plugged into the fan connector.
For details about seating the power supplies, see DC Powered Two-Slot on page 2-11.

Two-Slot Chassis
Installing Application Modules in a Two-Slot Chassis

CAUTION! INSTALL THE FLEXMASTER MODULE INTO A TWO-SLOT CHASSIS WITH THE
SMALLER HANDLE TO THE RIGHT OF THE CHASSIS. DO NOT INSTALL THE MODULE IN THE
OPPOSITE DIRECTION, AS THIS MAY CAUSE DAMAGE.
It is recommended to install the module in slot #2. To install a MASTERseries module into the two-slot
chassis, perform the following steps:
1. Gently slide the engine into the slot and press firmly so that it makes
full contact with the midplane connector located towards the back of
the chassis. Be sure that the ejector on the engine is to the right when
inserting into the chassis. The text along the edge should be upright.
2. Tighten the screws found on the front of the module. When correctly installed, the application
module faceplate will make contact with the chassis.
3. Insert the adapter module into the back of the two-slot chassis so that it makes full contact with
the midplane connector. In order for the two-slot chassis to be one rack unit compliant, the
adapter strip must be removed (see Adapter Strips on page 2-23). Be sure to install the adapter
module into the corresponding rear slot, and that the ports are to the right when inserting the
adapter into the chassis. Tighten the screws found on the adapter.
4. Insert the NMS cable into the NMS jack on the front panel of the FLEXmaster module. Plug
the other end of the NMS cable into the COM port of your PC or the port of your VT100
terminal.
5. Apply power to the unit.

Two-Slot Chassis
DC Powered Two-Slot
The -48 VDC and +24 VDC power entry modules provide DC power protection and isolation when you
attach the leads properly. See the following text and the figure on the next page.
Each input has its own return. The labels of the power entries vary based on what version of the chassis
you have. FEED A (IN A/RTN A) operates power supply 1; FEED B (IN B/RTN B) operates power
supply 2. Acceptable wire gauge is from 12 to 18 gauge.
CAUTION! IF YOU ARE USING TWO POWER SUPPLIES, POWER MUST BE CONNECTED TO BOTH
A AND B FEEDS. IF YOU ONLY POWER THE A FEED AND ARE USING TWO POWER SUPPLIES, YOU
WILL NEED TO JUMPER BETWEEN INPUT A AND INPUT B AND ALSO BETWEEN RETURN A AND
RETURN B. MAKE THIS JUMPER THE SAME GAUGE AS THE FEED.
Two-slot Power Supply
Power Entry Panel Alarm Terminal Block
DC Line Input Fuses

(A and B feeds)
Dual Power Feed - Dual Power Supplies

Attach the leads to the appropriate terminal as indicated in the graphic. Secure the leads with screws
on the terminal block to tighten them
-48VDC -48VDC
or Ground or
+24VDC +24VDC
RTN A IN B
Return A Power Entry B
RTN B
IN A
Return B
Power Entry A
red black green red

black black
red
+ - + -

Two-Slot Chassis
Single Power Feed - Dual Power Supplies

-48VDC DC Power
or Ground
+24VDC Jumpers
RTN A IN B
RTN B
IN A
Return B
Power Entry A
black green red

black black
black
red
+ - + -
NOTE: A ferrite (Fair-Rite P/N 0443164151, or equivalent) must be placed around the
DC battery feeds for compliant operation. The beads should be no lower than 3 inches
below the power entry panel.

Two-Slot Upgrade
Two-Slot Upgrade
If you are installing a FLEXmaster module in a chassis from series 2 or series 3, you must install a new
power supply, fuses and dual fan unit before operating it, due to the heat generated by the FLEXmaster.
This document describes:
Hardware Upgrade Procedure
Fan Replacement (on page 2-18 )
Contents of Kit
Dual fan unit Fan Unit
24/-48 VDC Power Supply
- DC Configuration: +24/-48VDC
(20–70V)
- Power Supply Wattage: 30W
- Input Power Feed(s): dual
Fuses
- 3.15A, 5mm x20mm
Labels
NOTE: Part number 8682UD1-AA

includes one power supply. Part
number 8682UD2-AA includes two
Power Supply
power supplies.
Hardware Upgrade Procedure

The following procedure describes how to install the dual fan unit, replace the power supply,
replace the fuses and apply new regulatory labels.
NOTE: The fan is installed in the center support bracket between module 2 and power
supply 2.
CAUTION! EXERCISE CAUTION WHEN INSTALLING OR REMOVING THE FAN MODULE.
1. Remove the right-hand screw from module 2.

Two-Slot Upgrade
2. Remove both screws from power supply 2.
Power Supply 2
Power Supply 1
Module 1
Module 2
Remove these Screws
3. Slide out power supply 2.

4. Hold fan module at an angle and insert into power supply slot.
Module 2
Power Supply
Slot 2

Two-Slot Upgrade
5. Engage the fan module into the bottom channel of the center support bracket and rotate
to vertical.
6. The fan module will snap into place. The fan module should rest flush with the center support
bracket face.

Two-Slot Upgrade
7. Insert the right screw into the faceplate of module 2. The screw should pass through the tab on
the front of the module.
Insert Screw Here
8. Slide the power supply from the kit halfway into the slot.
Before fully seating the power supply, twist the fan module power cable clockwise, and plug
into the power supply.
Power Cable
9. Continue to slide the power supply into the slot until fully seated.

Two-Slot Upgrade
10. Install the power supply retaining screws.
Power Supply 2
Power Supply 1
Module 2
Screws
11. If you are using two power supplies, replace power supply 1.
Replacing the fuses

The fuses are found on the rear of the power supply.
1. To replace a fuse, insert a flat screwdriver into the -
horizontal slot on the front of the cap and turn a quarter A B

turn counterclockwise. The cap will pop off with the fuse FUSE FUSE
inside.
2. Replace the old fuse with the fuse provided in the kit and
reinsert the fuse and cap into the fuse assembly.
NOTE: A ferrite (Fair-Rite P/N 0443164151, or equivalent) must be placed around the
DC battery feeds for compliant operation. The beads should be no lower than 3 inches
below the power entry panel. For more information see the graphic on page 2-12.
Applying the new labels

1. Apply the new labels to the rear of the power supply, over the existing ones. These labels are
required for compliance.
Powering the system
1. Apply power to the unit.
2. Verify the fans are functioning properly.

Two-Slot Upgrade
Fan Replacement
The following are instructions for fan replacement on the MASTERseries two-slot unit.
CAUTION! EXERCISE CAUTION WHEN REMOVING THE POWER SUPPLY WHICH POWERS THE
FAN UNIT. THE POWER CABLE IS SHORT AND COULD BE DAMAGED IF PULLED OUT WITH
EXCESSIVE FORCE.
1. Remove the right-hand screw from the module and both screws from power supply 2.
Power Supply 2
Power Supply 1
Module 1
Module 2

Two-Slot Upgrade
2. Pull out the power supply slowly.

Disconnect the fan power cable, and remove the power supply.
Fan Power Cable
3. Insert a small flat screwdriver into the slot indicated and pry the top part of the fan module
towards the power supply slot.
Power Supply Slot 2

Insert Small Flat
Screwdriver Here
Module 2
Module 1

Two-Slot Upgrade
4. Rotate the fan module into the power supply slot.
5. Remove the fan module.
6. Replace the fan. See steps 4-10, starting on page 2-14.

7. Replace the power supply.
8. Replace the retaining screws.

Eight-Slot Chassis
Eight-Slot Chassis
The eight-slot chassis provides two power supply slots for redundant power supply modules and slots
for eight MASTERseries application modules.
The dimensions are: 5.2 inches high, 10.2 inches deep, and 19 inches wide (expandable to
accommodate a 23-inch rack).
The maximum depth of the shelf, including cables, is 12 inches.
1RU of clearance is required above and below the chassis.
NOTE: FLEXmaster 4.02 supports a maximum of two FLEXmaster modules in a chassis.

No other modules are supported.
NOTE: Blank faceplates should be installed over each open slot to comply with product
emission standards.
Eight-Slot Chassis

Eight-Slot Chassis
Adjusting the Brackets for a 23-Inch Rack

The eight-slot chassis has reversible rack mounting brackets that allow for installation into a 19- or
23-inch rack. The unit is shipped with the mounting brackets installed for a 19-inch rack. To install in
a 23-inch rack, the brackets must be modified. The following steps walk you through this procedure.
1. Remove the four screws from the mounting brackets.
2. Turn them around so that the longer portion of the mounting brackets are now protruding from
the sides of the rack.
3. Reattach the brackets using two of the screws you previously removed. Place the remaining two
screws back into the location they were removed from.
23–inch mounting ears

chassis ground screw
connect to frame ground
Installing an Eight-Slot Chassis

To install the eight-slot chassis:
1. Unpack the eight-slot chassis.
2. Mount the chassis into a rack.
3. Insert the power supplies. See Eight-Slot Chassis on page 2-21 for locations.
Slide the first power supply into power supply slot A. Press firmly so that it makes full contact with the
connector in the back of the chassis. Secure the power supply using the enclosed screws.
If you have redundant power supplies, remove the blank plate from the slot (if installed) and slide the
second power supply into power supply slot B. Press firmly so that it makes full contact with the
midplane connector located towards the back of the chassis. Secure the power supply using the enclosed
screws.
After removing a power supply from the eight-slot chassis, allow approximately 15 seconds (discharge
time) before reinserting the supply.

Eight-Slot Chassis
Adapter Strips
All engine modules are shipped with an adapter strip attached to the faceplate for use on the eight-
slot chassis. This adapter strip reduces electromagnetic interference (EMI) and dust accumulation
within the chassis.
NOTE: The adapter strip is not needed with the two-slot chassis.
The adapter strip is flexible and slotted to wrap around the screws on the engine. To remove the
adapter strip, bend it around the two screws as the following figure shows.
The adapter strip is slotted to wrap around the screws that mount the right-side circuit board to the
engine faceplate.
Installation Instructions for Adapter Strips
Slide the adapter strip under the screw heads until snug as shown below.
Slide until snug

Top of Module- Bottom -
ejector handle fixed knob
NOTE: To avoid displacing the ejector assembly at the top of the engine, do not remove
the screws. Spacers below the screw heads allow enough space to install the adapter strip
without loosening the screws.
lide until snug

Eight-Slot Chassis
Rear Adapter Strip Installation

Each MASTERseries adapter module is shipped with an adapter strip and screws.
NOTE: The adapter strip is not needed with the two-slot chassis.
The adapter strip fits over the top, bottom, and left edge of the adapter module faceplate. If the
screws have been driven tight to the panel, back them out just far enough to allow the slotted end
of strip to fit under the screw head.
Slide over the partially

driven screws
Through holes
Adapter strip

Eight-Slot Chassis
Installing the FLEXmaster Module in an Eight-Slot Chassis

Before installing the application modules, please see the following note, then proceed to the following
pages which describe the installation.
WARNING! STATIC PROTECTION IS REQUIRED DURING INSTALLATION. PROPER HANDLING,

GROUNDING AND PRECAUTIONARY ESD MEASURES ARE ESSENTIAL WHEN INSTALLING AND
SERVICING PARTS OR CARDS. KEEP PARTS AND CARDS IN ANTISTATIC PACKAGING WHEN NOT
IN USE OR DURING TRANSPORT. IF POSSIBLE, USE ANTISTATIC FLOORPADS AND WORKBENCH
PADS.
Attach an adapter strip to the faceplate before installing the module (for instructions see Installation
Instructions for Adapter Strips on page 2-23). Install the FLEXmaster module into slot #1 (left slot) of
the chassis.

Eight-Slot Chassis
To install the FLEXmaster module into an eight-slot chassis:

1. Press on the bottom handle labeled Carrier Access. Push slowly until the connectors first make
contact. Then apply more pressure to fully engage the mating connectors so that the engine
makes full contact with the midplane connector located towards the back of the chassis. When
correctly installed, the application module faceplate makes contact with the chassis. Next,
tighten the two screws on the application module.
L
YE
A /X
F
O
O
L
YE
F
O
O
L
YE
C/Z
F
attaching O
O
screws YE
L
D O
F
O
2. Attach an adapter strip to the faceplate before installing the module (for instructions see
Installation Instructions for Adapter Strips on page 2-23).Insert the FLEXmaster adapter
module into the back of the chassis so that it makes full contact with the midplane connector.
Tighten the screws found on the adapter.
Be sure to install the adapter module into the corresponding rear slot.

Eight-Slot Chassis
3. Insert the Network Management System (NMS) cable into the NMS jack of the FLEXmaster
module. Plug the other end of the NMS cable into the COM port of your PC or the port of your
VT100 terminal.
-
8608
FLEXmaster8
RxD TxD PST ALM
NMS
8-Pin RJ45 Connector
for Network Management
T1/E1
Systems (NMS)
2
2 SLOT DOWN
4
8 - Not Used
6 7 - Not Used
8 6 - Not Used
5 - Gnd/Drain
4 - Not Used
ENET 2 3 - Rx Data
ENET 2
2 - Tx Data
1 - Not Used
ENET 1
ENET 1
Wiring Diagram
J1-2 P1-2
J2-2
J1-3 P1-3 J1
J2-3
J1-5 P1-5 P1 DB-9

J2-5
J1-8 P1-5 J2
J2-8
P1-1
P1-4 15 feet
P1-6
P1-7
P1-8
4. Apply power to the chassis. It will take a approximately 45 seconds before the module LEDs
are lit and the module(s) are fully operational.
NOTE: To remove an application module from an eight-slot chassis, remove the two
screws that lock the module faceplate to the eight-slot chassis, then lift up on the ejector
handle (labeled FLEXmaster) to disengage the connectors. Finally, slide the module out
carefully.

Eight-Slot Chassis
Powering the Eight-Slot Chassis

The wide-ranging DC supply is used for both -48 and +24 VDC applications. All power supplies are
redundant.
The power entry modules provide DC power protection and isolation when you attach the leads
properly.
Each input has its own return. Acceptable wire gauge is from 12 - 18 gauge.
The power terminal block and the alarm terminal block should be removed for easier lead
attachment. Pry up with a screwdriver and pull out.
+24/-48 DC Power Supply
DC Line Input Fuses Power Entry Panel
Alarm Contacts
NOTE: If you are using two power supplies, input power must be connected to both A
and B feeds. If you only power the A feed and are using two power supplies, you will need
to jumper between Input A and Input B and also between Return A and Return B. Make
this jumper the same gauge as the feed.
Connect 12-18 Gauge Wire Here

Terminal Block
Attach the leads to the appropriate terminal using the
securing screws on the block to tighten them.
The power terminal block and the alarm terminal block
can be removed for easier lead attachment. Pry up with a
screwdriver and pull out.
Wire Securing Screws

Eight-Slot Chassis
Dual Power Feed - Dual Power Supplies

-48VDC -48VDC
or Ground or
+24VDC +24VDC
RTN A IN B
RTN B
IN A
Return B
Power Entry A
red black green red

black black
red
+ - + -
Single Power Feed - Dual Power Supplies

-48VDC DC Power
or Ground
+24VDC Jumpers
RTN A IN B
RTN B
IN A
Return B
Power Entry A
black green red

black black
black
red
+ - + -
WARNING! THE GROUND TERMINAL ON THE POWER BLOCK MUST BE CONNECTED TO

FRAME GROUND TO PREVENT POSSIBLE DAMAGE TO EQUIPMENT. THE CHASSIS GROUND SCREW
(SEE Adjusting the Brackets for a 23-Inch Rack on page 2-22 FOR LOCATION) SHOULD
ALSO BE CONNECTED TO FRAME GROUND.

Eight-Slot Chassis
Alarm Terminal Block Definitions
MAJ. ALARM
N.C. Normally Closed
COM Common
N.O. Normally Open
MIN. ALARM
N.C. Normally Closed
COM Common
N.O. Normally Open
Alarm Contact
If the alarm contact feature is used, a ferrite is required.


The MASTERseries product line provides a variety of methods for remote access to the user interface.
Communications utilizing a standard telephone line and modem connected to the MASTERseries
console port provides one form of remote access to the user interface menu for diagnostic and
configuration control.
The following information is provided to reliably connect and configure a modem for remote access
connectivity to the MASTERseries user interface. This configuration requires pre-setting auto answer
functionality and line synchronization parameters for the modem. Modem switch settings combined
with changes to the modem configuration profile using AT commands will assure that the modem will
maintain auto answer capability at the assigned console baud rate after a modem or system reset or re-
power occurs.
You will need the following hardware (orderable through Carrier Access):
Modem type: fax modem
An NMS console access cable and a MASTERseries console adapter
The MASTERseries console adapter is a DB25M (that
connects to an external modem) to RJ-45. An 8-pin RJ-45
to RJ-45 straight through cable is used to connect the
RJ-45 side of the console adapter to the NMS port. The
cable requires end-to-end connectivity for pins 2, 3, and 5. RJ-45 DB-25
See the following table page for pinouts of the console Male
adapter. (modem)
MASTERseries Console Adapter Pinouts

1 - Shield —
2 - Transmitted Data 2 - Transmitted Data
3 - Receive Data 3 - Receive Data
4 - Request to Send (this pin is tied to pin 8) —
5 - Clear to Send 5 - Ground/Drain
6 - Data Set Ready —
7 - Signal Ground —
(this pin is tied to pin 5 on the RJ-45 side)
8 - Carrier Detect —

The redundancy configuration “Y” cable shown below is a RJ-45 “Y” cable that can also be used with
the MASTERseries console adapter. It allows backup for management of the shelf in the event of a
master toggle. When a master toggle occurs, the next populated module to the right of the master module
becomes the backup.
Wiring Diagram Console Adapter
J1-2
Redundancy Configuration
J3-2
J2-2 J1 “Y” Cable
J1-3 J3-3
J2-3 J3 DB-25
J1-5 J3-5
J2-5 J2
J1-8 J3-8
J2-8 15 feet
NOTE: You should connect the single connector end RJ-45 to the MASTERseries
console adapter. One of the pair of other RJ-45s connects to the NMS port of the master
module, the remaining RJ-45 on the cable connects to the next populated module. All three
RJ-45 connectors on this cable are pin-to-pin straight-through.
The following table lists the modem DIP switch settings:

Carrier Access
DIP Switch Settings Default
Configuration
Up Data Terminal Ready Normal - Down Data Terminal Ready Up Down
Override
Up Verbal Result code - Down Numeric Result Code Up Up
Up Suppress Result Codes - Down Display Result Codes Down Up
Up Echo Offline Commands - Down No Echo, Offline Up Down
Commands
Up Auto Answer on the first Ring specified in NVRAM - Down Down Up
Auto Answer Off
Up Carrier Detect Normal - Down Carrier Detect Override Up Down
Up Load NVRAM Defaults - Down Load Factory Defaults Up Up
Up Dumb Mode - Down Smart Mode Down Up
NOTES:
1 - Up = Off, Down = On
2 - On modems pre-configured for MASTERseries access, DIP switches must be returned to factory
default mode for console echo and result codes to appear on the access terminal.

You must enter the following AT commands to configure the supplied modem:
NOTE: Modems purchased from a source other than Carrier Access should be
configured with the parameters provided in the user manuals provided with the modem.
AT&F - Load factory defaults. Issue this command first.

AT&C0 - Force carrier detect high
AT&D0 - Modem ignores DTR—override
AT&E3 - Flow control disabled
AT&E14 - Data compression disabled
ATS0=1 - Auto answer on the first ring
AT&W0 - Saves this command string to the ROM (this Save Profile command must be entered
last)
ATL5 - Lists the current operating parameters


CHAPTER
3
Configuration
In this Chapter
Accessing the FLEXmaster Interface
Recommended Configuration Sequence
Configuration

Connect the network management cable (provided with your FLEXmaster equipment) to the RS-232
port on your PC and the NMS port on the FLEXmaster module.
Port Setup
The FLEXmaster software screens are viewable through a VT100 terminal or through a PC using a
VT100 terminal emulation software application. The following table describes the parameters needed
to configure a system using a VT100 terminal or emulation software
Data bits: 8
Parity: None
Stop Bits: 1
Terminal Type: VT100
ANSI Setup: ANSI page length=25, Strip ANSI from capture file
VT100 Setup: Send DEL for backspace, Cursor visible
Column Width: 80 Columns
Baud Rate: 4800, 9600 (default), 19200
NOTE: The first time you bring up the system, you must connect using a 9600 baud
rate.
Procomm Users—If you are unsure of the baud rate set on a module, connect to that module at
19200 baud and press the R key. If no response, use 9600 baud using the same approach. If there is
a baud rate mismatch between Procomm and the FLEXmaster module, the module could reboot. To
prevent this, go to setup->setup and select the Data tab, then select Terminal Options then set the
Enquiry Type field to OFF. Later versions of Procomm might require you to navigate to the
Enquiry Type field differently. Consult your Procomm manual.
Additional Settings
Hardware flow control: Off
XON/XOFF flow control: Off
Use DTR (for hang-up Off
Monitor DCD (carrier): Off
Exit on hang-up: Off

Configuration
Navigating the Screen

The following figure shows a sample screen and describes the fields on the screen. Screens can look
somewhat different depending on your configuration, the modules you have installed, and your software
version.
In release 4.02, each module appears as a master module.
Master/Slave Status
All configuration
changes must be
made from the
Physical Slot master module
Software
Number that
NMS cable is Version
Configuration Number Menu Area
attached to
being edited
01 MASTER CARRIER ACCESS MASTERseries Ver 4.02

------------------------------ your sysname here ------------------------------
Alarms sTat Diag pOrt Link tImeslot clK Connect coMmit aPs Setup Help
----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------
<------- LINK -------> <- PORT -> <------- MGMT ------->
M T1 ABCD 111 1111 EFGH 111 Configuration
1111
# S E1 MODULE TYPE 1234 5678 9012 3456 1 1234 5678 9012 3456 number
currently
- - --------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- running
1 M T1 FLEXmaster OOUU OOOO uu uu
2 -
3 -
4 -
5 -
6 -
7 -
8 -
Power Supply 1 Down Fans Down

Power Supply 2 Up
u=Unassigned U=Up D=Down I=Init d=Diag O=Off (Disabled)

---------------------------------- GREEN ---------------------------------
Alarms: Clk: INT Jan 25, 2005 11:29
Cards having active link alarms Link Alarm Summary Network

If slots are in green state, this area is blank. Indicates alarm state Clock Date/Time
Also power supplies and fans in alarm state. of chassis Source
The first screen that you see (after the power-up screen) when you bring up the VT100 terminal or
emulation software is the Alarms screen. This screen lists each unit installed in the chassis and the
current status of each link, port, management channel, and power supply. An alarm status summary and
a listing of any slot currently in alarm is listed at the bottom of every screen. You may have to refresh
the alarm screen by pressing R. If the top line of the screen does not refresh, press [ESC], then R again.

Configuration
Keyboard Navigation
Select screens using hot keys. Hot keys are the capitalized letters in menu names. Example: the
hotkey for the Alarms screen is A, the hotkey for sTat is T.
Scroll within screens using the up and down arrow keys. (the arrow keys may have to be set up
for terminal use in your communications software).
The following table summarizes keyboard navigation.
Action Press these Keys Representation in manual

Select a menu S (for Setup)
ENTER S (Setup)
C (for Consol) C (Consol)
ENTER
Cycle through a N (for Next) N/P
cyclical field P (for Previous) cyclical field
Accept selection ENTER [ENTER]
Exit a menu, ESC [ESC]
Save Settings
Navigate through Up Arrow ↑
a screen Down Arrow ↓
Refresh display R

Configuration
Interface Identifiers
Interface names are made up of four characters - digit letter digit digit.
The first number indicates the module location. The letter indicates if the interface type. The final two
digits indicate the interface ID.
{Slot Number} {Interface Type} {Interface ID}
Description This is the slot Single character T1 link ID. Possible
position of the representation of the values: 01-08 on a
module in the interface type single module.
chassis. Possible
values: 1-8
Example 1 L 01 1L01
Interface types:
E Ethernet Port
M Serial (HDLC)
P v.35 port
X PPP Interface
Link types:
L DS1 Link

Configuration
Menus
The menu bar
These items have no submenus:

sTat, Link, clK, Connect, coMmit, aPs, Help.
The following items have submenus which are described below:

• Alarms Menu
• Diag Menu
• Port Menu
• Setup Menu
Alarms Menu
Select Alarms and press [ENTER] to open the Alarms sub-menu. As with other screen and menus,
type the hotkey (capitalized letter) to enter that selected screen/menu.
For more information about hotkeys, see Keyboard Navigation on page 3-4
Alarms Linklog Syslog trHold Performance trunK Minor_def acO
Local_stats reMote stats Definitions Signaling Datacodes
Show_remote_stats send_reMote-msg
Menu Item Navigation Function

acO Alarms > acO Configures the operation of the
external alarm contact closures
at the rear of the chassis.
This feature is not available in
FLEXmaster 4.02
Datacodes Alarms>trunK>Datacodes Defines the data patterns that are
transmitted in place of normal
data, on bypass connections,
when a link is in alarm.

Configuration

Definitions Alarms>Performance>Definiti Displays definitions of
ons performance monitoring error
messages.
Linklog Alarms>Linklog Displays a record of major and
minor alarms for each link.
Local_stats Alarms>Performance> Displays performance
Local_stats monitoring statistics for links
with performance monitoring
enabled.
Minor_def Alarms > Minor_def Defines the conditions which
generate a minor alarm.
send_reMote-msg Alarms>Performance>reMote Sends a message to the far end
_stats> send_reMote-msg to request individual statistics.
Show_remote_stats Alarms>Performance>reMote Shows the performance
_stats> Show_remote_stats monitoring statistics for the far
end of a link that has been
configured for T1_ESF framing
and the performance monitoring
protocol set to AT&T_54016 or
T1_403.
Signaling Alarms>trunK>Signaling Defines the ABCD/abcd
signaling patterns that will be
transmitted in place of normal
signaling when a link is in
alarm.
Syslog Alarms>Syslog Displays a history of system
events, including configuration
changes and error conditions.
trHold Alarms>trHold Configures the links which
signal an alarm when a specified
level of unavailable/errored
seconds is exceeded for links
that have performance
monitoring enabled.

Configuration
Diag Menu
Select Diag and press [ENTER] to open the Diag sub-menu. As with other screen and menus, type
the hotkey (capitalized letter) to enter that selected screen/menu.
Linkdiag Portdiag Carddiag Warmreset master Toggle Upgrade

Carddiag Diag>Carddiag not currently supported.
Linkdiag Diag>Linkdiag Controls the diagnostic
loopbacks and BERT functions
of each link.
master_Toggle Diag>master_Toggle Toggle from the current master
module to the next lowest
number in the chassis.
This is not supported in rel. 4.02.
Portdiag Diag>Portdiag Controls the diagnostic loopback
and BERT functions of ports.
Upgrade Diag>Upgrade Upgrade the software running on
the selected module.
Warmreset Diag>Warmreset Reboots the chassis.

Configuration
Port Menu
Select Port and press [ENTER] to open the Port sub-menu. As with other screen and menus, type
the hotkey (capitalized letter) to enter that selected screen/menu.
Dacs Mgmt

Dacs pOrt>Dacs Configures port parameters.
Mgmt pOrt>Mgmt Configures the management port and the
connection rate (64) of the management
channel to a remote site.
Setup Menu
Select Setup and press [ENTER] to open the Setup sub-menu. As with other screen and menus,
type the hotkey (capitalized letter) to enter that selected screen/menu.
Maint Consol Time SendL Send receivE Xfer Passwds cOnfig Abcd mGmt Vers
Cli

Abcd Setup>Abcd Defines ABCD idle signaling bit patterns
cOnfig Setup>cOnfig Changes the configuration currently being edited.
Consol Setup>Consol Sets the communication parameters for the NMS
port.
Cli Setup > mGmt Connects you to the command line interface (CLI).
> Cli
Maint Setup>Maint For engineering use only.
Passwds Setup>Passwds Use to define the Superuser, Maintenance and
Telnet passwords.
receivE Setup>receivE Not supported in release 4.02
Send Setup>Send Not supported in release 4.02

Configuration
Menu Item Navigation Function (Continued)

Sysname Setup > mGmt Create user-selected system name. This name
> Sysname appears in the second row of the screen.
SendL Setup>SendL Sends a copy of alarm and syslog to a text file (.txt)
on your PC.
Time Setup>Time Sets the date and time
Vers Setup>Vers Displays the software version number running on
the installed modules.
Xfer Setup>Xfer Transfers program files from the master module to a
slave module installed in the same chassis.
Master/Slave functionality is not supported in
FLEXmaster 4.02

Configuration
Recommended Configuration Sequence

The MASTERseries modules must be configured in the order presented in this chapter. Below are links
to the subsections, in the recommended order.
1. Local Access to the FLEXmaster
2. Setting the Date and Time
3. Configuring the Configuration Editor
4. Specifying the Link Parameters
5. Configuring System Timing
6. Configuring the DACS Port
7. Configuring the Management Port
8. ABCD/abcd Signaling Patterns
9. Configuring the Data Patterns
10. Configuring Internal Timeslot Connections
11. Using the Timeslot Screen
12. Full Duplex Cross Connects
13. Configuring APS for Link Failures

Configuration
Local Access to the FLEXmaster

Use the console screen to set the communication parameters for the NMS port. This port is used with
the network management cable for local access from a PC or VT terminal to the FLEXmaster module.
It is recommended that you use the default settings as shown here:
Rate : 9600
Mgmt : Console
Telnet: 23 (standard server port)
Data : 8
Stop : 1
Parity: Disable

Maint Consol Time sendL Send receivE Xfer Passwds cOnfig Abcd mGmt Vers
----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------
Password:
Rate : 9600
Mgmt : Console
Mode : Standalone module
Data : 8
Stop : 1
Parity: Disable
To set the Console settings, follow these steps. Descriptions of the fields are in the table on the next
page.
1. To enter the screen, press [ENTER]. S (Setup)
2. Type your password and press [ENTER]. If the password is not entered C (Consol)
correctly, read-only access is provided (see more about passwords in the
following table).
3. At the Rate prompt, cycle through the rates using the N/P keys. To save your selection, press
[ENTER], then [ESC].
4. At the Management prompt, select PPP or Console using the N/P keys. To save your selection,
press [ENTER], then [ESC].
5. Data, Stop and Parity are fixed values.
6. To exit this screen, press [ESC]. This will prompt the Save field. Press Y or N to save or cancel
your changes.

Configuration
The following table describes the fields on the console screen:

Console Screen Definitions
Password This is a 12 position editable field with superuser access only. The default
password on all screens is blank (press [ENTER]).
Rate 4800 bps
9600 bps (default)
19200 bps
If the Rate option has been set at an improper console speed, the unit will not
be accessible. The boot-up screen and the Carrier Access copyright screen are
defaulted to 9600 baud. If the console speed is set to a baud rate other than
9600 and the unit is power cycled, the opening screens which are defaulted will
not be readable. When the application software has been loaded it will
automatically adapt to the configured baud rate.
Management Console—(default).
(Mgmt) PPP—Asynchronous point-to-point protocol. Used when connected to an IP
based network interface such as a Cisco router’s AUX port.
If the PPP option has been selected without a proper PPP device available, the
Consol screen will not be accessible. To return to the console mode (normal
operation) press the R key at least five times with a one-second pause between
each key depression. There can be up to a 10 second delay for the transition to
complete.
Mode This defaults to Standalone Mode in version 4.02
Data Fixed value = 8, the number of data bits in a character.
Stop Fixed value = 1, the number of stop bits in a character.
Parity Fixed value = Disable parity.
Accessing Two Standalone Units from a Single Ethernet Connection

An Ethernet Crossover cable is required to connect and communicate
Ethernet Crossover
from the NIC card of a PC to the FLEXmaster Ethernet Port. Two
Cable Pin Intersects
standalone FLEXmaster modules in one MASTERseries chassis can be
accessed via the Ethernet ports using a crossover cable.
To create the physical connection: 1 3
1. Use a crossover cable to connect from Ethernet Port 2 on the first

module to Ethernet Port 2 on the second module. 2 6
2. Connect a crossover cable to Ethernet Port 1. This is the local

3 1
ethernet connection.
The graphic on the right illustrates the pins intersected in the crossover 6 2
cable.

Configuration
Setting the Date and Time
Setting the Date and Time

Use the Time screen to view and change the date and time. The date and time must be set to give accurate
time stamping of network events and alarm conditions.
1. To enter the screen, press [ENTER]. S (Setup)

2. At the Day prompt, key in the date in a two-digit format. Example: key 01 for T (Time)
the first of the month. Press [ENTER].
3. At the Month prompt, select the month using the n/p keys. Press [ENTER].
4. At the Year prompt, type in the current year using four digits. Press [ENTER].
5. At the Hour prompt, type in two digits in military time. Example: type in 14 to represent 2 p.m.
Press [ENTER].
6. At the Minute prompt, type in the current two-digit minute. Press [ENTER].
7. To exit this screen, press [ESC]. This will prompt the Save field. Press Y or N to save or cancel
your changes. Press [ENTER] to continue.

Configuration
Configuring the Configuration Editor
Configuring the Configuration Editor

Configurations are complete sets of operational parameters that allow you to define how the system
functions. Up to sixteen different configurations are stored in non-volatile memory. Use the cOnfig
menu to select the configuration currently being edited. This has no impact on which configuration is
currently running in the system. The EDIT configuration and the RUN configuration are always
displayed in the config status field located below the menu bar.

----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------
Password:
Enter the Configuration to edit CFG 6
1. To enter the screen, type the superuser password and press [ENTER]. If the S (Setup)
password is not entered correctly, read-only access is provided.
O (cOnfig)
2. Use the N/P keys to select the configuration to edit/use. Up to 16
configurations are supported, CFG 1 through CFG 16.
3. Press [ENTER] to exit this screen.
Creating a New Configuration

Create a new configuration to reset the variables in the editor to the default values. The EDIT indicator
(upper left corner) displays NEW.

----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------
Password:
Enter the Configuration to edit NEW
After the new configuration is changed, error check and save the changes using the commit screen (see
Error Checking, Saving, and Activating the Configuration on page 3-34). This process allows you to
assign a configuration number from 1 to 16.

----- EDIT: NEW ------------------------------------------ RUN: CFG 1 -------
Password:
NOTE: Current configuration is NEW

Save to: CFG 1
Save Now:

Configuration
Specifying the Link Parameters

Use the link screen to specify the link parameters for each module installed in the chassis.
Follow the steps below to specify the parameters for a link. Definitions for each of the
L (Link)
field are on the next page.
1. From the main screen, press the L key to go to the Link screen.
2. At the No. prompt use the N/P keys to cycle to the link you want. Or type in the ID of the link
(example: 2L03. Press [ENTER] to move to the Name prompt.
3. At the Name prompt type in a name
No => 1L04 T1 DS1_LINK
of the link. This can be up to eleven Name => mfg4
characters in length. Dest => mfg
Press [ENTER]. Frame => T1 ESF
4. At the Dest prompt type in a name LBO => 0dB
Code => B8ZS
for the destination of this link. Disable => No
Press [ENTER]. IdleCode=> 50 (1 hex byte from 00 to ff)
CrossAIS=> No
5. Select values for the next three LpUpCode=> 10 (1 hex byte from 08 to 7f)
Protocol=> T1_403
fields (Frame, LBO and Code)
using the N/P keys to cycle through
the options. Press [ENTER] after each entry.
6. Type in a hex value for conditioning on idle links, then [ENTER].
The following table describes the fields that appear on the link screen:
Link Screen Definitions
No This is a four position cyclical field containing the slot number and link ID
(Number) number of modules installed in the chassis. The first digit indicates the slot
number. The second and third characters indicate the link ID). For details
about other interfaces see Interface Identifiers on page 3-5.
Name This is a user-defined meaningful name for the local side of this link. Can be
up to eleven characters.
Dest This is a user-defined meaningful name for the destination side of this link.
(Destination) Can be up to eleven characters.
Frame This is a cyclical field. It is used to specify the link framing format.
T1 ESF—Select for extended superframe formats (T1 default)
T1 D4—Select for superframe (D4) formats
T1 ERIC—Select when connecting to equipment that uses Ericsson modified
D4 framing format. This format does not support signaling.

Configuration
Link Screen Definitions (Continued)

LBO This is a cyclical field. Use this field to set the output attenuation level of the
(Line Build link. (This prevents overdriving and cross-talk on short lines.)
Out) 0dB—T1 only (default)
7.5dB—T1 only
15dB—T1 only
22.5dB—T1 only
Code This is a cyclical field. It is used to specify the line code to be used.
B8ZS—T1 only (default)
AMI—T1 only
Disable This is a cyclical field which enables or disables the alarm reporting features
of the selected link. Prior to disabling a link, you should remove any
configured traffic including management channels and clock sources
associated with that link.
Yes—Use if the link is not being used and you want to prevent alarms from
being reported on the link.
No—(default) Enables alarm reporting for the specified link.
IdleCode This is an editable field. It contains the hex value for the idle code to be
transmitted on each link.
Default = 50.
CrossAIS This is a cyclical field that enables or disables cross AIS functionality for each
(Cross Alarm link.
Indication Yes—Select this if you want the incoming Alarm Indication Signal (AIS; blue
Signal) alarm) to be allowed to propagate through a fully crossconnected link to
which channels are bypassed.
No—(default) Select this if you do not want the Alarm Indication Signal (AIS;
blue alarm) to be allowed to propagate through.
CrossAIS cannot be set if any channels are dropped or inserted in a related
link. Attempting to save such a configuration will cause an error condition,
and be recorded in the syslog screen. Do not set crossAIS and APS on the
same link.
Sig_mode This is a cyclical field that defines the signaling mode for the link being
(Signaling configured.
Mode) CAS—(Channel Associated Signaling) Uses timeslot 16 for voice signaling.
CLEAR—No signaling (clear channel). This option allows the use of timeslot
16 for user traffic.
LpUpCode This is an editable field. It contains the hex value for the LoopUp code to be
(LoopUp transmitted on each link. Type in a hex value for the desired links, then
Code [T1]) [ENTER]. Default (10) standard LoopUp code. User defined LoopUp codes
may be used to loop up mid-span repeaters.

Configuration
Link Screen Definitions (Continued)

Protocol This field specifies the Facility Data Link (FDL) protocol and enables
performance monitoring statistics for the specified link. The MASTERseries
application modules have both near and far end performance monitoring
capabilities on T1 ESF compliant links using ANSI T1.403 or AT&T TR
54016 protocols. Near end performance monitoring capabilities are also
implemented on T1 SF (D4) and E1 links. The performance monitoring
software will collect performance parameters using a one second window; it
will then organize and store the performance data in current and previous
second, 15-minute, 24-hour, 48-hour, and 72-hour intervals. This data
provides end-to-end error performance statistics that can be used to determine
service quality. When you have displayed the required selection, press
[ENTER].
Off—No error collection (default).
T1_403—(T1 ESF only) FDL operates in ANSI T1.403 mode, near end and
far end.
ATT_54016—(T1 ESF only) FDL operates in AT&T 54016 mode near end
and far end.
PMON_D4—(T1 D4 or T1 ERIC only) Provides superframe near end only
performance monitoring
T1 Link Screen

----- EDIT: CFG 4 ------------------------------------------ RUN: CFG 1 -------
No => 1L01 T1 DS1_LINK
Name =>
Dest => Boulder
Frame => T1 ESF

LBO => 0dB
Code => B8ZS
Disable => No
IdleCode=> a1 (1 hex byte from 00 to ff)
CrossAIS=> No
LpUpCode=> 10 (1 hex byte from 08 to 7e)
Protocol=> T1_403

Configuration
Configuring System Timing
Configuring System Timing

Use the system timing configuration screen to specify the link(s) to be used as system K (clK)
timing sources. You can configure one primary and one or more secondary external
timing sources, or you can configure an internally generated timing source. The primary source is the
link that is chosen first when scanning for a new clock source.
Automatic switchover to the first available secondary clock source is initiated upon failure of the
primary source. Clock source availability is determined by scanning from the first available link to the
last available link in the module. If no secondary is available the clock will fall back to the internal
timing source of the module. Automatic restoral to the primary timing source will occur only if the
timing source is internal or the current secondary fails.

----- EDIT: NEW ------------------------------------------ RUN: CFG 1 -------
Clock Mode : External
<-------------------------- LINK ----------------------------->

A B C D 1 1 1 1 1 1 1
# MODULE NAME 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6
- ------------- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---
1 FLEXmaster Pri Sec Sec Non Non Non Non Non
Setting the System Clock

1. Use N/P keys to select either Internal or External, then press [ENTER].
2. For each enabled link use the N/P keys to select PRI, SEC or NONE.
The following table describes the fields on the system timing configuration screen:
ClK Screen Definitions
Clock Mode Internal—(default) The timing source is the internal crystal of the module
(±25ppm)
External—The timing source is derived from the network using loop timing
Links 1-8 NON—(default) Indicates that this link is not a timing source.
PRI—(primary) Indicates which link is the primary timing source for the
chassis. You can select only one primary source.
SEC—(secondary) This is an alternate timing source that can be used if the
primary source fails. There is no limit to the number of secondaries.
A primary source must be selected if the clock mode is external to prevent
synchronization problems. The system timing source specifications for each of
the 16 configuration files should be identical to simplify system administration.

Configuration
Configuring the DACS Port

Use the DACS (Digital Access and Crossconnect System) port screen to configure port O (pOrt)
parameters. DACS allow you to add, drop and/or switch data traffic as necessary across
multiple links. The following figure and screen show an example of a DACs D (Dacs)
connection.
NOTE: Only one port is supported in FLEXmaster 4.02 .
LAN
DS0 # 1
DS0 # 2
320k Digital
Router V.35 Cross-Connect DS0 # 3
1P01 Link 1L03
DS0 # 4
DS0 # 5
Navigating through the DACS screen

Press the [ENTER] key to navigate through the modifiable fields. Use the N/P keys to cycle through
the available values.
1. Select internal or external for the selected port using the N/P keys. Press [ENTER] to continue.
2. Select 56 or 64 kbps as the base rate. Press [ENTER] to continue.
3. Select desired control lead using the N/P keys, Press [ENTER] to continue.
4. These fields default to auto, but when On are always active.
5. To save your changes, press [ESC] to exit the screen. coMmit.
The following table describes the fields on the Dacs port screen:
Dacs Port Screen Definitions

Card This is a cyclical field which lists modules installed in the chassis.
Clock This is a cyclical field which configures the data port clock sources for each
port.
Intnl—(internal) (default) The system supplies a clock synchronized to the
network.
Extnl—(external) The clock is supplied by an external CPE device
(sometimes called 306 mode in other devices).
Type This is a fixed field (DACS).

Configuration
Dacs Port Screen Definitions (Continued)

Interface This is a fixed field which identifies the interface type as V.35 or RS530.
Base This is a cyclical field.
Nx64—64 kbps operation (default)
Nx56—56 kbps operation with bit stuffing.
Rate This is a protected field. It lists the connection rate and is equal to the base
multiplied by the number in the #TS fields which are assigned on the
connect screen.
Link This is a protected field which contains the link identification that this port is
connected to and the user specified link name configured in the Name field
on the link screen.
Number of This is a protected field which contains the number of time slots assigned to
Timeslots (#TS) the connection.
Clear To Send This is a cyclical field. It configures the operation of the CTS signaling lead.
(CTS) On—Signal is forced high
Auto— (default) Follows RTS
Data Set Ready This is a cyclical field. It configures the operation of the DSR signaling lead.
(DSR) When you have displayed the required selection, press [ENTER].
On—Signal is forced high
Auto—(default) Follows DTR
Data Carrier This is a cyclical field. It configures the operation of the DCD signaling
Detect (DCD) lead. When you have displayed the required selection, press [ENTER].
On—Signal is forced high
Auto—If the link that this port is connected to is in alarm, the DCD is turned
off. If the alarm status is green, yellow, or minor the DCD is on. (default)

Configuration
Configuring the Management Port
Configuring the Management Port

Use the management screen to configure the management port and the connection rate O (pOrt)
of the management channel to a remote site. M (Mgmt)

Dacs Mgmt
----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------
<-------- Origin --------><- Type -> <----------- Path ----------->
Port Type Base Rate ID Link-Name TimeSlot
1M01 MGMT 64k 0k Idle
1M02 MGMT 64k 0k Idle
The following table describes the fields on the management port screen:
Management Port Screen Definitions
Provisioning the management port—Select Mgmt.
Available management ports are displayed on the screen.
Port This is a fixed field that lists the available management ports.
Origin Type This is a protected field. It will always indicate MGMT.
Base This is a cyclical field. When you have displayed the required selection, press
[ENTER].
64k—64 kbps operation (default)
Rate This is a protected field. It lists the connection rate and is equal to the base
multiplied by the number of TS fields that are assigned to this management port
on the connect screen.
Type Use the N/P keys to select the destination of the management link. The default
is Idle.
Port—Will go to a user selectable port ID.
Link-Name This is a protected field which contains the link ID that this management port is
connected to and the user supplied link name which is configured on the link
screen.
Timeslot This is a protected field which contains the timeslot number of this management
connection. It is configured on the connect screen.

Configuration
ABCD/abcd Signaling Patterns
ABCD/abcd Signaling Patterns

Use the trunk conditioning signaling screen to define the ABCD/abcd signaling
A (Alarms)
patterns that will be transmitted in place of normal signaling when a link is in
alarm. The ABCD signaling pattern is transmitted when the link first enters the K (trunK)
alarm state. After the first 2.5 second interval, the abcd signaling pattern is S (Signaling)
transmitted until the alarm state clears.

Signaling Datacodes
----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------
Password:
Trunk Conditioning Signaling Patterns (in form ABCD/abcd)
1. No TC 2. 1011/1111
3. 0011/0000 4. 1111/0000
5. 0101/1110 6. 0001/1110
7. 1110/0111 8. ----/----
9. ----/---- 10. ----/----
The following table describes the fields on the trunk conditioning signaling screen:
Signaling Screen Definitions
Password This is a 12 position editable field. Type your password (superuser access is
required) and press [ENTER]. If the password is not entered correctly, read-
only access is provided.
Signaling Trunk Conditioning Signaling Patterns <in form ABCD/abcd>—This is an
editable field that allows you to configure up to nine signaling patterns. The
patterns defined here can be assigned to each time slot configured for robbed bit
or CAS signaling of each link using the ABCD/abcd field on the connect screen.
(CASD2 and robbed signaling only supported link to link).
Save When you have completed entering the above listed fields, press [ESC]. This
will prompt the Save field.

Configuration
Configuring the Data Patterns
Configuring the Data Patterns

Use the trunk conditioning datacodes screen to define the data patterns that will A (Alarms)
be transmitted in place of normal data on bypass connections when a link is in
alarm. K (trunK)
D (Datacodes)
01 MASTER CARRIER ACCESS MASTERseries

------------------------------ your sysname here -------
---
Signaling Datacodes
----- EDIT: NEW --------------------------------------
---
Password:
Trunk Conditioning Signaling Patterns (in form ABCD/abcd)
1. No TC 2. ----/----
3. ----/---- 4. ----/----
5. ----/---- 6. ----/----
7. ----/---- 8. ----/----
9. ----/---- 10. ----/----
Trunk Conditioning Datacodes (in 8 bit binary)
1. No TC 2. 11110000
3. -------- 4. --------
The following table describes the fields on the trunk conditioning signaling screen:
Datacodes Screen Definitions
Password This is a 12 position editable field. Type your password (superuser access is
required) and press [ENTER]. If the password is not entered correctly, read-only
access is provided.
Datacodes Trunk Conditioning Datacodes (in 8 bit binary)—This area is only editable
when Datacodes is selected from the menu. The datacodes defined here can be
assigned to each time slot configured for bypass using the Datacode field on the
connect screen.
Save When you have completed entering the above listed fields, press [ESC]. This will
prompt the Save field. Press Y on the keyboard to save the entries made. Press N
on the keyboard if you do not want to save your changes. After completing the
required fields, press [ENTER] to return to the menu.

Configuration
Configuring Internal Timeslot Connections

Use the connect screen to configure the internal timeslot connections for the link interfaces available in
the chassis.
A link can be connected to
other links
physical ports
logical management ports
or can be left idle
What kind of Link? Name Description

Link connected to another link Bypass Connects current timeslot to another timeslot on
another link.
Physical Port Drop This configures the system to connect the current
Drop/Insert from a data port to timeslot to a data port interface (E, F, G, or H) that
a link is specified in the drop column.
Logical Management port Mgmt Connects the current timeslot to a logical
Management Connection For management port interface (M1 or M2). Configures
Remote Access the specified timeslot to provide remote
management connectivity.
Idle Idle Timeslot is unassigned, that is, not connected to a
port or a link. Configuring the timeslot as idle will
cause the system to transmit PCM idle code and
signaling bit idle code for the appropriate link. *
* PCM idle code is configured using the IdleCode field in the link screen and signaling bit idle code is
configured using the Idle ABCD field on the connect screen.

Configuration
The operation of the connect screen differs depending on the type of unit and link C (Connect)
that is being configured.

----- EDIT: NEW ------------------------------------------ RUN: CFG 1 -------
No: 1L01 T1 DS1_LINK
Name: Destination:
Frame: T1 ESF
IDLE <----- DROP -----> <--------- BYPASS --------->

TS Type Sig ABCD Port Type Rate Link TS ConName
01 Bpss Clr 1101 - - - - 1L03 01 LA
02 Bpss Clr 1101 - - - 1L04 02 NewYork
03 Idle Clr 1101 - - - - - - -
----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------

Name: Destination:
Frame: T1 ESF
Connect Screen Header Definitions

Number (No) Number (No) is a cyclical field that lists the slot and link ID of link interfaces
that connect directly to the TSI subsystem for modules installed in the
chassis. These are the links that require internal system connectivity and
configuration. When you have displayed the desired link to configure, press
[ENTER].
Name This is a protected field that contains the user supplied name of the link. The
user supplied name is configured on the link screen.
Frame This is a protected field. It contains the frame type of the link that was
configured in the link screen.
Destination This is a protected field that contains the user supplied name of the
destination link. The user supplied destination name is configured in the link
screen.
Signal This is a protected field that is displayed only for E1 links. It contains the
signaling mode (Clear or CAS) that was configured in the Sig_mode field in
the link screen.

Configuration
IDLE <----- DROP -----> <--------- BYPASS --------->

01 Idle Clr 1101 - - - - - - -
02 Idle Clr 1101 - - - - - - -
Connect Screen Timeslot Definitions

TimeSlot (TS) Displays the DS0 timeslots in the specified link. Use the keyboard to select
a timeslot.
Type This is a cyclical field used to configure the connection type. The following
connection types are available for each kind of link that requires connect
screen configuration: Idle, Bpss, Drop, Voic and Mgmt. When you have
displayed the desired connection type, press [ENTER].
Idle Signaling This is a cyclical field which allows you to configure the idle signaling to
ABCD be transmitted on the specified timeslot. The field cycles through the
ABCD signaling patterns defined on the ABCD screen. When you have
displayed the required selection, press [ENTER].
DROP Column The fields in this column are used to identify the destination port that will
be connected to the link and timeslot currently being configured. Note that
once a link ID/timeslot number combination (for example, link A/Timeslot
#1) on the mid plane syncbus has been used, it cannot be used for another
connection or a Syslog error message will indicate a resource conflict.
Port This is a cyclical field that lists the slot/port ID of the available destination
ports of the modules installed in the chassis. This field is only accessible
when the Type field is configured as Drop, Mgmt, or Imux. When you
have displayed the desired destination port, press [ENTER].
Type This is a fixed value that indicates the interface type (for example, V.35, or
RS530) of each port selected.
Rate This is a protected field that is automatically populated as connections are
made. It is equal to the number of timeslots dropped to this port multiplied
by the base rate (56 kbps or 64 kbps).
BYPASS The fields in this column are used to identify the destination link and
Column timeslot that will be connected to the link and timeslot currently being
configured.
Link This is a cyclical field that lists the link name and slot/link ID of the
available destination links of the modules installed in the chassis. When
you have displayed the desired destination link, press [ENTER].
TS This is an editable field containing two decimal digits (01 to 24 are valid
(Timeslot) for T1; 01 to 31 are valid for E1). It allows you to configure the destination
timeslot to which the timeslot being configured will be connected.
ConName This feature provides a 7 character connection name field assigned to DS0
(Connection Name) connections.

Configuration
Entering Connections
Bypass
Timeslot Select timeslot for editing using up/down keys or by typing in the desired
time slot number (using two digits)
Type Select Bpss using the N key then [ENTER].
Signaling Select desired signaling type for the DS0 (Rob or Clr if T1).
Destination Type in or use the N key to select the destination link, then [ENTER].
Timeslot Type in a two digit number (for example, 01) for the destination timeslot,
then [ENTER].
Drop
time slot number (using two digits
Type Select Drop by using N key, then [ENTER].
Destination Select the destination port using the N key. The Type and *Rate fields are
automatically populated.
*The more timeslots are added to a port, the higher the port rate becomes.
Entering Management (Mgmt) Connections

time slot number (using two digits
Type Select* Mgmt by using the N key, then [ENTER].
*Only one drop is allowed on a management port.
Copying Timeslots in the Connect Screen

Timeslot Select the desired timeslot to be copied. Press the C key and enter the last
timeslot to be copied. For example, to copy timeslots up to timeslot 24, type
C24.
All timeslots in between the selected timeslot and the destination timeslot
will be allocated the same as the original, incrementing the destination
timeslot by one.

Configuration
Using the Timeslot Screen
Using the Timeslot Screen

Use the Timeslot screen to configure the data code and signaling bit patterns that I (tImeslot)
the system will automatically send when the specified link is in an alarm state.
01 MASTER CARRIER ACCESS MASTERseries

------------------------------ your sysname here -------
Alarms sTat Diag pOrt Link tImeslot clK Connect coMmit
----- EDIT: NEW --------------------------------------
Name: Destination:
Frame: T1 ESF
TS Name DataCode ABCD/abcd
01 No TC No TC
02 NewYork No TC No TC
03 No TC No TC
04 No TC No TC
The following table describes the fields on the timeslot screen:

Timeslot Screen Definitions
Name This field allows you to name timeslots (DS0s).
DataCode This is a cyclical field that allows you to configure the trunk conditioning data
patterns to be transmitted on the specified timeslot when the link is in an alarm
state. The field cycles through the trunk conditioning patterns entered on the
trunk conditioning datacodes screen. When you have displayed the desired data
pattern, press [ENTER]. If No_TC parameter is selected then a default 7E
(hex) datacode will be sent.
ABCD/ This is a cyclical field which allows you to configure the trunk conditioning
abcd signaling bits to the transmitted on the specified timeslot when the link is in an
alarm state. The field cycles through the ABCD/abcd trunk conditioning
signaling bit patterns entered on the trunk conditioning signaling bits screen.
When you have displayed the required selection, press [ENTER]. If No_TC
parameters is selected then the incoming signaling bit pattern will be frozen
during alarm states.
After configuring the ABCD/abcd field, you must press [ENTER]. To escape to
the Link No. field, press [ESC] once. To escape to the main menu, press [ESC]
twice.

Configuration
Full Duplex Cross Connects
Full Duplex Cross Connects

This feature makes full duplex connections by automatically making the reverse connection for each
half duplex bypass connection specified in the connect screen. The full duplex connections are made
when you escape from the connect screen and the connections will overwrite or idle any previous
connections on the destination timeslot. The following figure shows a typical screen.

----- EDIT: NEW ------------------------------------------ RUN: CFG 1 -------
Name: Destination:
Frame: T1 ESF
IDLE <----- DROP -----> <--------- BYPASS --------->

01 Bpss Clr 1101 - - - - 1L03 01 LA
02 Bpss Clr 1101 - - - 1L04 02 NewYork
03 Idle Clr 1101 - - - - - - -

Configuration
Configuring APS for Link Failures

Use the automatic protection switching (APS) screen to configure how the system P (aPs)
responds to link failures. The system can be configured to perform an APS where an
alternative link is used as a backup for a failed link (red, blue/AIS or yellow alarm). APS provides the
ability to automatically reroute and/or vary link or channel parameters if a link fails or degrades below
user definable thresholds. When the failed link has been restored to service, the APS feature can be
configured to automatically return to the original configuration or remain on the switched configuration.

----- EDIT: CFG 4 ------------------------------------------ RUN: CFG 4 -----
LINK AUTOMATIC PROTECTION SETUP
CARD: 1
Link Config Ret

---- ------ ---
1 NO APS No
2 NO APS No
3 NO APS No
4 NO APS No
APS configurations cannot be nested (that is APS cannot protect against simultaneous multiple
failures). However, when an APS condition clears, the module scans links for alarms starting with link
1LA. If an alarm condition is found on another link configured for APS, then an APS switch will be
performed for that particular link. APS should not be used on G.761 links.
APS will NOT switch configurations under the following conditions:
If a link is already in alarm when it is configured for APS, no switch will occur when the
configuration is committed. An APS switch only occurs on the “transition” of a link from the
green state to the red alarm status.
The following table describes the fields on the APS screen:
APS Screen Definitions
RUN:CFG 16/1 Line four of each screen always displays the currently running
configuration (for example, RUN: CFG 1). When an APS switch occurs,
the display changes to show currently running CFG/previously running
CFG.
Example: RUN: CFG 16/1 indicates that an APS switch has occurred.
The configuration now running is 16 and the configuration that was
running before the APS was config 1).
Card This is a fixed field that lists the available slots in the chassis.

Configuration
APS Screen Definitions (Continued)

Link Conf This field lists the available configurations. From this list select the
(Link configuration to be used in the event of a link failure.
Configuration) NO APS—(default) Select NO APS (default) for no APS protection, then
[ENTER].
CFG 1 through CFG 16—In the event of a link failure, perform an
automatic protection switch to the specified configuration. The system will
not APS if you select the same configuration for APS as your running
configuration.
Use the N/P keys to select a configuration, then [ENTER].
Ret Select Yes to return to the original configuration when the link has returned
(Return) to normal. Then [ENTER].
Select No to remain in APS configuration.
The following figure shows a typical APS application.
Normal Operation—Network Link 1 carrying traffic to Port E and Link 4; Link 3 carrying traffic to Link 2
LINK 1 Fails—Port E switches to Link 2 and reduces traffic to Link 4; Reduces traffic to Link 3
LINK 2 Fails—Maintain Port E, Reduce traffic to Link 4; Reduce traffic to Link 3
RF Finger Printing MDIS
T1/E1
V.35 1 X 1 V.35
E E
T1/E1
2 X 2
Carrier Carrier
Access Access
4 3 3 4
T1/E1
AMPS Radio
T1/E1
T1/E1
DIGITAL Radio
Mobile Switch
CELL SITE MSO

Configuration
Password Management
Password Management
Use the passwords screen to manage the Superuser, Maintenance, and Telnet S (Setup)
passwords. You can define the passwords now or you can wait until later in the
P (Passwds)
configuration process. If you assign password protection now you will be prompted
for your new passwords many times during the configuration process.
In new FLEXmasters, the default passwords are set to blank fields (just press [ENTER]).

----- EDIT: NEW ------------------------------------------ RUN: CFG 1 -------
Password: New Pass: <--- SUPERUSER PASSWORD
Password: New Pass: <--- MAINTENANCE PASSWORD

Password: New Pass: <--- TELNET PASSWORD
The following table describes the fields on the passwords screen:

Passwords Screen Definitions
Superuser The Superuser password allows you to make configuration changes and
Password access status and diagnostic screens. This is a 12 character field. Press
[ENTER] to move to the New Pass field.
New This is a 12 character field. When you enter this field it first becomes a yes/no
Password field. If you do not want to enter a new password, answer no by pressing N. If
you would like to enter a new password, answer yes by pressing Y. This field
now turns into a 12 position editable field. Type the new password and press
[ENTER]. The field now turns into a field labeled Confirm. Re-enter the
new password for verification and press [ENTER].
Maintenance The maintenance password allows you to access the diagnostic screens, but
Password does not allow you to make any configuration changes. This is a 12 character
field. Press [ENTER] to move to the New Pass field.
Telnet A remote Telnet session to this system must be initiated using the password in
Password this field. This is a 12 character editable field. Press [ENTER] to move to the
New Pass field.

Configuration
Error Checking, Saving, and Activating the Configuration

Use the commit screen to error check and save the various configurations that you M (coMmit)
have created and to tell the system whether you want to activate a particular
configuration. This screen is also used to select the running configuration. There are
16 pre-named files to save your changes to: CFG 1 through CFG 16. The default is CFG 1.
The first thing that to look at in the commit screen is the indicator line. This is the line directly
underneath the menu. The left side of the indicator line indicates which configuration you are editing
(EDIT: CFG 2 in this example). The right side of the indicator line shows you which configuration you
are currently running (RUN: CFG 2 in this example).
You can copy an existing configuration file and save it under a new configuration ID. This allows you
to copy the existing configuration into a new one and then make changes as necessary. To make a
configuration copy, perform the following steps:
1. Go to the configuration screen.
2. Select the configuration number to be copied.
3. Go back to the commit screen.

----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 1 -------
Password:
NOTE: Current configuration is CFG 3

Save to: CFG 7
Save Now: Yes Activate now: No
4. In the Save to field select the new number for the configuration and press [ENTER].
5. Select Yes at the Save Now prompt and press [ENTER].
6. Select No at the Activate Now prompt and press [ENTER]. The copy is now complete.
NOTE: Make sure you know which configuration you need to update before saving it.
Once saved and/or activated, the system will not allow you to undo your changes. If there
are any diagnostic functions running, these will terminate upon activation. After making
changes to any of the screens, you must return to this screen and save and/or activate the
changes.

Configuration
The following table describes the fields on the commit screen:

Commit Screen Definitions
Password This is a 12 position editable field (superuser access is required). Type
your password and press [ENTER]. If the password is not entered
correctly, your changes will not be committed or saved.
Save To This is a cyclical field. When you have displayed the required selection,
press [ENTER].
CFG 1 through CFG 16 are valid selections.
Save Now This is a cyclical field. When you have displayed the required answer,
press [ENTER].
Yes—If you want to save the configuration currently being edited.
No—If you do not want to save the configuration currently being edited.
Activate now This is a cyclical field. When you have displayed the required answer,
press [ENTER].
Yes—If you want to activate the configuration currently being edited
No—If you do not want to activate the configuration currently being edited
If a commit fails, you will see the message: Commit failed Please see
Syslog for details. You will then see a prompt to cancel configuration
changes, answer yes or no to continue. If yes is selected, your edits will
revert back to the last saved configuration. If no is selected, an asterisk (*)
will appear next to the edit configuration number. This is the edit indicator.
The edit indicator is a visual reminder that the running configuration is
different from the edit configuration. The system event history (Syslog)
screen will indicate the reason for the commit failure. Once a commit has
been activated, the asterisk will be removed.
Using Save Versus Using CoMmit

In some configuration screens you are prompted to save your changes when you exit the screen.
This is like saving a memo that you have just typed using your word processor. If you answer yes
then your edits are written to memory and the changes take effect immediately. If you answer no
then your edits will automatically revert back to the last saved configuration.
The MASTERseries system also uses a commit screen where you can save and/or activate changes.
Changes saved under a commit do not take effect until you activate them. The following options
can be chosen:
Save Now: Yes, Activate now: Yes
When saving changes using the commit screen a series of error checks are completed before the
system allows the changes to be saved. If no errors are detected, the changes are activated
immediately.

Configuration
Save Now: No, Activate now: Yes

Changes are checked for errors and then activated without saving to memory. This can be used to
test a change before it is saved. The message Activated Table Not Saved will be temporarily
displayed in the lower right hand corner of the screen. Remember to save these changes if you want
to keep them. If you change configurations or the unit is power cycled before your changes are
saved they will be lost.
Save Now: Yes, Activate now: No
Changes are checked for errors and saved to memory without disruption to the running
configuration.
Save Now: No, Activate now: No
Edits will revert back to the last saved configuration.
If a configuration is saved and/or activated and it fails the error checking, then the message Cancel
changes now n/y? will be displayed. If you answer yes then changes are discarded. If you answer
no then you can view the errors in the syslog screen, correct the errors and commit again.
NOTE: The configuration that will run after a power cycle is the last configuration that was
saved and activated.
Commit failed Cancel configuration changes now?

If failed message appears, and you would like to start from the last good configuration, select Yes
when prompted to cancel changes, then [ENTER]. You can view the errors that occurred during
the activation on the system event history log screen.

Configuration
Configuring Links for Threshold Alarms
Configuring Links for Threshold Alarms

Use the threshold alarm screen to configure which links will signal an alarm when A (Alarms)
a specified level of unavailable/errored seconds is exceeded for links that have
performance monitoring enabled. Performance monitoring is enabled using the H (trHold)
Protocol field on the link screen menu.

----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
CARD: 1
Force link to RED: No
<---- UAS ---> <---- ES ----> <---- UAS ---> <---- ES ---->
Link State Thresh State Thresh Link State Thresh State Thresh
1 Disable Disable 9
2 Disable Disable 10
To set thresholds:
1. Select the card using the N/P keys, then [ENTER].
2. At Force Link to RED cycle between Yes and No, then [ENTER]. Select Yes if the link is
forced to a red alarm when a set error threshold is exceeded. Select No to log an exceeded
threshold as a minor alarm.
3. Select Enable or Disable, then [ENTER].
4. Type the amount of errored or unavailable seconds allowed before setting a threshold alarm.
5. Type the number of errored or unavailable seconds allowed during a 15-minute sliding window
before an alarm is declared for the specified link.
The following table describes the fields on the threshold alarm screen:
Threshold Screen Definitions
Card This is a cyclical field that contains the modules installed in the chassis. When
you have displayed the required card, press [ENTER].
Force Link to This is a cyclical field.
RED Yes—If you want the conditions configured in the UAS Threshold and ES
Threshold field below to force the link into red alarm state. This is very
effective if APS is being utilized.
No—If you want the conditions in the UAS Threshold and ES Threshold
field to force the link into a minor alarm state

Configuration
Configuring Minor Alarms
Threshold Screen Definitions (Continued)

Unavailable This is a cyclical field which configures whether or not unavailable seconds
Seconds (UAS) will generate an alarm.
(UAS) Enable—Triggers an alarm when the ES threshold is exceeded in a 15 minute
Threshold sliding window. A minor ES alarm is generated if Force link to RED is set to
(State) no. A major alarm is generated if Force link to RED is set to yes.
Disable—(default) UAS levels will not generate an alarm
Errored This is a cyclical field which configures whether or not errored seconds (ES)
Seconds (ES) will generate an alarm.
Threshold Enable—Triggers an alarm when the ES threshold is exceeded in a 15 minute
(State) sliding window. A minor ES alarm is generated if Force link to RED is set to
no. A major ES alarm is generated if Force link to RED is set to yes.
Disable—(default) ES levels will not generate an alarm.
Threshold This is a three digit editable field. Enter the number of errored seconds allowed
during a 15 minute sliding window before an alarm is declared for the specified
link.
Configuring Minor Alarms

This feature is not supported in release 4.02. A (Alarms)
M (Minor_def)

Configuration
Configuring the Idle Signaling Patterns
Configuring the Idle Signaling Patterns

Use the idle signaling patterns screen to define the ABCD idle signaling bit S (Setup)
patterns.
A (Abcd)

----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
ABCD signalling bit patterns:
1. 1101 2. ----
3. ---- 4. ----
5. ---- 6. ----
7. ---- 8. ----
The following table describes the fields on the idle signal patterns screen:
ABCD Screen Definitions
Password This is a 12 position editable field. Type your superuser password and press
[ENTER]. If the password is not entered correctly, read only access is
provided.
ABCD This area consists of two columns of editable fields that allow you to define
signaling Bit the ABCD idle signaling bit patterns. The idle signals defined here can be
Patterns assigned to any time slot on any link using the Abcd field on the connect
screen.

Configuration
Telnet Access to FLEXmaster
Telnet Access to FLEXmaster

01 MASTER CARRIER ACCESS MASTERseries TELNET Ver 4.02
Alarms sTat Diag pOrt Link tImeslot clK Connect coMmit aPs Setup Help Quit
----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------
<------- LINK -------> <- PORT -> <------- MGMT ------->
M T1 ABCD 111 1111 EFGH 111 1111
# S E1 MODULE TYPE 1234 5678 9012 3456 1 1234 5678 9012 3456
- - --------------- ---- ---- ---- ---- ---- ---- ---- ---- ----
2 -
3 -
4 -
5 -
6 -
7 -
8 -

Power Supply 2 Up

---------------------------------- GREEN ---------------------------------
Connect to the FLEXmaster using a Telnet TCP/IP application. The FLEXmaster must be connected
via Ethernet. The default IP address is 192.168.101.101. Login using the Telnet password.
To exit the telnet session, press Q for Quit. Q (Quit)
One Telnet session is allowed at a time. When the session is in use, another
user will get the message "Exceeding MAX CLI sessions" when they try to Telnet in.
If you exit out of the Telnet session unexpectedly (for example, by killing the window, or
keying control+C), no information is sent to the FLEXmaster to indcate that the client
terminated the session. The telnet timer will have to expire before the next Telnet session is
allowed.
When using HyperTerminal or Procomm Plus, the Telnet session will expire but the window
will remain open. Press [ENTER] to create a new Telnet session, and the Enter passes to the
Login prompt for a new session.

Configuration
Setting the System Name

Use the Sysname screen to create a custom system name. This name is displayed S (Setup)
on the second line of all screens.
G (mGmt)
S (Sysname)

----------------------------- Sample System Name ------------------------------
----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
To specify a system name:

1. To enter the screen, type the superuser password and press [ENTER].
2. Type a name for this module. Maximum length is 64 characters, including spaces.
3. Press [ESC] to exit this screen and save changes.

-------------------------------------------------------------------------------
Cli Sysname
----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
System Name : Sample System Name
Save: Yes
NOTE: This sysname is not related to the MIB II sysName object.

Configuration

CHAPTER
4
CLI Commands
In this Chapter
Accessing the CLI
Command Line Interface Help
CLI Command Modes
CLI Commands
Accessing the CLI
Accessing the CLI

S (Setup)
Select Setup > mGmt > CLI from the text user interface, and you will be placed in G (mGmt)
the root mode of the CLI.
C (CLI)

During a CLI session, help is available at any time.
? or help
Type a ? (or “help”) at any time for quick command information.
/# date?
Available commands :
[Syntax] : date [{MMDDHHmmYYYY.ss}]
[TAB] usage for word or command completion

Use [TAB] for command word completion:
/# sh [TAB]
/# show
Or type the first three characters or each section of a command, and the command will autocomplete
each word.
/1E1# shut
This command will be recognized as “shutdown”
CLI Command Syntax

The command syntax uses the following conventions:
Courier Font is used for command words
Curly Brackets { } enclose required parameters
Square Brackets [ ] enclose optional items
Vertical Rules | | | separate items in a list for which you must select only one item

CLI Commands
CLI navigation
The CLI is divided into a number of modes, including root mode. Use the commands below to move
through the CLI modes.
Mode: all
Syntax: /
Description: Returns prompt to root mode.

Example: /sntp# /
/#
Mode: all
Syntax: ../

Example: /sntp# ../
/#
Mode: all
Syntax: cd ..

Example: /rtm# ../
/#
Mode: all
Syntax: /{interface-name}/
Description: Change mode to an existing interface.

Example: /#
/# /1e1/
/1e1#
Mode: all
Syntax: exit
Description: Exits the CLI, returning you to the Text User Interface (TUI).
Example: /#exit

CLI Commands
CLI Command Modes
CLI Command Modes

For maneuverability through commands in this chapter, all command names in blue or italics are
hyperlinked.
Modes
all modes
root (# or /)
dhcp
dhcpc (DHCP Client)
dhcprelay (DHCP Relay)
Interface Commands Interface: ethernet
Interface: hdlc
Interface: ppp
ip
ppp
relay
resolver
rip
rtm
snmp
sntp
system

CLI Commands
all modes
Commands
all modes
The following are the commands that can be entered in ALL MODES. All commands listed below are
hyperlinked to the detailed definition of the command in this chapter.
• ?
• autoexit [timeout]
• cd {mode}
• clear
• clear key {key-string|all}
• date [MMDDHHmmYYYY.ss]
• end
• exit
• help [command]
• history
• key {key-string}
• ping {ip-address} [-n {count}] [-l {size}] [-w {timeout}] [-h {interface-address}]
• run script {script file} [output file]
• screen pause {on|off}
• show mode
• show running config
• show version
• traceroute {ip-address} [-m {max_ttl}] [-w {wait_time}]
Mode: all modes

Syntax: ?
Description: This command (help) can be used at any time, and at any level. The more of a command
that accompanies the ?, the more detailed the information is regarding the specific
command will be displayed.
Example: /sntp# clear ?
Available commands :
[Syntax] : clear
[Syntax] : clear key {key-string|all}
/sntp# clear

CLI Commands
all modes
Mode: all modes

Syntax: autoexit [timeout]
Description: This command displays the current autoexit setting in seconds. The timeout period can be
set by entering a new timeout value.
Example: /# autoexit
Current Session Timeout (in secs) = 1200
/# autoexit 900
Session Timeout set (in secs) to: 900
/# autoexit 0
Session Timeout disabled
Variable Definition
timeout A set timeout period, in seconds. A value of zero turns off the autoexit.
Range is 0-18000, default is 1200 seconds (20 minutes).
NOTE: Any changes made to the autoexit values are for the current session only. Default
values are restored with each new session. Autoexit does not affect the TUI.
Mode: all modes

Syntax: cd {mode}
Description: To change to a different mode or interface.

Example: /# cd 1e1
/1e1#
/ip# cd /sntp
/sntp#
Variable Definition
mode A mode or interface. Options are:
dhcp, dhcp_client, dhcp_relay, interface, ip, ppp, relay, resolver, rip,
root, rtm, snmp, sntp, system.
Interface Options: ethernet, ppp, hdlc.
Mode: all modes

Syntax: clear
Description: To clear all previous commands displayed on the window.

Example: /# clear

CLI Commands
all modes
Mode: all modes

Syntax: clear key {key-string|all}
Description: This command disables the specific keyed features associated with the software key, or
disable all the keyed features.
Example: /# clear key cxusdfutkj3diosn412CDFslkjf098iwjflsk
Write FACT OK
Successfully Cleared Features
*Need Reset to Realign the Features
/#
Variable Definition
key-string A key string associated with a feature, up to 64 characters long.
Mode: all modes

Syntax: date [MMDDHHmmYYYY.ss]
Description: This command displays current date if a date value is not given. If date command is given
with a value, it will set the given date as described in the syntax.
Example: /# date
SAT AUG 28 21:23:53 1999
/#
/# date 121716582004.43
/# date
FRI DEC 17 16:58:44 2004
Mode: all modes

Syntax: end
Description: Ends current mode and returns to the root directory.

Example: /# cd rtm
/rtm# end
/#

CLI Commands
all modes
Mode: all modes

Syntax: exit
Description: This command exits the current session and returns the user to the TUI (text user
interface).
Example: /# exit
Mode: all modes

Syntax: help [command]
Description: To get help for a particular command. When help or ? is typed in the required mode, all
commands present in that mode as well as all general commands will be listed.
Example: /dhcprelay# ?
dhcprelay trace {Hex value: Pattern 0xAB}
rai-option-control {enable|disable}
server {ip address}
servers-only {enable|disable}
state {enable|disable}
Description: When a help is followed by a keyword, all possible commands starting from that keyword
are displayed.
Example: /1E1# help testing
[Syntax] : testing
Description : Bring the interface in testing mode
/1E1#
Description: When help is needed for a specific command, enter the command within quotes along
with the word help.
Example: /# help "show eth stats"
[Syntax] : show eth stats {interface-name}
Description : Display Ethernet interface statistics
Description: When an abbreviation is used in the help string, all matching commands are listed with
the description.
Example: /# help "sh dh ex add"
[Syntax] : show dhcpsrv exclude addresses
Description : Display exclude IP addresses from each pool

CLI Commands
all modes
Mode: all modes

Syntax: history
Description: Displays the command list history by listing the last 15 commands given by the user.
Example: /# history
1 history
2 cd 1e2
3 ip address dhcp
4 traceroute 10.10.2.49
5 history
6 cd dhcp
7 list options
8 history
/dhcp#
Execute an already given command by looking at the history

and then using ! {command-number}
Example: /# !6
/dhcp#
Mode: all modes

Syntax: key {key-string}
Description: This command enters a feature key, whereby a specific feature is enabled on the unit.
Example: /# key cxusdfutkj3diosn412CDFslkjf098iwjflsk
Write FACT OK
Successfully Set Features
*Need Reset to Realign the Features
Variable Definition
key-string A key string associated with feature, up to 64 characters long.

CLI Commands
all modes
Mode: all modes

Syntax: ping {ip-address} [-n {count}] [-l {size}] [-w {timeout}]
[-h {interface-address}]
Description: This command Pings from the Router to the specified host. Send a message to a host
machine/switch using the IP address.
Example: /# ping 192.168.1.3
Reply Received From : 192.168.1.3, TimeTaken : 0.20 msecs
--- 192.168.1.3 Ping Statistics ---
3 Packets Transmitted, 3 Packets Received, 0% Packets Loss
Example: /# ping 192.168.1.3 -n 1 -l 1200

--- 192.168.1.3 Ping Statistics ---
1 Packet Transmitted, 1 Packet Received, 0% Packets Loss
Variable Definition
ip-address IP address of the host to ping.
-n {count} Specifies the number of ping requests to be sent. Range 1-
1000.
-l {size} Specifies the size of the ping requests packets to be sent.
Range 0-2080.
-w {timeout} Specifies the time to wait for a response before sending the
next ping request packet. Timeout is given in seconds.
Range 1-100. Default is 2 seconds.
-h {interface-address} Local host interface IP address.

CLI Commands
all modes
Mode: all modes

Syntax: run script {script file} [output file]
Description: Run CLI commands from a specified script file. The output of the commands prints to the
console.
To create a script file, type the commands in a text file. Use the file-download
command to load the script to the local flash.
Example: /system# file-download commands.txt ipaddr 192.168.1.158
Downloading commands.txt from 192.168.1.158
.
Download Complete
/system#
/system# run script commands.txt
/system# show mode
SYSTEM : system
/system# cd /
/# show int config all
Index Name IfaceType MTU AdminStatus OperStatus EncapType

----- ----- --------- --- ----------- ---------- ---------
1 1E1 ENET 1500 Up Up Ethernet V2
2 1E2 ENET 1500 Down Down Ethernet V2
3 1M1 HDLC 1504 Down Down Other
5 1X1 PPP 1500 Down Down PPP
Variable Definition
script file File which has the CLI commands.
output file unsupported
Mode: all modes

Syntax: screen pause {on|off}
Description: This command enables/disables the screen pause. Screen pause enables the "more"
prompt for large screen output. It is enabled by default.
Example: /# screen pause off

CLI Commands
all modes
Mode: all modes

Syntax: show mode
Description: Displays the available modes. When executed inside a mode, will display current mode.
Example: /# cd ip
/ip# show mode
IP: ip
/# show mode
ROOT : /
SNTP : sntp
RESOLVER : resolver
RELAY : relay
SYSTEM : system
INTERFACE : <slot#><E|M|X><interface#>
IP : ip
RTM : rtm
PPP : ppp
DHCP_RELAY : dhcprelay
DHCP : dhcp
DHCP_CLIENT : dhcpc
RIP : rip
SNMP : snmp

CLI Commands
all modes
Mode: all modes

Syntax: show running config
Description: Displays the major configuration that is in effect on the router. It shows all the show
commands for various features and interfaces. It does not show statistics.
Example: /# show running-config
INTERFACE CONFIGURATION -- Summary

----- ----- --------- --- ----------- ---------- ---------
ETHERNET INTERFACES CONFIGURATION
Interface Configuration
-----------------------
Interface Index : 1
Interface Name : 1E1
Encapsulation Type : Ethernet V2
MTU : 1500
Admin Status : Up
Operational Status : Up
Auto Negotiation : Enabled
Ethernet Link Status : 100 full-duplex
MAC Address : 00:e0:97:10:95:ea

CLI Commands
all modes
Mode: all modes

Syntax: show version
Description: This command displays the version for the hardware, software and firmware in the
FLEXmaster. The Manager level user will be provided with more information than
Operator and User levels. Software features are listed along with enabled status.
Example: /# show version
Equipment Versions:
BootCode Version:
FPGA Revision: 0.00
CPU: WinPath 747 Rev A.0
DPS version: 0X10001112
BSP: Winpath/MIPS5Kc
Product Features:
T1x4 - T1 Enabled
HDLCx4 - HDLC Enabled
High Performance Routing - HPR Enabled
Mode: all modes

Syntax: traceroute {ip-address} [-m {max_ttl}] [-w {wait_time}]
Description: This command will trace the route to the destination.

Example: /# traceroute 10.10.8.1 -m 8
Variable Definition
ip-address IP address of the destination host.
-m {max_ttl} The maximum number of hops to trace. Range 1-30, default is 15
-w {wait_time} Defines the time to wait for a response before sending the next
probe packet. Timeout is given in seconds. Range 1-100, default is
1 second.

CLI Commands
root
root
The following are the commands under the ROOT mode. All commands listed below are hyperlinked
to the detailed definition of the command in this chapter.
• delete interface {interface-name}

• interface {interface-name}
• show arp cache
• show arp config
• show arp stats
• show dhcp relay info
• show dhcpclnt config
• show dhcpclnt stats
• show dhcpsrv bindings
• show dhcpsrv boot config
• show dhcpsrv config
• show dhcpsrv exclude addresses
• show dhcpsrv global options
• show dhcpsrv global stats
• show dhcpsrv host options
• show dhcpsrv pools
• show dhcpsrv subnet options
• show eth stats {interface-name}
• show icmp config
• show icmp stats
• show inarp stats
• show interface config {all|interface-name}
• show interface stats {interface-name}
• show ip global config
• show ip interface [interface-name]
• show ip path mtu
• show ip traffic
• show login authentication
• show rarp config
• show rarp stats
• show rip config
• show rip interface stats
• show rip stats

CLI Commands
root
• show route
• show rrd deny routes
• show rrd permit routes
• show rtm config
• show snmp-community config
• show snmp-trap config
Mode: root
Syntax: delete interface {interface-name}
Description: Removes a logical interface from the provisioning.

Example: /# delete interface 1X1
Variable Definition
interface-name Name of the interface
Mode: root
Syntax: interface {interface-name}
Description: Create the specified interface and change mode into the interface provisioning mode for
the specified interface. If the interface has already been created, the mode will change to
be the interface provisioning mode of the specified interface.
Example: /# interface 1X1
/1X1#
Variable Definition
interface-name E = Ethernet Port
M = Serial (HDLC)
X = PPP Interface
For more information about interface naming, see Interface Identifiers on page 3-5.

CLI Commands
root
Mode: root
Syntax: show arp cache
Description: Displays the Address Resolution Protocol (ARP) cache information.

Example: /# show arp cache
IP Address to Physical Address Mapping
Iface IP Address Physical Address Mapping

1M1 192.168.1.1 00.d4.71.47.ac.d0 Static
1M1 192.168.1.1 00.d4.71.47.ac.d0 Static
Mode: root
Syntax: show arp config
Description: Displays the Address Resolution Protocol (ARP) configuration information.

Example: /# show arp config
ARP Global Configuration

Cache Timeout : 7200 secs
Pending Timeout : 30 secs
ARP Max Retries : 10
IP ARP Proxy : Disabled
Mode: root
Syntax: show arp stats
Description: Displays the Address Resolution Protocol (ARP) statistics.

Example: /# show arp stats
ARP Statistics
Received
Total ARP Packets Received : 112
Total ARP Packets Discarded: 15
Number of ARP Requests Received: 48
Number of ARP Responses Received: 59
Sent
Number of ARP Requests Transmitted: 57
Number of ARP Responses Transmitted: 35

CLI Commands
root
Mode: root
Syntax: show dhcp relay info
Description: Displays the DHCP Relay configuration information.

Example: /# show dhcp relay info
DHCP Relay Information

DHCP Relay: Enabled
DHCP Relay Servers only: Enabled
Server IP Address: 10.0.0.27
DHCP Relay RAI option: Enabled
Trace Level: 0x1
No of Packets inserted RAI option: 0
No of Packets inserted circuit ID suboption: 0
No of Packets inserted remote ID suboption: 0
No of Packets inserted subnet mask suboption: 0
No of Packets dropped: 0
No of Packets which did not insert RAI option: 0
Mode: root
Syntax: show dhcpclnt config
Description: Displays the DHCP Client Configuration.

Example: /# show dhcpclnt config
DHCP Client Configurations
PortNum Renew Rebind Inform Release Trace

0 disabled disabled disabled disabled None

CLI Commands
root
Mode: root
Syntax: show dhcpclnt stats
Description: Displays the General statistics of DHCP Client.

Example: /# show dhcpclnt stats
DHCP Client Counter Table

Count Discovers: 2
Count Requests: 0
Count Releases: 0
Count Declines: 0
Count Informs: 0
Count Offers: 0
Count Acks in Req state: 0
Count Nacks in Req state: 0
Count Acks in Renew state: 0
Count Nacks in Renew state: 0
Count Acks in Rebind state: 0
Count Nacks in Rebind state: 0
Count Acks in Reboot state: 0
Count Nacks in Reboot state: 0
Count Error in header: 0
Count Error in Xid: 0
Count Error in Options: 0
Client IP Address: 0.0.0.0
Client Lease Time: 0
Counter Reset: 0
Mode: root
Syntax: show dhcpsrv bindings
Description: Displays the server bindings with the clients (that is, the IP addresses assigned to clients
are displayed).
Example: /# show dhcpsrv bindings
DHCP Server Current Bindings
IPHwHw alloc ExpireBinding

AddressTypeAddressMethodTimeState
192.168.1.27Ethernet00.8b.c3.f4.23.c0Dynamic00:01:00Assigned

CLI Commands
root
Mode: root
Syntax: show dhcpsrv boot config
Description: Displays the Boot Server configuration.

Example: /# show dhcpsrv boot config
DHCP Boot Server Configuration
Boot-SupportAuto_BootpServer-AddrBootp-File
DisabledEnabled10.7.5.23file1
Mode: root
Syntax: show dhcpsrv config
Description: Displays the DHCP Server configuration.

Example: /# show dhcpsrv config
DHCP Server Configuration

Server Status:Disable
Server ICMP Echo:Disable
Server Address Reuse Timeout:60
Trace Level:None
Mode: root
Syntax: show dhcpsrv exclude addresses
Description: Displays the exclude IP Addresses from each pool.

Example: /# show dhcpsrv exclude addresses
DHCP Server Exclude Addresses
PoolIndexStartIpAddressEndIpAddress
110.0.0.1510.0.0.25

CLI Commands
root
Mode: root
Syntax: show dhcpsrv global options
Description: This command displays the DHCP Server options. Note: The DHCP Server provides a
framework for passing configuration information to hosts on a TCP/IP network.
Configuration parameters and other control information are carried in tagged data items
that are stored in the “options” field of the DHCP message.
Example: /# show dhcpsrv global options
DHCP Global Options Table
TypeLengthValue
ROUTER4 255.0.0.0
IP Forwarding1 1
Mode: root
Syntax: show dhcpsrv global stats
Description: This command displays the DHCP Server statistics.

Example: /# show dhcpsrv global stats
DHCP Server Global Statistics

Num of Discovers received: 0
Num of Requests received: 0
Num of Releases received: 0
Num of Informs received: 0
Num of Invalids received: 0
Num of Offers sent: 0

Num of ACKs sent: 0
Num of NACKs sent: 0
Num of Declines sent: 0
Num of Packets dropped due to unknown client: 0

Num of Packets dropped due to invalid subnet: 0

CLI Commands
root
Mode: root
Syntax: show dhcpsrv host options
Description: Displays options for a specific client.

Example: /# show dhcpsrv host options
DHCP Server Host Options
PoolIdHostTypeClientIdentifierOptTypeOptLenOptValue
1100.ae.16.93.f3.51IP Forwarding10
1100.la.09.48.2b.11ROUTER4255.255.255.0
Mode: root
Syntax: show dhcpsrv pools
Description: This command displays the DHCP Server pool network configuration.
Example: /# show dhcpsrv pools
DHCP Server Pool Configuration
Pool IDPortNumSubnetSubnetMaskStartIPAddrEndIPAddrLeaseTime
1eth#210.0.0.0255.0.0.010.0.0.1010.0.0.1001:00:00
Mode: root
Syntax: show dhcpsrv subnet options
Description: This command displays the DHCP Server subnet options.

Example: /# show dhcpsrv subnet options
DHCP Server Subnet Option Configuration

PoolOptionOptionOption
IndexTypeLengthValue
1Subnet Mask4 255.0.0.0
1IP Forwarding10

CLI Commands
root
Mode: root
Syntax: show eth stats {interface-name}
Description: Displays the interface statistics for the specified Ethernet interface.
Example: /# show eth stats 1E2
1E2 Interface Statistics
Alignment Errors : 0
Frame Checksum Errors : 0
Single Collision Frames : 0
Multiple Collision Frames : 0
SQE Test Errors : 0
Deferred Transmissions : 0
Late Collisions : 0
Excessive Collisions : 0
Internal MAC Tx Errors : 0
Carrier Sense Errors : 0
Frames Too Long : 0
Internal MAC Rx Errors : 0
Symbol Errors : 0
Duplex Status : 10Base-T full-duplex
MAC Address : 00:e0:97:10:95:eb
Variable Definition
interface-name Name of Ethernet Interface to display.
Mode: root
Syntax: show icmp config
Description: Displays Internet Control Message Protocol (ICMP) configuration information.

Example: /# show icmp config
ICMP Global Configuration

Send Redirect : Enabled
Send Unreachable : Enabled
Send Echo Reply : Enabled
Net Mask Reply : Enabled
Timestamp Reply : Enabled
Direct Query : Disabled
Send Security Failure : Enabled
Recv Security Failure : Enabled

CLI Commands
root
Mode: root
Syntax: show icmp stats
Description: Displays Internet Control Message Protocol (ICMP) statistics.

Example: /# show icmp stats
Received:
total: 16
checksum errors: 0 unreachable: 1 redirects: 0
time exceeded: 0 param problems: 0 quench: 0
echo: 0 echo reply: 0 timestamp: 0
timestamp reply: 0 mask req: 0 mask reply: 0
domain name req: 0 domain name reply: 0 security failure: 0
Sent:
total: 10670
checksum errors: 0 unreachable: 10670 redirects:0
time exceeded: 0 param problems: 0 quench:0
echo: 0 echo reply: 0 timestamp 0
timestamp reply: 0 mask req: 0 mask reply:0
domain name req: 0 domain name reply:0 security failure: 0
Mode: root
Syntax: show inarp stats
Description: Displays the InARP statistics.

Example: /# show inarp stats
InARP Statistics
Received
Total InARP Packets Received : 0
InARP Replies Received : 0
Invalid InARP Requests Received: 0
Sent
Total InARP Packets Sent : 0
InARP Replies Sent : 0
InARP Requests Not Got Reply : 0

CLI Commands
root
Mode: root
Syntax: show interface config {all|interface-name}
Description: Shows interface configurations for all or specific Interface according to user input.
Example: >show interface config 1E1
-----------------------
Interface Index : 1
MTU : 1500
Admin Status : Up
Auto Negotiation : Enabled
Ethernet Link Status : 100 full-duplex
MAC Address : 00:e0:97:10:95:7e
Variable Definition
all Displays all the interfaces
interface-name A specific interface name. Example: 1E1, 1M1.

CLI Commands
root
Mode: root
Syntax: show interface stats {interface-name}
Description: Displays interface statistics of specified interfaces.

Example: /# show interface stats 1E2
1E2 Interface Statistics
Received
Octets : 0
Unicast Packets : 0
Discarded Packets : 0
Multicast Packets : 0
Broadcast Packets : 0
Transmitted
Octets : 1680
Unicast Packets : 0
Discarded Packets : 0
Multicast Packets : 28
Broadcast Packets : 0
Variable Definition
interface-name A specific interface name. Example 1E1, 1M1.
Mode: root
Syntax: show ip global config
Description: Displays the IP Global configuration.

Example: /# show ip global config
Global IP Configuration
IP Forwarding : Enabled
Default TTL : 64
Route Cache Age : 180 secs
IP Options Processing : Enabled
Path MTU Discovery : Disabled
Path MTU entry age : 10 min
Reassembly Queue Depth : 32
Maximum Static Routes : 25
Maximum Number Of Fragments : 128
Trace level : 0

CLI Commands
root
Mode: root
Syntax: show ip interface [interface-name]
Description: Shows all ip interfaces or specific interface.

/# show ip interface
IP Interface Configuration
---------------------------
Interface Index : 100
Interface Type : ENET
Interface Admin Status : Up
Interface Oper Status : Up
IP Address : 10.6.4.211
Subnet Mask : 255.255.255.0
Broadcast Address : 10.6.4.255
Address Allocation : Manual
Interface MTU : 1500
MAC Address : 00:e0:97:10:92:c0
NAT Address Domain : Local
/# show ip interface 1E1
1E1 IP Interface Configuration

--------------------------------
Interface Index : 1
IP Address : 10.40.107.30
Subnet Mask : 255.255.0.0
MAC Address : 00:E0:97:00:10:91
Auto Negotiation Status : Enabled
Variable Definition
interface-name Name or index of interface.

CLI Commands
root
Mode: root
Syntax: show ip path mtu
Description: Displays the Path Maximum Transmission Unit (MTU) table.

Example: /# show ip path mtu
IP Path MTU Table
DestinationType ofPathPath MTUEntry

AddressServiceMTUDiscoveryStatus
10.0.0.201200 EnabledACTIVE
20.0.0.201500 Enabled
Mode: root
Syntax: show ip traffic
Description: Displays the IP Traffic information.

Example: /# show ip traffic
IP Statistics:
Received:
Total IP Packets Received: 35817, IP Header Errors Discards: 0
Bad IP Address Discards: 0, Unsupported Protocol Discards: 1571
Bad IP Header Length Discards: 0, Discards For Checksum errors: 0
Version error Discards: 0, TTL error Discards: 0
Bad options Discards: 0 Successfully Received 35817
Fragmented:
Reassembled Packets: 0, Reassembly Timeout: 15
Packets Needs Reassembly: 0, Packets Fragmented: 0
Cannot Fragment : 0
Broadcast:
Total Broadcasts Received: 34130
Sent:
Packets to Forward : 0, Generated Requests : 10441
Discards Due To No Routes: 2, Discards Due To General Errors: 0
Mode: root
Syntax: show login authentication
Description: Displays current authentication method. For FLEXmaster 4.02, this will be LOCAL
Example: /# show login auth
Login authentication mode: LOCAL

CLI Commands
root
Mode: root
Syntax: show rarp config
Description: Displays Reverse Address Resolution Protocol (RARP) configuration.

Example: /# show rarp config
Rarp Configurations:
mode: client
retries: 4
entries: 20
timeout: 100
Mode: root
Syntax: show rarp stats
Description: Displays Reverse Address Resolution Protocol (RARP) statistics.

Example: /# show rarp stats
Rarp Statistics:
requests discarded: 0
responses discarded: 0
Mode: root
Syntax: show rip config
Description: Displays RIP configuration.

Example: /# show rip config
RIP Global Configuration

RIP2 Security : MAX
Max Peers : 25
Spacing : Disabled
Retransmit Interval (Sec) : 5
Redistribution : Disabled

CLI Commands
root
Mode: root
Syntax: show rip interface stats
Description: Displays RIP global statistics.

Example: /# show rip interface stats
RIP Interface Stats
IP BadPkts BadRoutes Trig Upd RIP

Address Received Received Sent Admin Status
-------- ------- --------- -------- --------
10.10.2.88 0 0 0 DISABLED
Mode: root
Syntax: show rip stats
Description: Displays RIP global statistics.

Example: /# show rip stats
RIP Global Stats

----------------
Route Changes : 0
Response Sent : 0
Packets Dropped : 0
Mode: root
Syntax: show route
Description: Displays the IP routing table information.

Example: /# show route
Codes: St - Route Status, UA - Up and Active, UI - Up and Inactive, Dn - Down
DestinationGenmaskGatewayProtoIfaceMetricPrefToSSt
192.168.2.0255.255.255.00.0.0.0local1E110 A
Mode: root
Syntax: show rrd deny routes
Description: Displays the entries created by the rrd permit commands (rtm mode).
Example: /# show rrd permit routes
Rrd total control table is empty

CLI Commands
root
Mode: root
Syntax: show rrd permit routes
Description: Displays the entries created by the rrd deny commands (rtm mode).
Example: /# show rrd deny routes
Rrd total control table is empty
Mode: root
Syntax: show rtm config
Description: Displays rtm settings.

Example: /# show rtm config
RTM Configuration
--------------------------------
Status : Enabled
AS No : 0
Router Id : 11.1.4.6
Mode: root
Syntax: show snmp-community config
Description: Displays SNMP community configurations.
Example: /# show snmp-community config
SNMP Community Details

Community Index: 1
Community Name:NETMAN
IP Address:10.0.6.204
Privilege Type: readonly
Mode: root
Syntax: show snmp-trap config
Description: Displays SNMP trap configurations.
Example: /# show snmp-trap config
SNMP Trap Manager Details

SNMP Index: 1
Community:PUBLIC
IP Address:10.0.6.204
Manager Type: V1V2

CLI Commands
dhcp
dhcp
The following are the commands under the DHCP mode. All commands listed below are hyperlinked
• add pool {pool index} {port name/index} {subnet} {mask} {start ip} {end ip}
• boot server {ip-address} {file name}
• delete binding {ip-address}
• delete pool {pool index}
• dhcp trace {all|events|packets|failure|bind|none}
• exclude pool {pool index} {start ipaddr} {end ipaddr}
• global option {type} {len} {val}
• host option {pool index} {host type} {host id} {option type} {len} {val}
• icmp echo enable
• lease time {pool-id} {value}
• list options
• no global option {type}
• no host option {pool index} {host type} {host id} {option type}
• no icmp echo
• no service dhcp
• no subnet option {pool index} {type}
• remove exclude pool {pool index} {start ip}
• server addr timeout {value}
• service dhcp
• subnet option {pool index} {type} {len} {val}

CLI Commands
dhcp
Mode: dhcp
Syntax: add pool {pool index} {port name/index} {subnet} {mask}
{start ip} {end ip}
Description: This command is used to define a pool of addresses that will be allocated by the DHCP
server on a network. A maximum of 6 entries can be made in a pool.
Example: /# cd dhcp
/dhcp# add pool 1 1E2 10.0.0.0 255.0.0.0 10.0.0.1 10.0.0.20
Variable Definition
pool index An integer value that uniquely identifies an address pool
port name/index Specify interface
subnet Specify the network to be used
mask Specify the network to be used
start ip Starting IP address present in the pool
end ip Ending IP address present in the pool
Mode: dhcp
Syntax: boot server {ip-address} {file name}
Description: This command is used to configure the Boot Server information. The boot server file must
be in the base directory of the tftp server.
Example: /dhcp# boot server 10.10.12.45 bootinfo.txt
Variable Definition
ip-address Indicates the IP address of the next boot server
file name The file name indicates the boot server file name terminated with a
null string
Mode: dhcp
Syntax: delete binding {ip-address}
Description: The DHCP server binds an IP address to a host / PC when the IP address is allocated to
the host. This IP address binding is deleted when the host fails to renew the IP address
after timeout. The bindings can also be deleted manually using the above command.
Example: /# cd dhcp
/dhcp# delete binding 10.10.0.10
Variable Definition
ip-address The IP address of the host whose bindings by the server to a PC/host
is to be deleted.

CLI Commands
dhcp
Mode: dhcp
Syntax: delete pool {pool index}
Description: This command removes DHCP server subnet pool.

Example: /# cd dhcp
/dhcp# delete pool 1
Variable Definition
pool index Enter existing pool-index of pool to delete.
Mode: dhcp
Syntax: dhcp trace {all|events|packets|failure|bind|none}
Description: Sets the debug level for tracing DHCP module.

/# cd dhcp
/dhcp# dhcp trace all
Variable Definition
all Traces all below.
events Traces DHCP events.
packets Traces packets.
failure Traces failures.
bind Traces all the bindings.
none Turns off all DHCP traces.
Mode: dhcp
Syntax: exclude pool {pool index} {start ipaddr} {end ipaddr}
Description: This command is used to exclude a set of IP addresses from being assigned to any hosts/
PC on the network. This command is used when there is a host or a set of hosts for which
the IP addresses are assigned statically. A large range of addresses can be configured for
the network and the hosts with static IP addresses can be excluded from the address range.
Example: /# cd dhcp
/dhcp# exclude pool 1 10.0.0.10 10.0.0.20
Variable Definition
start ipaddr Starting IP address present in the pool
end ipaddr Ending IP address present in the pool

CLI Commands
dhcp
Mode: dhcp
Syntax: global option {type} {len} {val}
Description: Set global options used by DHCP server. Global options are applicable for all subnets
(that is, all networks). DHCP server will send these options to all DHCP clients as a part
of the response message.
Example: /# cd dhcp
/dhcp# global option 3 4 198.162.1.254
Variable Definition
type Indicates the option type. Range is 1-76
len Indicates length of the value (in bytes). Range is 16-60 bytes.
val Specifies the actual option value.
Mode: dhcp
Syntax: host option {pool index} {host type} {host id} {option type}
{len} {val}
Description: This command is used to statically assign a specific IP address to a host.
Example: /# cd dhcp
/dhcp# host option 1 1 00.a0.eb.00.00.01 1 20 192.168.1.4
Variable Definition
pool index Specifies the DHCP address pool that the hosts belong to.
host type Specifies the if the Host ID is a MAC address or a string
1 = MAC address
2 = a string is given as an input
host id A MAC address or string which uniquely identifies the host pool
option type Indicates the option type.
len Indicates length of the value (in bytes)
val Specifies the actual option value

CLI Commands
dhcp
Mode: dhcp
Syntax: icmp echo enable
Description: This command enables ICMP echo mechanism in the DHCP server. The DHCP Server
Module checks the network for an IP address before allocating the IP address to the user.
This is done by sending ICMP (ping) packets with the selected IP address. If no response
is received then the IP address is assumed to be unique (no other host has the IP address
in the home network) and the address is allocated to a host.
Example: /# cd dhcp
/dhcp# icmp echo enable
Mode: dhcp
Syntax: lease time {pool-id} {value}
Description: Configures the DHCP subnet lease time period for a particular Pool ID.
Example: /# cd dhcp
/dhcp# lease time 1 20
Variable Definition
pool-id Indicates the specific subnet or address pool
value Indicates the lease time period in seconds. Range is 1-7200, with a
default of 3600.

CLI Commands
dhcp
Mode: dhcp
Syntax: list options
Description: This command displays the global as well as the subnet specific options that are used by
the DHCP server in response to a DHCP DISCOVER.
Example: /# cd dhcp
/dhcp# list options
----------------------------------------------------------------
RFC-2132 DHCP Options List | Configuration using FlexMaster CLI
----------------------------------------------------------------
Option Name | Type | Length | Example (assumed pool-id =1)
| | | <pool-id> <type> <len> <val>
----------------------------------------------------------------
Subnet Mask | 1 | 4 | 1 1 4 255.0.0.0
Time Offset | 2 | 4 | 1 2 4 3600
Def-Router | 3 | 4 | 1 3 4 10.0.0.254
Time Server | 4 | 4 | 1 4 4 10.0.0.1
Name Server | 5 | 4 | 1 5 4 10.0.0.2
DNS Server | 6 | 4 | 1 6 4 10.0.0.3
Log Server | 7 | 4 | 1 7 4 10.0.0.4
Cookie Server | 8 | 4 | 1 8 4 10.0.0.5
LPR Server | 9 | 4 | 1 9 4 10.0.0.6
Impress Server | 10 | 4 | 1 10 4 10.0.0.7
Resource Loc Server | 11 | 4 | 1 11 4 10.0.0.8
Host Name | 12 | 17** | 1 12 20 host1
Merit Dump File | 14 | 12** | 1 14 20 filename
Domain Name | 15 | 17** | 1 15 20 carrieraccess.com
Swap Server | 16 | 4 | 1 16 4 10.0.0.9
Root Path | 17 | 12** | 1 17 20 rootpath
Extensions Path | 18 | 12** | 1 18 20 extpath
IP Forwarding | 19 | 1 | 1 19 1 1
Non-Local Routing | 20 | 1 | 1 20 1 1
Policy Filter | 21 | 8 | 1 21 8 10.0.0.10 255.0.0.0
Data Reassembly size| 22 | 2 | 1 22 2 10
Default TTL | 23 | 1 | 1 23 1 1
MTU Aging Timeout | 24 | 4 | 1 24 4 3600
Path MTU Plateau | 25 | 2 | 1 25 2 10
Interface MTU | 26 | 2 | 1 26 2 10
All Subnets Local | 27 | 1 | 1 27 1 1
Broadcast Address | 28 | 4 | 1 28 4 10.255.255.255
Mask Discovery | 29 | 1 | 1 29 1 1
Mask Supplier | 30 | 1 | 1 30 1 1
Router Discovery | 31 | 1 | 1 31 1 1
Rtr Solicitation Adr| 32 | 4 | 1 32 4 10.0.0.11
Static Route | 33 | 8 | 1 33 8 10.0.0.12 10.0.0.13
Trailer Encp | 34 | 1 | 1 34 1 1
ARP Cache Timeout | 35 | 4 | 1 35 4 90
Ethernet Encp | 36 | 1 | 1 36 1 1
Tcp Default TTL | 37 | 1 | 1 37 1 1
Tcp Keepalive Int | 38 | 4 | 1 38 4 90
Tcp KpAlive Garbage | 39 | 1 | 1 39 1 1
NIS DNS Name | 40 | 17** | 1 40 20 carrieraccess.com
NIS Server IP | 41 | 4 | 1 41 4 10.0.0.14

CLI Commands
dhcp
NTP Server IP | 42 | 4 | 1 42 4 10.0.0.15

NETBIOS NS | 44 | 4 | 1 44 4 10.0.0.16
NETBIOS Datagram | 45 | 4 | 1 45 4 10.0.0.17
NETBIOS Node | 46 | 1 | 1 46 1 2 4 8
NETBIOS Scope | 47 | 4 | 1 47 4 10.0.0.18
X Font Server | 48 | 4 | 1 48 4 10.0.0.19
X Display Manager | 49 | 4 | 1 49 4 10.0.0.20
Client Identifier | 61 | 2 | 1 61 2 10
NIS+ Domain | 64 | 12** | 1 64 1 domainname
NIS+ Server IP | 65 | 4 | 1 65 4 10.0.0.22
TFTP Server Name | 66 | 12** | 1 66 1 servername
Bootfile Name | 67 | 12** | 1 67 1 bootfile
Mobile IP Home Agent| 68 | 4 | 1 68 4 10.0.0.23
SMTP Server | 69 | 4 | 1 69 4 10.0.0.24
POP3 Server | 70 | 4 | 1 70 4 10.0.0.25
NNTP Server | 71 | 4 | 1 71 4 10.0.0.26
WWW Server | 72 | 4 | 1 72 4 10.0.0.27
Finger Server | 73 | 4 | 1 73 4 10.0.0.28
IRC Server | 74 | 4 | 1 74 4 10.0.0.29
Street Server | 75 | 4 | 1 75 4 10.0.0.30
**Variable length
Mode: dhcp
Syntax: no global option {type}
Description: Remove global options used by DHCP server for the specified option type. Use list
options command to view DHCP options list.
Example: /# cd dhcp
/dhcp# no global option 8
Variable Definition
type Enter an existing option to be removed.

CLI Commands
dhcp
Mode: dhcp
Syntax: no host option {pool index} {host type} {host id}
{option type}
Description: Removes the DHCP server host options used by the DHCP server.
Example: /# cd dhcp
/dhcp# no host option 1 1 00.a0.eb.00.00.01 1
Variable Definition
pool index Specifies the DHCP address pool that the hosts belong to.
host type Specifies the if the Host ID is a MAC address or a string
1 = MAC address
2 = a string is given as an input
host id A MAC address or string which uniquely identifies the host pool
option type Enter an existing option to be removed.
Mode: dhcp
Syntax: no icmp echo
Description: This command disables ICMP echo mechanism in DHCP server. The DHCP server
module will not perform the ping test described above for uniqueness of IP address before
allocating the same to a host.
Example: /# cd dhcp
/dhcp# no icmp echo
Mode: dhcp
Syntax: no service dhcp
Description: This command disables the DHCP Server on the system.

Example: /# cd dhcp
/dhcp# no service dhcp

CLI Commands
dhcp
Mode: dhcp
Syntax: no subnet option {pool index} {type}
Description: This command is used to delete a configured subnet option.

Example: /# cd dhcp
/dhcp# no subnet option 1 3
Variable Definition
pool index An integer value that uniquely identifies the subnet
type Enter an existing option to be removed.
Mode: dhcp
Syntax: remove exclude pool {pool index} {start ip}
Description: This command is used to delete the configured exclude address pool. DHCP server will
start assigning all addresses in the address pool range. Take care to ensure there are no
PCs/workstations with static IP addresses that fall within the address pool.
Example: /# cd dhcp
/dhcp# remove exclude pool 1 10.0.0.10
Variable Definition
start ip Starting IP address present in the pool
Mode: dhcp
Syntax: server addr timeout {value}
Description: This command sets the DHCP server offer reuser timer.
Example: /# cd dhcp
/dhcp# server addr timeout 3600
Variable Definition
value Specify address timeout value. If the DHCP client does not send a
request for renewal of IP address, the IP address is returned back to the
free pool.
value is in seconds. Do not set this time to a very low value. This
value should be greater than the time taken by the host for renewal of
the IP address.

CLI Commands
dhcp
Mode: dhcp
Syntax: service dhcp
Description: This command enables the DHCP Server on the system.

Example: /# cd dhcp
/dhcp# service dhcp
Mode: dhcp
Syntax: subnet option {pool index} {type} {len} {val}
Description: Subnet options are applicable only to a specific IP subnet/address pool (for example, a
network). The pool index field identifies the specific subnet or address pool. Subnet
options are assigned to all PC/workstations on the network along with global options.
Example: /# cd dhcp
/dhcp# subnet option 1 3 5 192.168.1.50
Variable Definition
pool index An integer value that uniquely identifies the subnet
type Indicates the option type
len Indicates length of the value (in bytes)
val Specifies the actual option value.

CLI Commands
dhcpc (DHCP Client)
dhcpc (DHCP Client)

The following command is under the DHCP CLIENT mode. All commands listed below are
Mode: dhcpc
Syntax: dhcpc trace {all|events|packets|failure|bind|none}
Description: Sets the debug level for tracing DHCP Client module.
Example: /# cd dhcpc
/dhcpc# dhcpc trace all
Variable Definition
all Traces all below.
events Traces DHCP Client events.
packets Traces packets.
failure Traces failures.
bind Traces bindings.
none Turns off all DHCP traces.

CLI Commands

The following are the commands under the DHCP RELAY mode. All commands listed below are
• dhcprelay trace {Hex value}

• rai-option-control {enable|disable}
• server {ip-address}
• servers-only {enable|disable}
• state {enable|disable}
Mode: dhcprelay
Syntax: dhcprelay trace {Hex value}
Description: Configures DHCP relay trace options.

Example: /# cd dhcprelay
/dhcprelay# trace 0x0
Variable Definition
Hex value Pattern 0xAB
turn on the entire trace value 0xff
turn off the trace 0x0
initialization/shutdown activity 0x01
for OS resource usage 0x020
for failure conditions 0x040
Mode: dhcprelay
Syntax: rai-option-control {enable|disable}
Description: This command enable and disables Relay Agent Information (RAI) option control. Only
when enabled, the Relay Agent will process the related to Relay Agent Information
options. For example: inserting the necessary options while relaying a packet from a
client to a server and examining/stripping of options when relaying a packet from a server
to a client. The default is Disabled.
/dhcprelay# rai-option-control enable

CLI Commands
Mode: dhcprelay
Syntax: server {ip-address}
Description: Configures the IP address of the DHCP server to which the Relay Agent needs to forward
the packets from the client.
/dhcprelay# server 10.0.0.37
Variable Definition
ip-address IP address of the DHCP Server to which the Relay Agent needs to
forward the packets from the client.
Mode: dhcprelay
Syntax: servers-only {enable|disable}
Description: When enabled the Relay Agent shall forward the packets from the client to a specific
DHCP server. The default is Disabled.
/dhcprelay# server-only enable
Mode: dhcprelay
Syntax: state {enable|disable}
Description: This command enables and disables Relay Agent Information option control. Only when
enabled, the Relay Agent will process the related to Relay Agent Information Options -
like inserting the necessary options while relaying a packet from a client to a server and
examining/stripping of options when relaying a packet from a server to a client.
/dhcprelay# state enable
Variable Definition
enable Enables the DHCPC relay protocol.
disable Disables the DHCPC relay protocol.

CLI Commands
Interface Commands
Interface Commands
Mode: root
Syntax: interface {interface-name}
Description: Create the specified interface and change mode into the interface provisioning mode for
the specified interface. If the interface has already been created, the mode will change to
be the interface provisioning mode of the specified interface.
The interfaces that are physically present and key enabled are created at system start up.
This means that the user does not have to execute the "interface" command to create a
physical interface. Logical interfaces such as PPP will need to be created with the
"interface" command before the interface may be provisioned. If the interface is not a
physical interface, the interface will be created and then CLI enters into the provisioning
mode of the specified interface.
Physical interfaces/modules that have been physically removed from a FLEXmaster shall
not be provisionable and shall not be displayed to the user. An example is a module that
has been removed. The removed interfaces will not be visible to the user from CLI or
SNMP.
The software feature keys also affect the availability of the physical interfaces. If the
customer purchases the use of only two of the eight DS1s present in the FLEXmaster,
only two of the DS1 interfaces will be displayed. The user will not be allowed to use the
interface command to create 1L3 or 1L4 in this case.
Up to 8 PPP interfaces are allowed. Allowable names <slot>X1 up to <slot>X16.
After an interface has been created, the cd command may be used with the interface name
as a path to enter into the specified interface provisioning mode. For more information
about navigating in the CLI, see CLI navigation on page 4-3.
Interface types
Description Representation Example

Ethernet Port <slot number>E(1-2) 1E2
Serial (HDLC) <slot>M(1-2) 1M1
PPP interface. <slot>X(1-16) 1X6
8 PPP interfaces are allowed, but
allowable names range from
<slot>X1 to <slot).X16.
For more information about interface naming, see Interface Identifiers on page 3-5.

CLI Commands
Interface: ethernet
Interface: ethernet
The following are the commands under the INTERFACE: ethernet mode. All commands listed below
are hyperlinked to the detailed definition of the command in this chapter.
• address alloc {manual|negotiated|dynamic}

• authentication {ip-address} {none|simple|md5} [key {key-string}]
• autoneg {enable}
• autoneg force {10|100} {halfduplex|fullduplex}
• cost {ip-address} {value}
• delete interval [ip-address] {time}
• encapsulation {llcSnap(6)|enetV2(8)}
• ip config {ip-address} [mask {subnet mask}] [secondary] [global|local]
• ip rip [ip-address] enable
• ip rip [ip-address] split-horizon {1-enable| 2-poison-reverse|3-disable}
• no ip config {sec_ip_addr}
• no ip rip [ip-address]
• no shutdown
• recv [ip-address] {rip1|rip2|both|none}
• route age [ip-address] {time}
• send [ip-address] {rip1|ripv1compatible|rip2|v1|v2|none}
• show rip interface [ip-address] config
• shutdown
• testing
• update interval [ip-address] {time}

CLI Commands
Interface: ethernet
Mode: interface: ethernet

Syntax: address alloc {manual|negotiated|dynamic}
Description: Sets the address allocation method for the interface. Defaults to manual if the "ip config"
command is entered.
Example: /# interface ethernet 1E1
/1E1# address alloc dynamic
Variable Definition
dynamic The interface address will be obtained dynamically
manual The address for the interface is to be statically assigned
negotiated The interface address will be negotiated

Syntax: authentication {ip-address} {none|simple|md5}
[key {key-string}]
Description: Set type of RIP authentication used on the interface.
Example: /# int 1E1
/1E1# authentication 10.1.2.3 simple key 342
Variable Definition
ip-address IP address of the interface
none No authentication needed
simple Simple authentication method
md5 MD5 based authentication
key-string Optional parameter. Authentication key

Syntax: autoneg {enable}
Description: Enables auto-negotiation.

Example: /1e1# autoneg enable

CLI Commands
Interface: ethernet

Syntax: autoneg force {10|100} {halfduplex|fullduplex}
Description: This command will force the Ethernet interface to autonegotiate at the defined settings.
Example: /1E1# autoneg admin force 100 fullduplex
Variable Definition
force Force to specified parameters
10 10 MHz
100 100 MHz
halfduplex Half-duplex is transmission in both directions, but not at the same
time.
Fullduplex Full-duplex is transmission in both directions simultaneously.

Syntax: cost {ip-address} {value}
Description: Set RIP default metric.

Example: /# int 1E1
/1E1# cost 10.1.2.3 10
Variable Definition
ip-address IP address of the RIP interface.
value Value of the RIP default metric. Range is 0-6.

Syntax: delete interval [ip-address] {time}
Description: Set the interval before deleting a RIP entry after not hearing it.
Example: /# int 1e1
/1e1# delete interval 10.1.2.3 150
Variable Definition
ip-address IP address of the interface.
time A set interval time between RIP updates in seconds. Range is
120-180 seconds.

CLI Commands
Interface: ethernet

Syntax: encapsulation {llcSnap(6)|enetV2(8)}
Description: This command sets the encapsulation type for the interface.
Example: /# interface 1E1
/1E1# encapsulation 6
# interface 1E1
/1E1# encapsulation 8
Variable Definition
llcSnap (6) Logical Link Control and Sub-Network Attachment Point
Encapsulation.
enetV2(8) Ethernet V2 Encapsulation.

Syntax: ip config {ip-address} [mask {subnet mask}] [secondary]
[global|local]
Description: Set the IP address, subnet mask and broadcast address for the interface.
/1E2# ip config 192.168.1.3 mask 255.255.255.0
Variable Definition
subnet mask Subnet mask for the IP address. If not specified the default address
mask will be assumed.
secondary Indicates this as the secondary IP address. A maximum of 8
secondary addresses can be specified.
global|local The designation of local or global for an interface is used only for
NAT. It indicates that the interface uses either private (local)
addresses or public (global) interfaces. The local or global
designation is ignored when adding secondary addresses.
"Local" is the default for Ethernet and "global" is the default for
WAN links.

CLI Commands
Interface: ethernet

Syntax: ip rip [ip-address] enable
Description: Accept RIP packets on the specified IP interface.

Example: /# int 1E1
/1E1# ip rip 10.1.2.3 enable
Variable Definition

Syntax: ip rip [ip-address] split-horizon {1-enable|
2-poison-reverse|3-disable}
Description: Set split-horizon mode.
Example: /# int 1E1
/1E1# ip rip 10.1.2.3 split-horizon 1-enable
Variable Definition
ip address IP address of the interface
1-enable Enable split-horizon mode
2-poison-reverse Enable poison reverse mode
3-disable Disable both split-horizon and poison reverse

Syntax: no ip config {sec_ip_addr}
Description: Removes the given secondary IP address.

/1E1# no ip config 10.4.6.100
Variable Definition
sec_ip_addr Secondary IP address to remove.

CLI Commands
Interface: ethernet

Syntax: no ip rip [ip-address]
Description: Reject RIP packets on the specified IP interface.

Example: /# int 1E1
/1E1# no ip rip 10.1.2.3
Variable Definition

Syntax: no shutdown
Description: This command will set the designated Ethernet interface as In-Service.
/1E1# no shutdown
/1E2# cd ..
/# show int conf 1E1
Interface Index : 1
MTU : 1500
Admin Status : Up
Operational Status : Down
Auto Negotiation Status : 100 full-duplex
MAC Address : 00:e0:97:10:92:c0

Syntax: recv [ip-address] {rip1|rip2|both|none}
Description: Set RIP receive version method on the interface. Note that this command cannot be issued
until RIP is enabled on the subnet, see the ip rip [ip-address] enable command.
Example: /# int 1E1
/1E1# recv 10.1.2.3 rip2
Variable Definition
rip1 Implies receiving RIP updates compliant with RFC 1058
rip2 Implies receiving multicasting rip2 updates
both Implies receiving both rip1 and rip2
none None of the above

CLI Commands
Interface: ethernet

Syntax: route age [ip-address] {time}
Description: Set time after which the entry is put into garbage collect interval.
Example: /# int 1E1
/1E1# route age 10.1.2.3 200
Variable Definition
time Time after which the RIP route entry is put into the garbage collect
interval on the given interface. Default is 180 seconds. Range is from
1-3600.

Syntax: send [ip-address] {rip1|ripv1compatible|rip2|v1|v2|none}
Description: Set RIP send version method on the interface. Note that this command cannot be issued
Example: /# int 1E1
/1E1# send 10.1.2.3 rip2
Variable Definition
ripv1compatible Implies broadcasting rip2 updates using RFC 1058 route sub
assumption rules
v1 Indicates the use of demand RIP on a WAN interface under
ripversion1rules
ripversion2rules
none Set RIP send version to none.

CLI Commands
Interface: ethernet

Syntax: show rip interface [ip-address] config
Description: Displays RIP provisioning.

Example: /# int 1E1
/1E1# show rip interface 10.1.2.3 config
RIP Interface Configuration

Config Address: 11.11.11.1
Authentication:
Type: None
Key :
RIP Version:
Send : RIP Version2
Receive: RipVersion1 Or RipVersion2
Cost: 1
RIP State: Enabled Admin Status: Up Operational State: Up
Timer Intervals:
Update every : 30 seconds
Garbage collect after: 120 seconds
Route age out after : 180 seconds
Split Horizon Status : Poison Reverse

Syntax: shutdown
Description: This command will set the designated Ethernet interface as Out-of-Service.
/1E1# shutdown
/1E1# exit
/# show int conf 1E1
Interface Index : 1
MTU : 1500
Admin Status : Down
Operational Status : Down
Auto Negotiation Status : 100 full-duplex
MAC Address : 00:e0:97:10:92:c0

CLI Commands
Interface: ethernet

Syntax: testing
Description: Bring the interface into testing mode. The administrative state of the Ethernet interface is
set to “testing”, no operational packets are handled. Any packet received on the interface
is discarded while in testing.
/1E1# testing

Syntax: update interval [ip-address] {time}
Description: Set the interval time between RIP updates.

Example: /# int 1E1
/1E1# update interval 10.1.2.3 45
Variable Definition
time Interval time between RIP updates in seconds. Valid range is 10-3600
seconds.

CLI Commands
Interface: hdlc
Interface: hdlc
The following are the commands under the INTERFACE: hdlc mode. All commands listed below are
• no shutdown
• shutdown
• testing
Mode: interface: hdlc

Syntax: no shutdown
Description: This command will set the designated interface as In-Service.

Example: /# int 1M1
/1M1# no shutdown

Syntax: shutdown
Description: This command will set the designated interface as Out-of-Service.

Example: /# int 1M1
/1M1# shutdown
/1M1# exit

Syntax: testing
Description: Bring the interface into testing mode. The administrative state of the hdlc interface is set
to “testing”, no operational packets are handled. Any packet received on the interface is
discarded while in testing.
Example: /# interface 1m1
/1M1# testing

CLI Commands
Interface: ppp
Interface: ppp
The following are the commands under the INTERFACE: PPP mode. All commands listed below are
• address alloc {manual|negotiated|dynamic}

• authentication [ip-address] {none|simple|md5} [key {key-string}]
• authentication {PAP|CHAP} {user-name} {passwd} {Secret ID} {RemoteToLocal|
LocalToRemote}
• cost [ip-address] {value}
• delete interval [ip-address] {time}
• ip config {ip-address} [mask {subnet mask}] [global|local]
• ip rip [ip-address] enable
• ip rip [ip-address] split-horizon {1-enable|2-poison-reverse|3-disable}
• keep-alive-timer {timer-value}
• lqr enable {timeout}
• magic number
• no authentication {Secret ID}
• no ip rip [ip-address]
• no keep-alive-timer
• no lqr
• no magic number
• no shutdown
• recv [ip-address] {rip1|rip2|both|none}
• route age {ip-address} {time}
• send [ip-address] {rip1|ripv1compatible|rip2|v1|v2|none}
• show rip interface {ip-address} config
• show stackinterface {ppp interface-name}
• shutdown
• stackinterface {interface-name}
• testing
• unstackinterface {interface-name}
• update interval [ip-address] {time}

CLI Commands
Interface: ppp
Mode: interface: ppp

Syntax: address alloc {manual|negotiated|dynamic}
Description: Determine the method that IP address is set for this interface. Defaults to manual if the "ip
config" command is entered.
Example: /1X2# address alloc negotiated
/1X2# cd ..
/# show ip interface 1x2
1X2 IP Interface Configuration

--------------------------------
Interface Index : 6
IP Address : 0.0.0.0
IP Directed Broadcast : Disabled
Max Reassembly Size : 65535
Address Allocation : Negotiated
NAT Address Domain : None
Variable Definition
dynamic The interface address will be obtained dynamically
manual The address for the interface is to be statically assigned
negotiated The interface address will be negotiated

Syntax: authentication [ip-address] {none|simple|md5}
[key {key-string}]
Description: Set type of authentication used on the interface.
Example: /# int ppp 1X1
/1X1# authentication 10.2.2.1 simple key 342
Variable Definition
none No authentication needed
simple Simple authentication method
md5 Md5 based authentication
key-string Authentication key

CLI Commands
Interface: ppp

Syntax: authentication {PAP|CHAP} {user-name} {passwd} {Secret ID}
{RemoteToLocal|LocalToRemote}
Description: Chooses CHAP or PAP as authentication protocol for the PPP or MLPP link. By default
no authentication is configured.
/1X1# authentication CHAP cacs passwd cacs id 1
Enter Link Config Host Name:
Variable Definition
PAP Selects PAP as authentication protocol
CHAP Selects CHAP as authentication protocol
user-name Define a user name.
passwd Enter password here.
Secret ID Enter secret ID index.
RemoteToLocal Defines direction of authentication as Remote to Local
LocalToRemote Defines direction of authentication as Local to Remote. Default.

Syntax: cost [ip-address] {value}
Description: Set RIP default metric.

Example: /# int 1x1
/1x1# cost 10.1.2.3 10
Variable Definition
ip-address IP address of the RIP interface.
value Value of the RIP default metric. Range is 0-6.

CLI Commands
Interface: ppp

Syntax: delete interval [ip-address] {time}
Description: Set the interval before deleting a RIP entry after not hearing it.
Example: /# int 1x1
/1x1# delete interval 10.1.2.3 150
Variable Definition
time A set interval time between RIP updates in seconds. Range is 120-
180 seconds.

Syntax: ip config {ip-address} [mask {subnet mask}] [global|local]
Description: Set the IP address and subnet mask for the interface.
Example: /# interface 1x2
/1x2# ip config 192.168.1.3 mask 255.255.255.0
Variable Definition
subnet-mask Subnet mask for the IP address. If not specified the default address
mask will be assumed.
global|local The designation of local or global for an interface is used only for
NAT. It indicates that the interface uses either private (local)
addresses or public (global) interfaces. The local or global
designation is ingnored when adding secondary addresses.
"Local" is the default for Ethernet and "global" is the default for
WAN links.

Syntax: ip rip [ip-address] enable
Description: Accept RIP packets on the specified IP interface.

Example: /# int 1x1
/1x1# ip rip 10.1.2.3 enable
Variable Definition

CLI Commands
Interface: ppp

Syntax: ip rip [ip-address] split-horizon {1-enable|2-poison-
reverse|3-disable}
Description: Set split-horizon mode.
Example: /# int 1x1
/1x1# ip rip 10.1.2.3 split-horizon 1
Variable Definition
1-enable Enable split-horizon mode
2-poison-reverse Enable poison reverse mode
3-disable Disable both split-horizon and poison reverse

Syntax: keep-alive-timer {timer-value}
Description: Sets the period for the LCP echo request packets or a "keep alive" test on the link.
Example: /1x2# keep-alive-timer 15
Variable Definition
timer-value The range is 10 to 300 seconds.

Syntax: lqr enable {timeout}
Description: Sets PPP Link Quality Reporting (LQR) status and the reporting period for the link. By
default LQR negotiation is disabled.
/1X1# lqr enable 100
Variable Definition
timeout The LQR Reporting period that the local PPP entity will attempt to
negotiate with the remote entity, in units of hundredths of a second.
Changing this object will take effect when the link is next restarted.

CLI Commands
Interface: ppp

Syntax: magic number
Description: Enables PPP Magic Number negotiation on PPP link. By default no Magic Number
negotiation is done.
/1X1# magic number

Syntax: no authentication {Secret ID}
Description: Removes authentication protocol for the PPP link.

/1X1# no authentication 1
Variable Definition
Secret ID Specify the secret ID index.
Mode: interface:ppp
Syntax: no keep-alive-timer
Description: Disables the keep alive timer.

Example: /1X1# no keep-alive-timer

Syntax: no lqr
Description: Disable PPP Link Quality Reporting (LQR) negotiation for the PPP link.
/1X1# no lqr

Syntax: no magic number
Description: Disables PPP Magic Number negotiation on PPP link.

/1X1# no magic number

CLI Commands
Interface: ppp

Syntax: no ip rip [ip-address]
Description: Reject RIP packets on the specified IP interface.

Example: /# int 1x1
/1x1# no ip rip 10.1.2.3
Variable Definition

Syntax: no shutdown
Description: This command will set the designated ppp interface as In-Service.
/1x1# no shutdown
/1x1# cd ..
/# show interface config 1x1
-----------------------
Interface Index : 5
Interface Name : 1X1
Encapsulation Type : PPP
MTU : 1500
Admin Status : Up
NOTE: if you issue the "no shutdown" command on a PPP interface before configuring
an IP address, this will make it an un-numbered PPP interface.

CLI Commands
Interface: ppp

Syntax: recv [ip-address] {rip1|rip2|both|none}
Description: Set RIP receive version method on the interface. Note that this command cannot be issued
Example: /# int 1x1
/1x1# recv 10.1.2.3 rip2
Variable Definition
both Implies receiving both rip1 and rip2
none None of the above

Syntax: route age {ip-address} {time}
Description: Set time after which the entry is put into garbage collect interval.
Example: /# int 1x1
/1x1# route age 10.1.2.3 200
Variable Definition
time Time after which the RIP route entry is put into the garbage collect
interval on the given interface. Default is 180 seconds. Range is from
1-3600.

CLI Commands
Interface: ppp

Syntax: send [ip-address] {rip1|ripv1compatible|rip2|v1|v2|none}
Description: Set RIP send version method on the interface. Note that this command cannot be issued
Example: /# int 1x1
/1x1# send 10.1.2.3 rip2
Variable Definition
ripv1compatible Implies broadcasting rip2 updates using RFC 1058 route sub
assumption rules
ripversion1rules
ripversion2rules
none Set RIP send version to none.

CLI Commands
Interface: ppp

Syntax: show rip interface {ip-address} config
Description: Displays RIP provisioning.

Example: /# int 1x1
/1x1# show rip interface 10.1.2.3 config
/# cd 1x1
/1x1# show rip interface config
RIP Interface Configuration
Config Address: 11.11.11.1
Authentication:
Type: None
Key :
RIP Version:
Send : RIP Version2
Receive: RipVersion1 Or RipVersion2
Cost: 1
RIP State: Enabled Admin Status: Up Operational State: Up
Timer Intervals:
Update every : 30 seconds
Garbage collect after: 120 seconds
Route age out after : 180 seconds
Split Horizon Status : Poison Reverse
Variable Definition

Syntax: show stackinterface {ppp interface-name}
Description: Displays the stack interface information.

/1X1# show stackinterface 1X1
Stack interface for ppp: 1m2
Variable Definition
ppp interface-name Enter a defined PPP interface name.

CLI Commands
Interface: ppp

Syntax: shutdown
Description: This command will set the designated ppp interface as Out-of-Service.
/1x2# shutdown
/1x2# exit
/# show interface config 1x2
-----------------------
Interface Index : 6
Encapsulation Type : PPP
MTU : 1500
Admin Status : Up
Operational Status : Other

CLI Commands
Interface: ppp

Syntax: stackinterface {interface-name}
Description: This command stacks a PPP interface over a physical interface. Configuration of the PPP
interface is permitted only after this command. All other interface parameters are
configurable only after stackinterface command.
/1x1# no shutdown
/1x1# cd ..
/# cd 1x2
/1x2# shutdown
/1x2# unstackinterface 1x2
Cannot unstack the interface: Admin status should be down
for Lower Layer
/1x2# cd ..
/# interface 1m2
/1M2# shutdown
/1M2# cd ..
/# interface 1x2
/1X2# unstackinterface 1x2
Successfully unstacked the PPP interface

/1X2# stackinterface 1m2
Please enable the port before adding the link.
/1X2# cd ..
/# interface 1m2
/1M2# no shutdown
/1M2# cd ..
/# interface 1x2
/1X2# stackinterface 1m2
Layering successful
Variable Definition
interface-name Interface to stack.

CLI Commands
Interface: ppp

Syntax: testing
Description: Bring the interface into testing mode. The administrative state of the Ethernet interface is
set to “testing”, no operational packets are handled. Any packet received on the interface
is discarded while in testing.
/1x1# testing

Syntax: unstackinterface {interface-name}
Description: This command will remove a stacked interface.

/1X1# unstackinterface 1X1
Variable Definition
interface-name Interface to stack.

Syntax: update interval [ip-address] {time}
Description: Set the interval time between RIP updates.

Example: /# int 1x1
/1x1# update interval 10.1.2.3 45
Variable Definition
time Interval time between RIP updates in seconds. Valid range is 10-3600
seconds.

CLI Commands
ip
ip
The following are the commands under the IP mode. All commands listed below are hyperlinked to the
detailed definition of the command in this chapter.
• arp add {phys-address} {ip-address} {interface-name}

• arp max retries {value}
• arp timeout {secs}
• icmp send echo reply
• ip aggregate route {value}
• ip default ttl {value }
• ip directed broadcast {interface-name}
• ip forwarding
• ip fragments {value}
• ip path mtu {dest ip} {tos} {mtu}
• ip path mtu age {mins}
• ip path mtu discover
• ip process option
• ip proxy arp
• ip reassembly {n} [size {value} {interface-name}]
• ip redirects
• ip route add {dest ip-addr} [mask {dest mask}] {next hop} [metric {metric}]
• ip route age {ageout}
• ip route del {dest ip-addr} [dest mask] {next hop| interface-name}
• ip unreachables
• no arp {ip-address} {interface-name}
• no icmp send echo reply
• no ip directed broadcast {interface-name}
• no ip forwarding
• no ip path mtu {dest-ip} {ToS}
• no ip path mtu discover
• no ip process option
• no ip proxy arp
• no ip redirects
• no ip unreachables
• rarp add {hw-address} {ip-address}
• rarp del {hw-address}
• rarp disable
• rarp server [entries]

CLI Commands
ip
Mode: ip
Syntax: arp add {phys-address} {ip-address} {interface-name}
Description: Adds an ARP entry in the arp cache. This entry is permanent and does not have a timeout.
It can be deleted manually.
Example: /# cd ip
/ip# arp add 00:9e:4c:57:82:6f 192.168.111.35 1X1
Variable Definition
phys address Physical address of the interface
ip address IP address of the interface
interface name/index Name of Interface
Mode: ip
Syntax: arp max retries {value}
Description: This command specifies the maximum number of retry attempts before aborting ARP
resolving.
Example: /# cd ip
/ip# arp max retries 10
Variable Definition
value The maximum number of retries. Range is 2-10.
Mode: ip
Syntax: arp timeout {secs}
Description: This command specifies the time after which the entry in ARP cache is to be deleted.
Example: /# cd ip
/ip# arp timeout 7500
Variable Definition
secs Range is 30-86400 seconds. Default is 7200.

CLI Commands
ip
Mode: ip
Syntax: icmp send echo reply
Description: This command enables sending of ICMP echo replies for the incoming ICMP echo
requests.
Example: /# cd ip
/ip# icmp send echo reply
Mode: ip
Syntax: ip aggregate route {value}
Description: This command specifies the maximum number of aggregated routes that can be
configured in the system.
Example: /# cd ip
/ip# ip aggregate route 12
Variable Definition
value The number of aggregated routes that can be configured on the
router. Range is 5-499, default is 10 routes
Mode: ip
Syntax: ip default ttl {value}
Description: This command is used to set the default Time-To-Live (TTL) parameter for IP packets in
seconds.
Example: /# cd ip
/ip# ip default ttl 80
Variable Definition
value Range is 1-255.

CLI Commands
ip
Mode: ip
Syntax: ip directed broadcast {interface-name}
Description: This command enables IP directed broadcast forwarding on the given interface.
Example: /# cd ip
/ip# ip directed broadcast 1E1
Variable Definition
interface-name Interface on which the directed broadcast forwarding
is to be enabled.
Mode: ip
Syntax: ip forwarding
Description: Enables IP forwarding on all interfaces of the router. When this option is enabled, IP
packets are forwarded if required to the destination. IP forwarding is enabled by default.
Example: /# cd ip
/ip# ip forwarding
Mode: ip
Syntax: ip fragments {value}
Description: This command specifies the number of IP datagrams that can be allowed in a single
reassembly.
Example: /# cd ip
/ip# ip fragments 132
Variable Definition
value Number of IP datagrams that can be allowed in a single reassembly.
Range is 1-301, default is 10 datagrams.

CLI Commands
ip
Mode: ip
Syntax: ip path mtu {dest ip} {tos} {mtu}
Description: This command sets the Path MTU and TOS of the path for a given destination IP address.
Example: /# cd ip
/ip# ip path mtu 10.0.0.2 0 1200
Variable Definition
dest ip Destination IP address of the new route
tos Type of Service value. Range 0-255.
mtu Maximum transmission unit value. Range is 68-65535.
Mode: ip
Syntax: ip path mtu age {mins}
Description: This command specifies the timeout, after which the estimate of a PMTU is considered
stale. After the configured time the estimate of the PMTU is increased. When set to
infinity (255), detection in increase of PMTU is not done.
Example: /# cd ip
/ip# ip path mtu age 10
Variable Definition
mins Specifies the path MTU entry age time. Range is 5-255 minutes.
Default is 10.
Mode: ip
Syntax: ip path mtu discover
Description: This command enables path MTU discovery on all paths.

Example: /# cd ip
/ip# ip path mtu discover
Mode: ip
Syntax: ip process option
Description: Enables processing of the IP options in the received IP packets.

Example: /# cd ip
/ip# ip process option

CLI Commands
ip
Mode: ip
Syntax: ip proxy arp
Description: This command is used to enable proxy ARP.

Example: /# cd ip
/ip# ip proxy arp
Mode: ip
Syntax: ip reassembly {n} [size {value} {interface-name}]
Description: This command is used to specify the number of IP datagrams awaiting for reassembly and
the maximum size of the fragmented IP datagrams received on the specified interface.
Example: /# cd ip
/ip# ip reassembly 5 size 2000 1E1
Variable Definition
n Number of IP datagrams awaiting for reassembly. Range is 1-150.
value The maximum size of the fragmented IP datagram received on the
interface that can be considered for reassembly.
Range is 1024-33280.
interface-name Specify Interface.

CLI Commands
ip
Mode: ip
Syntax: ip redirects
Description: This command enables sending of ICMP redirect messages.

Example: /# cd ip
/ip# ip redirects
NOTE: Even if ICMP redirects are enabled, ICMP redirect messages may not be sent.
When there is a cached entry for the next hop already present in the data plane
coprocessor, the packets will be forwarded at wire speed by the data plane coprocessor
and no ICMP redirect message will be sent. Note that this will only happen when the
firewall is disabled and the data plane already knows the MAC address of the next hop.
However, if the control plane processor handles the packet, ICMP redirects will be sent as
usual, such as when an ARP request must be generated for the next hop.
Mode: ip
Syntax: ip route add {dest ip-addr} [mask {dest mask}] {next hop}
[metric {metric}]
Description: This command adds a route in the routing table for a given destination.
Example: /# cd ip
/ip# ip route add 101.255.0.0 mask 255.255.0.0 1X2 1
Variable Definition
dest ip-addr Destination IP address of the new route
dest mask Subnet Mask of the Destination IP address
next hop IP address of the next hop host to reach route
metric The metric value is the "cost" of the route. May be used as number
of hops to that destination but could also be given a larger value to
indicate a slower link therefore a less desirable route to choose.
Used in comparison to other routes to determine the smallest cost
of getting to the same destination
NOTE: On an un-numbered PPP interface you should specify the interface name instead
of the next hop address (since you can't specify 0.0.0.0 as a valid next hop).

CLI Commands
ip
Mode: ip
Syntax: ip route age {ageout}
Description: This command is used to set the ageout time after which an IP route will be deleted.
Example: /# cd ip
/ip# ip route age 200
Variable Definition
ageout Range is 1-3600 seconds. Default is 180.
Mode: ip
Syntax: ip route del {dest ip-addr} [dest mask] {next hop|
interface-name}
Description: This command deletes the route for a given destination from the routing table.
Example: /# cd ip
/ip# ip route del 200.111.153.140 255.0.0.1 192.168.1.1
Variable Definition
dest ip-addr Destination IP address of the new route
dest mask Subnet Mask of the Destination IP address
next hop IP address of the next hop host to reach route
interface-name Name of the interface.
There is no "next hop" on un-numbered PPP interfaces so you have
to use the interface name.
NOTE: On an un-numbered PPP interface you should specify the interface name instead
of the next hop address (since you can't specify 0.0.0.0 as a valid next hop).
Mode: ip
Syntax: ip unreachables
Description: This command enables sending of ICMP unreachable messages.

Example: /# cd ip
/ip# ip unreachables

CLI Commands
ip
Mode: ip
Syntax: no arp {ip-address} {interface-name}
Description: This command removes an entry in the ARP cache.

Example: /# cd ip
/ip# no arp 192.168.111.35 1E1
Variable Definition
interface-name Name of Interface
Mode: ip
Syntax: no icmp send echo reply
Description: This command disables sending of ICMP echo replies for the incoming ICMP echo
requests.
Example: /# cd ip
/ip# no icmp send echo reply
Mode: ip
Syntax: no ip directed broadcast {interface-name}
Description: This command disables IP directed broadcast forwarding on the given interface.
Example: /# cd ip
/ip# no ip directed broadcast 1e1
Variable Definition
interface-name Interface on which the directed broadcast forwarding
is to be disabled.

CLI Commands
ip
Mode: ip
Syntax: no ip forwarding
Description: Disables IP forwarding globally on all interfaces of the router. Disabling IP forwarding
on an interface will result in packets, which are to be forwarded on that interface being
dropped and ICMP error messages being generated for the packets.
Example: /# cd ip
/ip# no ip forwarding
Mode: ip
Syntax: no ip path mtu {dest-ip} {ToS}
Description: This command removes the Path MTU entry for a given IP address.
Example: /# cd ip
/ip# no ip path mtu 10.0.0.2 0
Variable Definition
dest-ip IP address of the destination.
ToS Type of Service value.
Mode: ip
Syntax: no ip path mtu discover
Description: This command disables path MTU discovery on all paths. PMTU-D is not done even if
the application requests to do so.
Example: /# cd ip
/ip# no ip path mtu discover
Mode: ip
Syntax: no ip process option
Description: Disables processing of the IP options in the received IP packets.

Example: /# cd ip
/ip# no ip process option

CLI Commands
ip
Mode: ip
Syntax: no ip proxy arp
Description: This command is used to disable proxy ARP.

Example: /# cd ip
/ip# no ip proxy arp
Mode: ip
Syntax: no ip redirects
Description: This command disables sending of ICMP redirect messages.

Example: /# cd ip
/ip# no ip redirects
Mode: ip
Syntax: no ip unreachables
Description: This command disables sending of ICMP unreachable messages.

Example: /# cd ip
/ip# no ip unreachables
Mode: ip
Syntax: rarp add {hw-address} {ip-address}
Description: Adds the Reverse Address Resolution Protocol (RARP) entry to the server.
Example: /# cd ip
/ip# rarp add 00:11:22:33:44:55 10.0.0.11
Variable Definition
hw-address Physical address of the client
ip-address Destination IP address of the client

CLI Commands
ip
Mode: ip
Syntax: rarp del {hw-address}
Description: Deletes a Reverse Address Resolution Protocol (RARP) entry from the server.
Example: /# cd ip
/ip# rarp del 00:11:22:33:44:55
Variable Definition
hw-address Physical address of the client
Mode: ip
Syntax: rarp disable
Description: Disables RARP protocol.

Example: /# config ip
/ip# rarp disable
Mode: ip
Syntax: rarp server [entries]
Description: Enables Reverse Address Resolution Protocol (RARP) and displays the RARP entries.
Example: /# cd ip
/ip# rarp server 10
Variable Definition
entries Number of entries to be displayed. Range is 1-25.

CLI Commands
ppp
ppp
The following are the commands under the PPP mode. All commands listed below are hyperlinked to
the detailed definition of the command in this chapter.
• ip address local-pool {pool-index} {start-ip-addr} {end-ip-addr}

• no ip address local-pool {pool-index}
• ppp authentication aaa {local|radius}
• ppp trace {all|initshut|mgmt|data|ctpl|dump|os|failall|buffer|none}
• show ip address local-pool
• show ppp interface config
Mode: ppp
Syntax: ip address local-pool {pool-index} {start-ip-addr}
{end-ip-addr}
Description: Create Local IP address pool with the specified range.
Example: /# cd ppp
/ppp# ip address local-pool 1 10.0.0.10 10.0.0.100
Variable Definition
pool-index Specify pool index
start-ip-addr Specify start of IP pool
end-ip-addr Specify end of IP pool
Mode: ppp
Syntax: no ip address local-pool {pool-index}
Description: Delete Local IP address pool with the specified index.

Example: /# cd ppp
/ppp# no ip address local-pool 1
Variable Definition
pool-index Specify pool index

CLI Commands
ppp
Mode: ppp
Syntax: ppp authentication aaa {local|radius}
Description: This command is used to set the type of authentication method for user authentication.
Example: /# cd ppp
/ppp# ppp authentication aaa local
Variable Definition
local Set authentication method to local. Default.
radius Set authentication method to RADIUS.
Mode: ppp
Syntax: ppp trace {all|initshut|mgmt|data|ctpl|dump|os|failall|
buffer|none}
Description: Set debug level for tracing PPP module.
Example: /# cd ppp
/ppp# ppp trace dump
Variable Definition
all all the traces
buffer Buffer traces
ctpl Control Plane traces
data Data path traces
dump Packet dump traces
failall all failure traces
initshut Init and shutdown traces
mgmt Management traces
os Traces related to all resources except buffers
none No tracing for PPP

CLI Commands
ppp
Mode: ppp
Syntax: show ip address local-pool
Description: Displays all Local IP address pools.

Example: /# cd ppp
/ppp# show ip address local-pool
Pool Index Start Address End Address

1 10.0.0.10 10.0.0.100
Mode: ppp
Syntax: show ppp interface config
Description: This command displays PPP interface details.

Example: /# cd ppp
/ppp# show ppp interface config
/ppp# show ppp interface config
---------------------------
Interface Index : 5
Encap type : PPP
Admin Status : Down
Oper Status : Down
AAA Authentication Method : Local

Magic Number Negotiation : Enabled
LQR Reporting Period : 0
IPCP Admin Status : Closed
PPP Keep-Alive-Timer Period : 10
Interface Index : 6
Encap type : PPP
Admin Status : Up
Oper Status : Up
AAA Authentication Method : Local

Magic Number Negotiation : Enabled
LQR Reporting Period : 0
IPCP Admin Status : Closed
PPP Keep-Alive-Timer Period : 10

CLI Commands
relay
relay
The following are the commands under the RELAY mode. All commands listed below are hyperlinked
• dns relay cache ttl {number}

• dns relay default-nameserver {ip-address} {domain-name}
• dns relay maxCacheEntries {number}
• dns relay maxNameServer {number}
• dns relay maxQueries {number}
• dns relay maxUrlFilters {number}
• dns relay port type {number}
• dns relay primary-nameserver {server-address} domain {domain-name}
• dns relay query timeout {number}
• dns relay trace {on{tracevalue}|off}
• relay cache {enable|disable|clear}
• relay disable
• relay enable
• show dns relay cache
• show dns relay message info
• show dns relay name-server table
Mode: relay
Syntax: dns relay cache ttl {number}
Description: Configures the TTL for cache entries.

Example: /# cd relay
/relay# dns relay cache ttl 123
Variable Definition
number Range is 10-604800 minutes.

CLI Commands
relay
Mode: relay
Syntax: dns relay default-nameserver {ip-address} {domain-name}
Description: Configures the DNS Relay default server.

/relay# dns relay default-nameserver 192.168.0.100 boulder
Variable Definition
ip-address IP address of the Name Server. Default is 0.0.0.0
domain-name Enter Domain Name. Default is “none”
Mode: relay
Syntax: dns relay maxCacheEntries {number}
Description: This command sets the maximum cache entries.

/relay# dns relay maxCacheEntries 100
Variable Definition
number Range is 1-5000. Default is 10 entries.
Mode: relay
Syntax: dns relay maxNameServer {number}
Description: This command sets the maximum server entries.

/relay# dns relay maxNameServer 10
Variable Definition
number Range is 1-2000.
Mode: relay
Syntax: dns relay maxQueries {number}
Description: This command sets the maximum queries.

/relay# dns relay maxQueries 10
Variable Definition

CLI Commands
relay
Mode: relay
Syntax: dns relay maxUrlFilters {number}
Description: This command sets the maximum filters.

/relay# dns relay maxUrlFilters 100
Variable Definition
Mode: relay
Syntax: dns relay port type {number}
Description: This command sets the port type.

/relay# dns relay port type 100
Variable Definition
num Range is 1-65535.
Mode: relay
Syntax: dns relay primary-nameserver {server-address} domain
{domain-name}
Description: Set the IP address and domain name of the primary nameserver
Example: /relay# dns relay default-nameserver 10.10.10.1 boulder
Variable Definition
server-address IP address of the Name Server.
domain-name Enter Domain Name.
Mode: relay
Syntax: dns relay query timeout {number}
Description: This command sets the timeout for a query in seconds.

/relay# dns relay query timeout
Variable Definition
number Range is 3-29 seconds. Default is 10 seconds.

CLI Commands
relay
Mode: relay
Syntax: dns relay trace {on{tracevalue}|off}
Description: This command enables/disables the relay trace.

/relay# dns relay trace off
Variable Definition
off Disables the trace.
on {trace-value} Range is 0-6. Need info here.
Mode: relay
Syntax: relay cache {enable|disable|clear}
Description: Configure the relay cache.

/relay# relay cache enable
Variable Definition
clear Clears the relay cache
disable Disables the relay cache. Default is disable.
enable Enables the relay cache
Mode: relay
Syntax: relay disable
Description: Shutdown the relay and remove all related dependencies.

/relay# relay disable
Mode: relay
Syntax: relay enable
Description: Initialize the relay and start the relay agent.

/relay# relay enable

CLI Commands
relay
Mode: relay
Syntax: show dns relay cache
Description: Display DNS relay cache information.

/relay# show dns relay cache
Cache Status : Disable

Max Cache Entries : 10
Max Cache TTL : 3600
Good caches : 0
Bad caches : 0
Cache overflows : 0
Mode: relay
Syntax: show dns relay message info
Description: Display the query info, number of queries answered etc.

/relay# show dns message info
Retransmits Responses Pending TimeOut

0 0 0 10
Mode: relay
Syntax: show dns relay name-server table
Description: Display information about all name servers.

/relay# show dns relay name-server table
Default relay name server info :
Max.No : 10
DefaultNS : 10.50.1.1
DomainName : carrieraccess.com
Relay Status : Enabled
Primary Relay Servers Info :
NSAdderss : 10.50.1.1
QueriesSent : 0
Responces : 0
RowStatus : ACTIVE

CLI Commands
resolver
resolver
The following are the commands under the RESOLVER mode. All commands listed below are
• dns-resolver trace {all|packets|failure|none}

• resolver {enable|disable}
• resolver cache {clear|disable|enable}
• resolver cache ttl {ttl}
• resolver clear query info
• resolver nameserver {server-address} domain {domain-name}
• resolver safetybelt addr {ip-address} domain {domain-name}
• resolver safetybelt delete domain {domain-name}
• show resolver cache
• show resolver config
• show resolver name-server table
• show resolver queries
• show resolver statistics
Mode: resolver
Syntax: dns-resolver trace {all|packets|failure|none}
Description: This command set the trace status for the DNS Resolver.
Example: /# cd resolver
/resolver# dns-resolver trace all
Variable Definition
all Shows all trace messages related to any operation for DNS resolver.
packets Shows trace messages related to packets (received/transmitted)
specific to DNS resolver
failure Shows trace messages associated with failure conditions in DNS
resolver.
none Turns off tracing.

CLI Commands
resolver
Mode: resolver
Syntax: resolver {enable|disable}
Description: This command enables/disables the Domain Name Server (DNS) Resolver.
/resolver# resolver enable
Mode: resolver
Syntax: resolver cache {clear|disable|enable}
Description: This command configures the caching in the DNS Resolver.

/resolver# resolver cache clear
/resolver# show resolver cache
No cache entry found
Variable Definition
clear Clears the DNS resolver cache
disable Disables the DNS resolver cache
enable Enable the DNS resolver cache
Mode: resolver
Syntax: resolver cache ttl {ttl}
Description: This command configures the Time To Live (TTL) for cache entries.
/resolver# resolver cache ttl 123
Variable Definition
ttl Range is 10-604800 minutes, with a default of 60 minutes.
Mode: resolver
Syntax: resolver clear query info
Description: This command clears the query information table.

/resolver# resolver clear query info
Cleared query info table

CLI Commands
resolver
Mode: resolver
Syntax: resolver nameserver {server-address} domain {domain-name}
Description: This command adds a default Name and server entry.

/resolver# resolver nameserver paris domain suburb
Variable Definition
server-address Default IP address of the NameServer. Default is 0.0.0.0.
domain-name Default Domain name.
Mode: resolver
Syntax: resolver safetybelt addr {ip-address} domain {domain-name}
Description: This command adds a Name Server entry.

/resolver# resolver safetybelt addr 10.1.2.3 domain suburb
Variable Definition
ip-address IP address of the NameServer. Default is 0.0.0.0.
domain-name Domain name.
Mode: resolver
Syntax: resolver safetybelt delete domain {domain-name}
Description: This command adds a name-server entry.

/resolver# resolver safetybelt delete domain suburb

CLI Commands
resolver
Mode: resolver
Syntax: show resolver cache
Description: This command displays the DNS Resolver cache entries.

//resolver# show resolver cache
Domain Name IP-Address RRType RRClass
domain1.carrieraccess.com 10.40.1.6 Host Addr Internet
domain2.carrieraccess.com 10.10.1.10 Host Addr Internet
intraweb.carrieraccess.com 10.50.1.1 Host Addr Internet
Mode: resolver
Syntax: show resolver config
Description: This command displays the DNS Resolver configuration.

/resolver# show resolver config
Version Name : Dns Resolv Version 1.0.0.0

Resolver Service : Enabled
Cache Status : Disabled
UDP Local Port : 7000
TCP Local Port : 7000
Default NameServer : 0.0.0.0
Default Domain Name :
Cache Purge Interval : 3600sec
Query Timeout Interval : 10sec
Cache TTL : 60mins

CLI Commands
resolver
Mode: resolver
Syntax: show resolver name-server table
Description: Displays the name-server table as configured by user.

Example: /# cd resolver/
/resolver# show resolver name-server table
Default Resolver Name Server Info :
Max.No : 0
DefaultNS : 10.50.1.1
Primary Resolver Servers Info :
Mode: resolver
Syntax: show resolver queries
Description: This command displays the DNS Resolver queries.

/resolver# show resolver queries
No queries in table
Mode: resolver
Syntax: show resolver statistics
Description: This command displays the DNS Resolver statistics.

/resolver# show resolver statistics
Queries Received : 0
Stan Queries Received : 0
I Queries Received : 0
Queries Responded : 0
Queries Sent to Default NameServer : 0
Queries Retransmission : 0
Queries Responses : 0
Unknown Responses : 0
Auth Data Responses : 0
Auth No Data Responses : 0
Non Auth Data Responses : 0
Cache Overflows : 0
Good Cache : 0
Bad Cache : 0
Queries Filtered : 0

CLI Commands
rip
rip
The following are the commands under the RIP mode. All commands listed below are hyperlinked to
• neighbor add {Nbr-addr}

• neighbor del {Nbr-addr}
• neighbor disable
• neighbor enable
• no redistribute {direct|static|ospf|all}
• no spacing
• redistribute {direct|static|ospf|all}
• re-transmit {timeout}
• rip trace {initshut-1|mgmt-2|data-4|ctpl-8|dump-16|OS-32, failall-64|buffer-128|all-
255|disable-0}
• security {min|max}
• show neighbor
• spacing
Mode: rip
Syntax: neighbor add {Nbr-addr}
Description: Configures the Trusted Neighbors. RIP will accept the RIP packets from this Router.
Example: /# cd rip
/rip# neighbor add 10.0.0.35
Variable Definition
Nbr-addr IP address of the trusted neighbor.
Mode: rip
Syntax: neighbor del {Nbr-addr}
Description: Deletes the Trusted Neighbor.

Example: /# cd rip
/rip# neighbor del 10.0.0.35
Variable Definition
Nbr-addr IP address of the trusted neighbor.

CLI Commands
rip
Mode: rip
Syntax: neighbor disable
Description: Disables the Trusted Neighbor feature and RIP packets from all the routers will be
processed.
Example: /# cd rip
/rip# neighbor disable
Mode: rip
Syntax: neighbor enable
Description: Enables Trusted Neighbor feature, which allows that a list of router’s IP addresses can be
configured via the neighbor add command and RIP packets from those routers will be
processed by RIP and packets from other Routers will be dropped.
Example: /# cd rip
/rip# neighbor enable
Mode: rip
Syntax: no redistribute {direct|static|ospf|all}
Description: Disables redistribution of routes into RIP.

Example: /# cd rip
/rip# no redistribute static
Variable Definition
direct For direct routes.
static For static routes.
ospf OSPF routes are routes learned through OSPF. Note: OSPF is not
supported in this release.
all All types of routes
Mode: rip
Syntax: no spacing
Description: When this command is entered, generation of periodic update packet will not be split and
sent.
Example: /# cd rip
/rip# no spacing

CLI Commands
rip
Mode: rip
Syntax: redistribute {direct|static|ospf|all}
Description: Enables redistribution of routes into RIP.

Example: /# cd rip
/rip# redistribute static
Variable Definition
direct For direct routes.
static For static routes.
Mode: rip
Syntax: re-transmit {timeout}
Description: Specifies the interval to retransmit the update request packet or an unacknowledged
update response packet.
Example: /# cd rip
/rip# re-transmit 8
Variable Definition
timeout Range 5-10 seconds. Default is 5 seconds.

CLI Commands
rip
Mode: rip
Syntax: rip trace {initshut-1|mgmt-2|data-4|ctpl-8|dump-16|OS-32,
failall-64|buffer-128|all-255|disable-0}
Description: Sets RIP Trace to the specified level. Combination of levels are allowed. For example, if
initshut and mgmt are specified, then the Traces related to Init-Shutdown and
Management will be enabled.
Example: /# cd rip
/rip# rip trace 64
Variable Definition
all -255 All Traces
buffer -128 Buffer Traces
ctpl -8 Control Plane Traces
data -4 Data Path Traces
dump -16 Packet Dump Traces
failall -64 All Failure Traces
initshut -1 Init and Shutdown Traces
mgmt -2 Management Traces
os -32 Traces related to all Resources except Buffers
disable -0 Traces related to all Resources except Buffers
Mode: rip
Syntax: security {min|max}
Description: This command is used to set the security level of Routing Information Protocol (RIP).
Example: /# cd rip
/rip# security min
Variable Definition
min Minimum - The RIP1 packets will be accepted even when
authentication is in use.
max Maximum - The RIP1 packets will be ignored when authentication is
in use. Default is max.

CLI Commands
rip
Mode: rip
Syntax: show neighbor
Description: Displays the current neighbors.

Example: /# cd rip
/rip# show neighbor
Neighbor list: Enabled

Neighbor(s):
--------------
10.10.2.205
Mode: rip
Syntax: spacing
Description: If this command is entered, generation of periodic update packet will be split and sent.
Example: /# cd rip
/rip# spacing

CLI Commands
rtm
rtm
The following are the commands under the RTM mode. All commands listed below are hyperlinked to
• as-num {value}
• deny add {dest-ip} {Dest-range} {static|rip|ospf} {rip|ospf|all}
• deny all
• deny del {dest-ip} {dest-range}
• permit add {dest-ip} {dest-range} {static|rip|ospf} {rip|ospf|all}
• permit all
• permit del {dest-ip} {dest-range}
• router-id {ip-address}
Mode: rtm
Syntax: as-num {value}
Description: This command sets the AS-number for the router

Example: /# cd rtm
/rtm# as-num 99999
Variable Definition
value as-num {val}

CLI Commands
rtm
Mode: rtm
Syntax: deny add {dest-ip} {Dest-range} {static|rip|ospf}
{rip|ospf|all}
Description: This command adds a deny entry in the RRD control table.
Example: /# cd rtm
/rtm# deny add 10.0.0.10 24 static rip
Variable Definition
dest-range Enter range of addresses
static Static address
rip RIP address
Mode: rtm
Syntax: deny all
Description: This command sets the control table to permit mode, thereby allowing configuration of
permit entries.
Example: /# cd rtm
/rtm# deny all
Mode: rtm
Syntax: deny del {dest-ip} {dest-range}
Description: This command removes a deny entry in the RRD control table.
Example: /# cd rtm
/rtm# deny add 10.0.0.10 24
Variable Definition
dest-range Enter range of addresses.

CLI Commands
rtm
Mode: rtm
Syntax: permit add {dest-ip} {dest-range} {static|rip|ospf}
{rip|ospf|all}
Description: This command adds a permit entry in the RRD control table.
Example: /# cd rtm
/rtm# permit add 10.0.0.10 24 static rip
Variable Definition
static Static address
rip RIP address
Mode: rtm
Syntax: permit all
Description: This command sets the control table to Deny mode, thereby allowing configuration of
Deny entries.
Example: /# cd rtm
/rtm# permit all
Mode: rtm
Syntax: permit del {dest-ip} {dest-range}
Description: This command sets the control table to Deny mode, thereby allowing configuration of
Deny entries.
Example: /# cd rtm
/rtm# permit del
Variable Definition

CLI Commands
rtm
Mode: rtm
Syntax: router-id {ip-address}
Description: This command defines an identifier for the router.

Example: /# cd rtm
/rtm# router-id 192.168.2.200
Variable Definition
ip-address IP address to be assigned to the router.

CLI Commands
snmp
snmp
The following are the commands under the SNMP mode. All commands listed below are hyperlinked
• no snmp-community {index}
• no snmp-shutdown
• no snmp-trap {index}
• snmp-community {index} community-name {name} ipaddr {ip-address} privilege
{readonly|readwrite}
• snmp-shutdown
• snmp-trap {number} mgr-addr {ip-address} community {name} version {v1|v2|
both} trap-port {port-number}
Mode: snmp
Syntax: no snmp-community {index}
Description: Deletes the specific community information.
Example: /# cd snmp
/snmp# no snmp-community 2
Variable Definition
index Enter the SNMP-community index to remove.
Mode: snmp
Syntax: no snmp-shutdown
Description: This command enables the SNMP Agent and SNMP requests will be processed.
Example: /# cd snmp
/snmp# no snmp-shutdown

CLI Commands
snmp
Mode: snmp
Syntax: no snmp-trap {index}
Description: Deletes the specific trap manager information.
Example: /# cd snmp
/snmp# no snmp-trap 2
Variable Definition
index Specify the trap manager information.
Mode: snmp
Syntax: snmp-community {index} community-name {name} ipaddr
{ip-address} privilege {readonly|readwrite}
Description: Configures the SNMP community details which is used to store the machine and its
privileges.
Example: /# cd snmp
/snmp# snmp-community 2 community-name NETMAN ipaddr
10.6.4.232 privilege readonly
Variable Definition
index Specify trap manager information.
name Define a community name.
ip-address The IP address of the machine to be stored
readonly Sets the privilege level to Read-Only.
readwrite Sets the privilege level to Read and Write.
Mode: snmp
Syntax: snmp-shutdown
Description: This command disables the SNMP Agent and SNMP requests will no be processed.
Example: /# cd snmp
/snmp# no snmp-shutdown

CLI Commands
snmp
Mode: snmp
Syntax: snmp-trap {number} mgr-addr {ip-address} community {name}
version {v1|v2|both} trap-port {port-number}
Description: Configures the SNMP manager details to whom SNMP traps can be sent. A maximum of
10 entries can be configured.
Example: /# cd snmp
/snmp# snmp-trap 2 mgr-addr 10.6.4.212 community NETMAN
version v1 trap-port 1
Variable Definition
num_str Specify trap manager information
ip-address The trap manager IP address
name Specify a community name
v1|v2|both SNMP version 1, version 2 or both
port-number Trap port number

CLI Commands
sntp
sntp
The following are the commands under the SNTP mode. All commands listed below are hyperlinked to
• clock timezone {name} hours {hours} minutes {minutes} {before_UTC|after_UTC}

• no clock timezone
• no sntp poll-interval
• no sntp server {unicast|multicast|anycast} [ip-address]
• show sntp config
• show time
• sntp {enable|disable}
• sntp poll-interval {seconds}
• sntp server {unicast|multicast|anycast} [ip-address]
Mode: sntp
Syntax: clock timezone {name} hours {hours} minutes {minutes}
{before_UTC|after_UTC}
Description: This command will set the Simple Network Time Protocol (SNTP) timezone offset.
Example: /# cd sntp
/sntp# lock timezone Tulsa hours 1 minutes 10 before_utc
Variable Definition
name Enter a name for the timezone.
hours Set the hour from the Universal Time Clock
minutes Set the minutes from the Universal Time Clock
before_UTC Set time is to be subtracted from the Universal Time clock (earlier)
after_UTC Set time is to be added from the Universal Time clock (later)
Mode: sntp
Syntax: no clock timezone
Description: This command will remove the timezone offset.

Example: /# cd sntp
/sntp# no clock timezone

CLI Commands
sntp
Mode: sntp
Syntax: no sntp poll-interval
Description: This command will disable the Simple Network Time Protocol (SNTP) poll interval.
Example: /# cd sntp
/sntp# no sntp poll-interval
Mode: sntp
Syntax: no sntp server {unicast|multicast|anycast} [ip-address]
Description: This command will remove a Simple Network Time Protocol (SNTP) server.
Example: /# cd sntp
/sntp# no sntp server unicast
Variable Definition
unicast To one device.
multicast To a selected group.
anycast To the closest member of a group, which will then perform the
removal from the group.
ip-address To a defined IP address.
Mode: sntp
Syntax: show sntp config
Description: This command will display the SNTP configuration.

Example: /# cd sntp
/sntp# show sntp config
SNTP status : Disabled

Server : NULL
Server Mode : UNICAST
Poll Interval : 14 seconds
Timezone : Tulsa:1 hour 20 minutes before UTC

CLI Commands
sntp
Mode: sntp
Syntax: show time
Description: This command will display the current time.

Example: /# cd sntp
/sntp# show time
Current Time : 01:33:39
Mode: sntp
Syntax: sntp {enable|disable}
Description: This command will enable/disable Simple Network Time Protocol (SNTP) on the system.
Example: /# cd sntp
/sntp# sntp enable
Mode: sntp
Syntax: sntp poll-interval {seconds}
Description: This command will configure the Simple Network Time Protocol (SNTP) poll interval.
Example: /# cd sntp
/sntp# sntp poll-interval 14
Variable Definition
seconds Range is 16-1024, with a default of 14 seconds.
Mode: sntp
Syntax: sntp server {unicast|multicast|anycast} [ip-address]
Description: This command will configure a Simple Network Time Protocol (SNTP) server.
Example: /# cd sntp
/sntp# sntp server unicast
Variable Definition
unicast To one device.
multicast To a selected group.
anycast To the closest member of a group, which will then perform the
removal from the group.
ip-address To a defined IP address.

CLI Commands
system
system
The following are the commands are under the SYSTEM mode. All commands listed below are
• file-delete {file-name}
• file-download {file-name} ipaddr {ip-address} [destfile {name}]
• file-rename {old-name} {new-name}
• file-upload {file-name} ipaddr {ip-address} [destfile {name}]
• reset
• show files
Mode: system
Syntax: file-delete {file-name}
Description: Delete the specified file from FLASH. There is not a default file "name" on the command.
Example: /# cd system
/system# file-delete flash
Variable Definition
file-name The name of one of the files available. Display a list of the files with
the show files command.
Mode: system
Syntax: file-download {file-name} ipaddr {ip-address}
[destfile {name}]
Description: Attempt to retrieve the file "path\name" specified at the IP address entered by the user.
This command may be used for configuration and application files.
No defaults are on the command.
Example: /system#
/system# file-download flash ipaddr 192.168.10.10
Variable Definition
file-name Name to be used on the FLEXmaster for the configuration or
application file. Maybe up to 32 characters.
ip-address The form xxx.xxx.xxx.xxx must be used where xxx is a number
between 0 and 255.
name Name of configuration or application file. Maybe up to 32 characters.
Acceptable filename extensions are: *.mgm, *.cfg.

CLI Commands
system
Mode: system
Syntax: file-rename {old-name} {new-name}
Description: Renames a file from the first specified name to the second.
Example: /system# file-rename vxWorks.mgh backup.mgh
Renamed file vxWorks.mgh to backup.mgh
Variable Definition
old-name The current file name.
new-name New name for the file.
Mode: system
Syntax: file-upload {file-name} ipaddr {ip-address} [destfile
{name}]
Description: uploads a file to the specified TFTP server
Example: file-upload almsys.txt ipaddr 192.168.1.160
Variable Definition
file-name Name of file to load.
ip-address The form xxx.xxx.xxx.xxx must be used where xxx is a number
between 0 and 255.
name Optional parameter. Name of the destination file.
Mode: system
Syntax: reset
Description: This command is not supported in this release.

CLI Commands
system
Mode: system
Syntax: show files
Description: Displays the current running and backup files.

Example: /system# show files
File Name Size (bytes)
---------------- ------------
directory 1760 bytes
Hlink.mgh 42385 bytes
fpga.mgh 38227 bytes
vxWorks.mgh 2641067 bytes
ds11.cfg 38 bytes
ds12.cfg 38 bytes
ds13.cfg 38 bytes
ds14.cfg 38 bytes
ds15.cfg 38 bytes
ds16.cfg 38 bytes
ds17.cfg 38 bytes
ds18.cfg 38 bytes
aoc1.cfg 1128 bytes
aoc2.cfg 1128 bytes
aoc3.cfg 1128 bytes
aoc4.cfg 1128 bytes
aoc5.cfg 1128 bytes
aoc6.cfg 1128 bytes
aoc7.cfg 1128 bytes
aoc8.cfg 1128 bytes
sys.cfg 33 bytes
flash 272627 bytes

CLI Commands
system

CHAPTER
5
CLI Configuration
In this Chapter
Accessing the CLI
Basic Configurations
- RIP Configuration
- Setting Ethernet Interfaces
- Interface Stacking
- Save Configuration
System Information
CLI Configuration
Accessing the CLI
Accessing the CLI

Select Setup > mGmt > CLI from the text user interface, and you will be placed in the S (Setup)
root mode of the CLI.
G (mGmt)
C (CLI)
1. RIP Configuration
Use the following commands to configure RIP. For more information regarding the commands, see
Chapter 4, CLI Commands.
1. Connect to the CLI, from the TUI: Setup > mGmt > CLI.
2. Log on to the system with the superuser password. The default password is blank (press
[ENTER]).
The following commands are for numbered and unnumbered interfaces.
Command Description
/# interface 1x1 Create interface 1X1 and change mode to 1X1
/1X1# ip rip enable Enable rip on 1X1
/1X1# send rip2 Set the RIP version send method
/1X1# recv both Set the RIP receive version method
/1X1# cd / Change mode to root
/# interface 1e1 Change mode to interface 1E1
/1E1# ip rip enable Enable rip on 1E1
/1E1# send rip2 Set the RIP version send method
/1E1# recv both Set the RIP receive version method
/1E1# cd / Change mode to root
/# cd rip Change mode to RIP
/rip# router rip Enables the RIP protocol
/rip# redsitribute direct Enables redistribution of direct routes into RIP
/rip# redistribute static Enables redistribution of static routes into RIP

CLI Configuration
2. Setting Ethernet Interfaces

Use the following commands to configure Ethernet interfaces. For more information regarding the
commands, see Chapter 4, CLI Commands.
Command Description
/1E1# shutdown Set 1E1 as out-of-service
/1E1# ip config 11.0.0.1 mask 255.0.0.0 Set the IP address and subnet mask for the interface
/1E1# no shutdown Set 1E1 as in-service
3. Interface Stacking
Before stacking a ppp interface over an hdlc interface, configure the cross connects in the Connect
screen. Save and activate the cross connects in the coMmit screen.For more information about cross
connects, see Configuring Internal Timeslot Connections on page 3-25.
Command Description
/# interface 1X1 Create the interface
/# cd 1M1 Change mode to interface 1M1
/1M1# no shutdown Set 1M1 as in-service
/# cd 1X1 Change mode to 1X1.
There are a number of commands you can enter at this point,
depending on what PPP parameters you need. Some examples are:
/1X1# magic number
/1X1# keep-alive-timer 10
/1X1# no shutdown Set 1X1 as in-service

/1M1# cd / Change mode to root
/# cd 1X1 Change mode to 1X1
/1X1# stackinterface 1M1 Stack interface 1X1 over 1M1
Layering successful
/1X1#
4. Save Configuration
It is always a good idea to save your configuration. After exiting the CLI, save your changes using the
coMmit screen in the TUI. For more information about saving and committing changes, see Error
Checking, Saving, and Activating the Configuration on page 3-34.

CLI Configuration
System Information
System Information
To display basic system information user the following commands:
/# show version
Equipment Versions:
BootCode Version:
FPGA Revision: 0.00
CPU: WinPath 747 Rev A.0
DPS version: 0X10001112
BSP: Winpath/MIPS5Kc
Product Features:
T1x4 - T1 Enabled
HDLCx4 - HDLC Enabled
/# show ip interface
IP Interface Configuration
Interface Index : 1
IP Address : 192.168.1.160
Subnet Mask : 255.255.255.0
MAC Address : 00:e0:97:10:95:7e
NAT Address Domain : Local
Interface Index : 2
Interface Admin Status : Down
Interface Oper Status : Down
IP Address : 0.0.0.0
MAC Address : 00:e0:97:10:95:7f
NAT Address Domain : None

CLI Configuration
System Information
/# show interface config all

----- ----- --------- --- ----------- ---------- ---------

CLI Configuration
System Information

CHAPTER
6
Diagnostics
In this Chapter
Overview
The Diagnostics Menu
Performing Diagnostics on Links
Performing Diagnostics on Ports
Resetting the Modules
Diagnostics
Overview
Overview
This chapter covers the diagnostic screens. Be sure that you have completed the basic setup described
in Chapter 3, Configuration.
The Diagnostics Menu

Use the diagnostics menu option to enter the diagnostics submenu screen. The D (Diag)
password is a 12-character editable field (superuser or maintenance access only). Type
your password and press [ENTER].

Diagnostics

Use the link diagnostics (Linkdiag) screen to control the diagnostic loopback and BERT functions of
any links in the MASTERseries unit.
The following diagnostic loopbacks are available.
D (Diag)
Power on self test of hardware
L (Linkdiag)
Local data port loopback (toward DTE) activation
Remote data port loopback (toward DCE) activation
Payload loopback activation (T1)
Local loopback activation (T1)
Remote line loopback (T1) using in-band code, T1.403, or 54016
Remote payload loopback activation (T1) using 54016 request
Reset of loopbacks using menu selection, in-band code, universal code
Line loopback activation for T1
Bidirectional loopback T1
Timed loopbacks for loopback types except fractional
User programmable in-band loop-up/down codes are available
Bit Error Rate Testing (BERT) for all applications modules except the DATAmaster
NOTE: An inactive BERT screen is presented if no BERT is connected, and no test is

being run. After you select the required link, the link parameters are displayed. If a BERT
is active, the BERT section of the Linkdiag screen displays the current BERT results on
that link. Default BERT parameters are displayed if the test is not active. The State field
indicates the ACTIVE or INACTIVE state of the BERT. BERT operations are independent
of the loopback operations and can be performed in conjunction with the loopback
operations.

Diagnostics
Linkdiag Screen
The fields on the link diagnostics screen are described below.
Field Description
Link This is a cyclical field which lists the slot and link ID of modules
installed in the chassis. Cycle through the field with the N or P key
and press [ENTER] to select a link.
Frame This is a protected field which is configured on the link screen. It
refers to the frame format on the selected link.
Code This is a protected field which is configured on the link screen. It
refers to the code type on the selected link.
Disabled This is a protected field which is configured on the link screen. It
refers to the disable option on the selected link.
Protocol This is a protected field which is configured on the link screen. It
refers to the performance monitoring option on the selected link

Diagnostics
Loopback Type
This is a cyclical field which lists the available loopbacks. These loopbacks conform to ANSI
T1.403, TR 54106, and PUB 62411. Whenever a loopback is active on a network interface the
front panel yellow LED for that link flashes (approximately once per second) to provide a visual
indication that a loopback test condition is present. When you have displayed the desired
choice, press [ENTER].
When a fractional loopback is chosen you will see a second screen after pressing [ENTER].
This screen contains the data from the connect screen (see Configuring Internal Timeslot
Connections on page 3-25) and an additional Yes/No column to indicate the channel(s) to be
looped back. This loopback is a local loopback on a DS0 basis.
Fractional Loopback
This is a cyclical field to enable or disable a loopback for the selected timeslot. When you have
displayed the required choice, press [ENTER].
Yes—loopback enabled
No—normal operation
Do not use fractional loopback when the link is in alarm. If the link is in alarm, trunk codes will
overwrite the fractional looped back data. Use a local link loopback, which will clear the alarm
condition
Loopback Timeout
After you have selected a loopback type, this three digit editable field is presented. Enter the number
of minutes you would like this loopback to run (1–999). Entering 0 will allow the loopback to run
indefinitely. Timed loopbacks of up to 30 minutes are allowed through Telnet.

Diagnostics
BERT Direction
Static field. Only one direction is available:
To_Network—BERT is enabled on channels in place of the outgoing channels from the TSI
(Time Slot Interchange). Since BERT is activated on channels, this test is useful only when
DS0s are configured the same.
BERT Pattern
This selectable field provides the patterns described below.
BERT Pattern Description

Marks Repetitive pattern of 1’s
1_In_8 Repetitive pattern of 1 in 8
Spaces Repetitive pattern of 0’s
511 Pseudorandom pattern of length 511 bits
2047 Pseudorandom pattern of length 2047 bits
2E15-1 Pseudorandom pattern of length 215-1 bits
QRSS Quasi random signal—220-1
Fract (Fractional)
This selectable field allows BERT on fractional links (group of DS0s). When No is selected,
BERT is run on a full link. When Yes is selected, user is navigated to the timeslot screen.
The only field that is selectable is the BERT column. Select Yes or No then [ENTER]. Press
[ESC] to exit screen. NOTE: Fractional BERT is offered under link diagnostic (LinkDiag).

Diagnostics
BERT Operation
Provides the following selections:
Option Description
Start BERT enabled to run test with the selected parameters (direction,
pattern and timeout). BERT status is updated every five seconds. You
must configure the path management for connections, loopbacks, and
so on.
If a BERT is currently running on any other link or port on this module,
the following message is displayed:
BERT is in progress on xxx where xxx indicates the card and link
number (for example, 1LA).
Stop Disables BERT to stop running the test.
Clear The counts are zeroed, and if a first timeout of 10 minutes, for example,
was specified, the test will finish in 10 minutes from the time it was
first started. This option is available when BERT is running on the
selected interface. The following message will be logged to the Linklog
screen:
“00:05:19 15, Jun 2001: BERT Counts Cleared 1LA”
Inject_ERR Available when the test is already in progress.
You can insert a single error bit or a steady stream of error bits into the
data path of a currently running BERT. This action, intentionally
corrupts the generated pattern. You will be navigated to the Err Inject
Rate field to provide the error rate. Error injection begins when you
select the error rate. You can perform this option when the test is
already in progress.
BERT Timeout
The BERT Timeout field appears after you start the BERT operation. This is a four-digit
editable field used to set the duration of BERT. Enter 0 and BERT will run indefinitely. The
maximum duration is 24 hours.

Diagnostics
Err Inject Rate

This is a cyclical field where you can select error rates only when InjectErr is selected. The
following choices are offered:
Single Insert a single error bit.

10x10-1 Insert 1 error bit per 10 bits.
10x10-2 Insert 1 error bit per 100 bits.
10x10-6 Insert 1 error bit per 1 million bits.
Link signaling and BERT—If a link is configured to be:
T1 Robbed bit All timeslots are BERT’d using seven bit mode.
Field Description
State BERT results are gathered every five seconds during a BERT test. The
screen is updated with the last results. This field is not editable and
indicates the ongoing progress of the test.
Possible values:
ACTIVE—BERT test is in progress.
INACTIVE—BERT is not connected.
Sync State of synchronization of the interface. Pseudorandom patterns
synchronized after 34 +n bits are received without error. Repetitive
patterns synchronized when a received pattern of the same length
matches the transmitted pattern.
Possible values:
IN—The interface is in sync.
OUT—The interface is out of sync.
Sync Lost Number of times the interface has lost sync after gaining initial sync.
(Initial sync, in this manual indicates the first time the interface under test
gains sync. All BERT counts, Sync lost, Bit count, Bit errors, and Error
rate are reset when BERT is started. Incrementing the count begins only
after the interface gains initial sync.)
Bit Errors Number of error bits received after gaining initial sync.
Lapsed Time Number of minutes elapsed since test was started.

Diagnostics
Link Loopback Diagrams

The following diagrams describe the link loopbacks.
None (All)— No loopback
(normal operation). This setting is
also used to abort an active
loopback.
Local (T1)—Local Loopback.
Local The local loopback is performed
Loopback Network using transceiver circuitry. This
Local Trans- Interface
—menu command
Module
Framer ceiver test verifies proper operation of
the unit up to the transceiver on
the link interface.
LocAIS (T1)—Local AIS

LocAIS
Local
Loopback. This loopback is the
Loopback Network same as a local loopback except
w/AIS Local Trans-
—menu command Module
Framer ceiver Interface
(AIS Sent)
that AIS is sent to the far end
while the loopback is activated.
Line (T1)—Line Loopback. The

line loopback causes the receive
Line signal at the DS1 interface to be
Loopback
—10,000/100 in-band code Local Trans-
Framer ceiver
Network internally routed to the transmitter
—T1 403 bit code Module Interface
—menu command of the module, allowing the line
connected to the interface to be
tested independently of the
module. The receive signal to the
module is not affected by the
loopback.
Payld (T1)—Payload Loopback.
The payload loopback causes the
receive signal at the DS1 interface
Payld—Payload to be internally routed to the
Loopback
—54016 request 1 Local Trans- Network
transmitter of the module, with the
Framer ceiver
—T1 403 bit code Module Interface exception that the framing and
—menu command
CRC-6 bits are reinserted to the
transmit signal stream. The
receive signal to the module is not
affected by the loopback.
Multiframe alignment of signaling
is not guaranteed during the
payload loopback.

Diagnostics
BiDir (T1)—BiDirectional
Loopback. Local and line
BiDir—BiDirectional
Loopback loopback activated
Local Trans- Network
—menu command
Module
Framer ceiver
Interface
simultaneously.
Fract—Fractional Loopback. The

fractional loopback is the same as
Fract—Fractional the local loopback except that only
Loopback
Local Trans-
Network user specified timeslots within the
—menu command Framer ceiver Interface
Module link are looped back. In addition
to the test coverage of a local
loopback, this loopback will also
test the time division multiplexer
function and the modules ability to
maintain synchronization between
the unit and an external device.
This type of loopback should only
be chosen when the link is green.
If the link is in alarm use a local
loopback.
RemLL (T1 only)—Remote Line
RemLL—Remote Loopback
Loopback. The remote line
Trans-
loopback is a loopback sent to the
Local Module Framer
ceiver far end of the link. It is the same as
Remote Module a Line Loopback described above.
RemPL (T1 ESF only)—Remote

RemPL—Remote Payload Loopback
Payload Loopback. The remote
Trans-
payload loopback is a loopback
Local Module Framer
ceiver sent to the far end of the link. It is
Remote Module the same as a Payload Loopback
described above.

Diagnostics

Use the portdiag screen to control the diagnostic loopback and BERT functions of
D (Diag)
any ports in the MASTERseries unit.
P (Portdiag)
NOTE: If a BERT is active, the BERT section of the portdiag screen displays the current
BERT results on that port. Default BERT parameters are displayed if the test is not active.
The state field indicates whether the BERT is running on this port.
The following table describes the fields on the port diagnostics screen:
Port Diagnostics Screen Definitions
Port This is a cyclical field that lists the slots and port ID of modules installed in the
chassis. When you have displayed the required port press [ENTER].
Type This is a system populated field. It refers to the associated port type.
Interface This is a system populated field. It refers to the configured interface setting.
Rate This is a protected field which shows the amount of configured bandwidth
assigned to the selected port. This information is configured on the connect
screen.
Loopback This is a cyclical field which selects the port loopback options. When you have
Type displayed the required loopback type, press [ENTER].
Loopback This is a three-position editable field. Enter the number of minutes you would
Timeout like this loopback to run (1-999). Entering 0 will allow the loopback to run until
stopped by you or activate (Y) is selected on the commit (see Error Checking,
Saving, and Activating the Configuration on page 3-34) screen. Timed
loopbacks of up to 30 minutes are allowed through Telnet.

Diagnostics
Port Diagnostics Screen Definitions (Continued)

BERT To TSI—The BERT is connected in place of one of the ports toward the TSI.
Direction The TSI can be configured to send the port data anywhere in the system as long
as the BERT data is configured to arrive back to the BERT_PORT.
To PORT—The BERT is connected to a port in place of the TSI. The BERT
data is not crossconnected through the TSI. The full bandwidth allocated to the
port is used for the BERT. Changing the baud rate automatically provides more
or less BERT bandwidth per frame. This requires an external loopback at the
port.
The following diagrams show the port loopbacks:
None—No loopbacks, normal

operation.
Loc— Loopback towards DTE at
Loc—Local port interface.
Data Port Network
Loopback Interface
—menu selection Trans-
ceiver Framer
Rmt —Loopback towards DCE at

Rmt—Remote
Data Port
port interface.
Network
Loopback Interface
—menu selection Trans-
ceiver Framer
NOTE: The Carddiag feature is currently not available. Self test card diagnostic functions
are only performed during powerup.

Diagnostics

Use the warm reset screen to reset a specified module in the chassis. A reset is
D (Diag)
typically performed after loading new versions of software or changing the IP
address of the system. This function will not affect the time and date settings. W (Warmreset)
The following table describes the fields on the warm reset screen:
Warm Reset Screen Definitions

Card to reset This is a cyclical field. When you have displayed the card to be reset, press
[ENTER]. If you warm reset the master module (which is typically the
module in slot #1 of the chassis), the units installed in the chassis will be
reset.
Confirm This field is a yes or no field. It appears after selecting the card to reset.

Diagnostics

CHAPTER
7
Maintenance
In this Chapter
Overview
Displaying the Version Number
Alarms Screen
Link and Port Status
Alarm Contact Configuration
Link Alarm History
History Events
Displaying the Local Performance Statistics
Remote Performance Statistics
Individual Performance Statistics
Using the Help Screen
Sending a Copy of the System and Alarm Events
Uploading the Configuration Files
Downloading Application and Configuration Files
Maintenance
Overview
Overview
This chapter covers the maintenance screens. Be sure that you have completed the basic setup outlined
in Chapter 3, Configuration.
Displaying the Version Number

Use the version screen to display information about the software, hardware and S (Setup)
firmware installed in the MASTERseries application module. This information is useful
when seeking technical support or upgrading the software in your system V (Vers)

----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
CARD: 1 Version Information
MANUFACTURE BOARDS SERIAL NUMBER REV

Model #
Engine 00e097109ab9
Base
Processor
Link 2
Compression
Part #
LOAD IMAGES Boot Loader 0.B Mar 7 2005
Software 4.0.2 2005/03/11 2643282-1
Configuration
Dacs
Control 2005/02/02 38470-4-66
Link 2005/02/01 43687-4-0
Imux
To select the card to view, cycle to the desired card using the N/P keys and press [ENTER]. The
remaining fields on this screen are protected fields and are automatically populated by the system.

Maintenance
Alarms Screen
Alarms Screen
Use the alarms screen to list the current status of each link, port and power supply A (Alarms)
installed in the chassis. None of the fields on this screen are editable. At the bottom
of the screen is an alarm status summary for the entire chassis and a listing of slots currently in alarm.
The interface will be shown as Diag when loopback or BERT or both are active.

----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------
<------- LINK -------> <- PORT -> <------- MGMT ------->
M T1 ABCD 111 1111 EFGH 111 1111
# S E1 MODULE TYPE 1234 5678 9012 3456 1 1234 5678 9012 3456
- - --------------- ---- ---- ---- ---- ---- ---- ---- ---- ----
2 -
3 -
4 -
5 -
6 -
7 -
8 -

Power Supply 2 Up

---------------------------------- GREEN ---------------------------------
The following table describes the fields on the alarms screen:
Alarms Screen Definitions

# Slot Number This is a protected field which lists the populated slots in the chassis. It is
automatically populated by the system.
M Master/Slave This is a protected field which is automatically populated by the system. This
S column indicates an M for a master module and an S for a slave module. This
is not supported for FLEXmaster 4.02; every module is a master.
T1 T1 E1 This is a protected field that indicates whether the module is a T1 or an E1.
E1 E1 links are not supported for FLEXmaster 4.02.
Module Type This is a protected field that indicates the type of module installed in this slot.
It is automatically populated by the system.

Maintenance
Alarms Screen
Alarms Screen Definitions

Link This field is split into columns for each link on the module, numbered 1 through 16.
Each link automatically shows one of the following selections:
d Diag A diagnostic function is in operation.
D Down The link is in an alarm state.
I Init The link is initializing.
O Off Link is disabled.
U Up The link is up and functioning.
blank There is no module installed in this slot.
Port This field is split into port columns labeled E/1, F, G, and H. Each column represents a
port on each module installed in the chassis. Each port automatically shows one of the
following selections:
U Up The port is configured and operational.
D Down The port is in an alarm condition.
u Unassigned The port has not been assigned
Management This field is split into port columns labeled 1 and 2. Each column represents a
management port for each module installed in the chassis. Each port automatically
shows one of the following selections:
U Up PPP is configured and operational
D Down The port is in an alarm condition or PPP
is not established
u Unassigned The port has not been assigned.
Fan Displays the current status of the fans for a two-slot chassis.
Up The fan unit is operating.
Down The fan unit is not operating or is not installed.
Power Displays the current status of the power supplies.

Supply Up The power supply is operating.
Down The power supply is not operating or is not installed.

Maintenance
Alarms Screen
Alarm Contacts
The alarm power entry panel has two sets of form C alarm relay contacts, for major and minor alarms.
Both normally open and normally closed contacts are supported. The table that follows this table defines
the alarm contact operation.
The following table shows the alarm contacts:
Alarm Contacts
Major Alarm Contacts Minor Alarm Contacts
Alarm Conditions ON OFF ON OFF
Power Loss X X
No Alarms X X
Red Alarm X X
Yellow Alarm X X
PSU Failure X X
Threshold Red X X
Threshold X X
Minor X X
Slave Failure X X

Maintenance

Use the status screen to display the detailed status of the links and ports for each module T (sTat)
individually. This screen is related to the alarms screen. If the alarms screen indicates
an alarm on a particular module, you can go to the status screen to view the alarm details.
T1 FLEXmaster

----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
Card 1 T1 FLEXmaster
DS1/E1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
LPBK Non Non Non Non Non Non Non Non --- --- --- --- --- --- --- ---
BERT Non Non Non Non Non Non Non Non --- --- --- --- --- --- --- ---
STATE Red Red Red Red Red Red Red Red --- --- --- --- --- --- --- ---
TxD Yel Yel Yel Yel Yel Yel Yel Yel --- --- --- --- --- --- --- ---
RxD Los Los Los Los Los Los Los Los --- --- --- --- --- --- --- ---
MGMT u=unas U=Up D=Down

PORT 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
RATE 0 0 u u u u u u u u u u u u u u
State u u - - - - - - - - - - - - - -
PORT RATE LPBK BERT STATE DSR DTR DCD CTS RTS
1P01 V.35 0 None None Unas Off Off Off Off Off
---------------------------------- RED ---------------------------------

Alarms: 01 Clk: INT Mar 18, 2005 09:54
The fields on the status screen are described below:
Field Description
Card Use the N/P keys to cycle through the slot numbers of modules installed in the chassis.
LPBK Loopback. Shows the current loopback status for each link in the module.
Possible values: Local, Payld, Bidir, Fract, RemLL, RemPL, None.
BERT Indicates BERT status
State Displays the current alarm state of each link.
Possible values: RED, GREEN, YELLOW, BLUE, or Minor.
RxD Displays the alarm condition being received on each link. See a list of the possible alarm
conditions at RXD Values on page 7-7.
TxD Displays the alarm condition being transmitted on each link. See a list of the possible
alarm conditions at TXD on page 7-8.

Maintenance
RXD Values
Displays the alarm condition being received on each link. A list of the possible alarm conditions
and states follows:
Alarm Description
AIS Alarm indication signal
B8ZS B8ZS signature detected (T1)
CRC CRC error detected
CZR Eight consecutive zeros received (T1)
DB3 HDB3 signature detected (E1) *
ES Errored second
INIT Initialization
LAD Inband loop-up activate detected (T1 D4/ERIC)
LCV Line code violation
LDD Inband loop-down activate detected (T1 D4/ERIC)
LOS Loss of signal
MAIS Multiframe alarm indication signal (E1 CAS)*
MRAI Multiframe remote alarm indication signal (E1 CAS)*
NORM Good signal
NSL Uncontrolled bit slip (E1)*
OOF Out of frame
OOMF Out of multiframe (E1 CAS) *
PDV Pulse density violation
RAI Remote alarm indication signal (E1 G.704)*
REBE Remote end block error (E1)*
SESF Severely errored superframe
SLP Bit slip detected (E1)*
UAS Unavailable second
YEL Yellow alarm (T1)
* E1 is not supported in FLEXmaster 4.02

Maintenance
TXD
Displays the alarm condition being transmitted on each link. A list of the possible alarm
conditions and states follows:
Alarm Description
AIS Alarm indication signal
AisA Transmitted a timeslot 0 AIS signal on stream A of compressed link
AisB Transmitted a timeslot 0 AIS signal on stream B of compressed link
MAISA Transmitted a timeslot 0 multiframe AIS signal on stream A of
compressed link
MAISB Transmitted a timeslot 0 multiframe AIS signal on stream B of
compressed link
MRAIA Transmitted a timeslot 0 multiframe remote AIS signal on stream A
of compressed link
MRAIB Transmitted a timeslot 0 multiframe remote AIS signal on stream B
of compressed link
NORM Normal operation
RAIA Transmitted a timeslot 0 remote AIS signal on stream A of
compressed link
RAIB Transmitted a timeslot 0 remote AIS signal on stream B of
compressed link
Yel Yellow alarm

Maintenance
Port Status
MGMT u=unas U=Up D=Down

PORT 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
RATE 0 0 u u u u u u u u u u u u u u
State u u - - - - - - - - - - - - - -
PORT RATE LPBK BERT STATE DSR DTR DCD CTS RTS
Field Description
Port This column lists each port for modules in the chassis.
Rate This is the configured clock rate of the port. To view the actual rate of
IMUX ports that have automatically rate adapted, see Chapter 3,
Configuration, which shows displays of both the configured and actual port
rates.
LPBK Loopback. This shows the current loopback status.
Possible values: LOC, RMT, None.
BERT Displays current status of BERT.
STATE This is the current state of the port. The port states are:
Up - Port is configured and DTR is asserted.
Down - Port is configured but DTR is not asserted. If DTE is connected
data can pass (no port conditioning).
Unas - Port is not configured.
DSR Shows the status of Data Set Ready (Off or On).
DTR Shows the status of Data Terminal Ready (Off or On).
DCD Shows the status of Data Carrier Detect (Off or On).
CTS Shows the status of Clear To Send (Off or On).
RTS Shows the status of Ready To Send (Off or On).

Maintenance

Use the alarm cutoff screen to configure the operation of the external alarm contact A (Alarms)
closures at the rear of the chassis. This screen allows you to reset, enable, or disable
the external alarm contacts. O(acO)
NOTE: Alarm cut-off is not available in release 4.02

----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
Master Alarm Cut-Off
Alarm Cut-Off Mode Enabled
To configure the Alarm cut-off

1. Type your password and press [ENTER]. If the password is not entered correctly, entry is not
allowed.
2. Use the N/P keys to make your selection and press [ESC].
3. This change will not take effect until you coMmit it to the configuration. (For information about
committing changes to your configuration, see Error Checking, Saving, and Activating the
Configuration on page 3-34.)
Alarm Cut Off Mode

This field configures the external alarm contact mode of operation. Possible values:
Value Description
Enabled External alarm feature is active and alarms will activate
(default) the external alarm relays.
Disabled External alarm feature is inactive and alarm conditions
will not activate the external alarm relays.
Reset Use this setting to deactivate the external alarm relays
for the current alarm condition. If a new alarm
condition is subsequently detected, the external alarm
relay will be activated again.

Maintenance
Link Alarm History
Link Alarm History

Use the link alarm log screen to display an alarm history log for the selected link.
A (Alarms)
The alarm history log is a circular buffer containing a maximum of 400 entries. It is
used for storing alarm information. L (Linklog)
NOTE: Refresh (pressing the R key) will not update the information in the linklog screen.
You must exit and re-enter the screen to see the updates.
After a master toggle occurs, press [ENTER] for every link entry in the log to retrieve the latest alarm
history. The table below describes the fields on the link alarm log screen

----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
Link Number: 1L02 Name:
-------------------------------------------------------------------------------
13:46:19 14 Mar 2005: RED - TxD: Yel RxD: Los
11:52:11 14 Mar 2005: GREEN - TxD: Norm RxD: Norm
00:00:00 01 Jan 2000: ***** End of Log *****
To display a link, press the N/P keys to scroll up and down, and press [ENTER] on the link you want.
To exit the screen, press [ESC]. You will prompted with Erase Alarm History Log n/y? If you select Y
(yes), you must provide the superuser password. The *** End of Log *** time and date stamp reflects
the time and date of the reset. Select N to exit the screen without erasing the entries.
The table below describes the fields on the link alarm log screen.
Linklog Screen Definitions

Link Number This is a cyclical field which contains the slot and link ID of modules
installed in the chassis.
Name This is a protected field that contains the user specified name for the link.
(this name is configured on the link screen. See Specifying the Link
Parameters on page 3-16.). The remainder of this screen displays a history
log of alarm changes for the specified link.

Maintenance
History Events
History Events
Use the system event history log (Syslog) screen to display a history of system events, A (Alarms)
including configuration changes and error conditions. The system event history log is
a circular buffer containing a maximum of 400 entries. Press N/P keys to scroll up or S (Syslog)
down.

-------------------------------------------------------------------------------
----- EDIT: CFG 1 ------------------------------------------ RUN: CFG 1 -------
General System Log
-------------------------------------------------------------------------------
18:22:45 30, Nov 2004: Committed configuration 1
13:35:36 30, Nov 2004: Committed configuration 1
00:01:06 26, Nov 2004: Software versions match
00:00:47 26, Nov 2004: Power Supply B UP
00:00:47 26, Nov 2004: Power Supply A UP
00:00:34 26, Nov 2004: ***** End of Log *****
To exit the screen, press [ESC]. You will prompted with Erase Alarm History Log n/y? If you select Y
(yes), you must provide the superuser password. The *** End of Log *** time and date stamp reflects
the time and date of the reset. Select N to exit the screen without erasing the entries.
A comprehensive list of error messages you may find in the history log follows.
Error Messages
Error Message Description and Solution
******** No Framer This message is generated to indicate a module failure. If this message
Chip Detected ******** occurs, contact Carrier Access Customer Support.
Aps Failed (card#) Has This message is generated when a card has been configured in one
Wrong Signature system then placed into a new system with the previous system’s
configuration stored, and an APS is performed on the new system.
Solution: Verify that the new card(s) are configured appropriately and
perform an activate on the commit screen.
Aps Failed (card#) Timed This message is generated when a card has been instructed to perform
Out APS but does not respond to the master card.
Solution: Contact Carrier Access Customer Support.
Aps Occurred: (link ID) This message is generated when a card has been instructed to perform
change config from APS due to a failure on link #.
(config#) to (config#)
Aps Restore: (link ID) This message is generated when a card has been instructed to perform
change config back to APS due to a failure on link #.
(config#)

Maintenance
History Events
Error Message Description and Solution (Continued)

Can't allocate more than This message is generated when you attempt to connect more than 64
one time slot to Mgmt kbps to the same management port.
Port (port ID) Solution: Remove all but one of the time slots.
Clock Switch Occurred This message is generated to identify a clock switch event that has
altered the system clock.
Commit Configuration Refer to related messages in the syslog, then re-commit.
Failed
Commit Failed (card#) This message is generated when a card has been configured in one
Has Wrong Signature system and placed into another system with the previous systems
configuration stored. The message is generated during the card(s)
power up initialization.
Solution: Display the configuration to be activated on the configuration
screen to verify the configuration and perform an activate on the
commit screen again.
Commit Failed (card#) This message is generated when a card has been instructed to save and/
Timed Out or activate a configuration but does not respond to the master card.
Solution: Contact Carrier Access Customer Support.
Committed Configuration This message is used to identify which configurations have been
# activated and at what time they occurred.
Configuration did not This message is generated when module has been configured for a
match system setup specific slot and is subsequently moved to a different slot in the same
chassis.
Crossconnect Link (link This message is generated when the source and destination
ID) Slot (slot#) failed crossconnects do not match.
Solution: Check the crossconnection tables carefully on the connect
screen.
Database File Card This message is generated when a database conversion is performed
Locations (#) and specific card locations have not been converted to the new
database.
Solution: Upload the card(s) configuration to a PC and perform the
database conversion program and then reload those configurations.
Download Failed This message is generated when a configuration file older than version
2.0 is downloaded to a master module which is running version 2.0
software, and an activate is performed from the commit screen.
Solution: Upload the card(s) configuration to a PC, execute the
database conversion program and then reload those configurations.
File receive ended, card This message is generated when a file has been received properly by the
(#) unit.
File Send ended This message is generated when a file has been sent from the unit and is
completed.
File Send started This message is generated when a file send (upload) from the unit has
been initiated.

Maintenance
History Events

Invalid Passwd Entered This message is generated when an invalid password is entered.
Link (link ID) and link This message is generated when more than one link on a single card is
(link ID) are Dropped to being dropped to a single port.
port (port ID) Solution: Remove or reconfigure the drops from one of the links in
error.
Link (link ID) Slot (slot#) This message appears if a card you previously connected to was pulled
is connected to a missing from the chassis.
card (card#) Solution: Return the card to the chassis, or idle the crossconnects to the
missing card.
Links in cards (card#) and This message is generated when more than one link on multiple cards
(card#) are dropped to are being dropped to a single port.
port (port ID) Solution: Remove the drops from all but one of the links in error.
Mixed DROP and IMUX This message is generated when more than one IMUX link has Dacs
on Port (port ID) drops from a single port.
Solution: Only configure one IMUX link to handle those Dacs drops.
Port (port ID) Assigned to This message appears when a management port is connected to a
Mgmt Port (port ID) and management port and timeslot.
(port ID) Solution: Choose a connection to either a management port or a
timeslot.
Port (port ID) is configured This message is generated when only one link is defined as an IMUX.
for IMUX with only one Solution: A minimum of one DS0 on two different links must be
link configured for IMUX mode.
Power Supply Up/Down This message is generated to identify power supply failures or
vacancies.
Rack Master Switched This message is generated when a master redundancy toggle has
from (card#) to (card#) occurred.
Receive MS3 Image This message is generated when a receipt of version 2.x software is
Sanity Failure! made to a version 3.0 card. Only 3.x software will be saved to flash
memory.
Resource Allocation This message is generated when you exceed the allocated resources
conflict for Bpss Link (128 connections) across the syncbus.
(link ID) Slot (slot#) Solution: Eliminate connections until a commit can be activated.
Suggestion: move inter-card (the syncbus connections between two
cards) drops to local drops.
Resource Allocation This message appears on the drop table when the drops are incorrectly
Conflict for Drop (drop#) mapped.
Solution: Check the drops and remap them.
Resource Allocation Syncbus drops are assigned by link/timeslot. This message is generated
Conflict for Drop (link ID) when a connection is attempted to a link/timeslot across the syncbus
Slot (slot#) that has already been assigned.

Maintenance
History Events

Resource Allocation This message is generated when a conflict occurs in the management
conflict for Mgmt (mgmt tables.
ID) slot (slot#) Solution: Remap the management connections.
Resource Allocation This message is generated when the cross connect table is full.
Shortage in card (card#) Solution: Reduce the amount of connections on the card(s) in question.
If problem continues, contact Carrier Access Customer Support.
Since link (link ID) is used This message is generated when you idle out timeslot 1 (for E1) or
for IMUX channel 1 (for timeslot 2 (for T1) on IMUX defined links. Solution: Make this timeslot
E1) or 2 (for T1) must be an IMUX channel on IMUX defined links
configured as type IMUX
Slave card (card#) This message is generated when a slave card is removed from a chassis
disappeared or has stopped communicating with the master module, indicating that
the slave module is no longer available. If the module appears to be
operational but can not been seen on the master module, contact Carrier
Access Customer Support.
Slave card (card#) moved This message is generated when more than one link is dropped to a
into slot (#} single port.
Solution: Remove the drops from one of the links in error.
Slave card (card#) This message is generated when a slave card is initially installed in a
registered chassis. It indicates that the slave module is now active and ready for
configuration.
Slave module (card#) is This message is generated when a slave module has failed. It can also
absent be caused by a slave module that has been removed from the system
and you have not removed the syncbus connections to that module. In
both cases this message is generated on a system reset or power cycle.
Solution: Investigate reason for module failure or remove the syncbus
connections from the connect screen if the module is to be removed
permanently.
Software Mismatch This message indicates that the shelf master module is running version
3.51, and a slave module is operating version 3.42 or lower.
Solution: Upgrade the slave module to version 3.51.
Telnet Session Allowed This message is generated to track what IP addresses have been allowed
From x.x.x.x Telnet access to the local system and what time it occurred.
Telnet Session Closed This message is generated when you issue a control C (Ctrl C) or
performs an exit Telnet function.
Telnet Session Denied This message is generated when the disable Telnet option is active on
From x.x.x.x the Telnet screen. This message tracks what IP addresses have
attempted access to the local system and what time it occurred.
Telnet Session This message is generated when a Telnet session is terminated.
Terminated by Local User
Telnet Session Timed out This message is generated when a Telnet session times out on its own
after 10 minutes of keyboard inactivity.

Maintenance
History Events

Too Many Timeslots This message is generated when more than one timeslot is allotted to
Assigned to Fxs Port (port the FXS voice port.
ID) Solution: Remove all but one of the time slots.
Too Many Timeslots This message is generated when more than the allotted bandwidth is
Assigned to Port (port ID) being dropped to a single port.
Solution: Remove drops until the bandwidth is equal to the port speed.
Too Many TimeSlots This message is generated when too many destinations are assigned to a
Assigned to Port (port ID) single port.
Solution: Calculate the appropriate bandwidth for the port and assign
only what is allowable.
Transfer Failed on Card If this message appears, you must repeat the file transfer.
(card#) after (# of bytes)
error (error code)
Transfer Rx Failed card This message is generated when the receiver of the transfer has timed
(card#) timed out out.
Transfer to card (card#) This message is generated with a successful transfer to the specific card
completed successfully number.
Transfer Tx Failed card This message is generated when the transmitter of the file selected has
(card#) timed out timed out.
Transfer type file This message is generated when a file transfer from the master to a
(filename.ext) to card slave card is activated. It indicates the specific file being sent.
(card#) started
Voice Compression This message is generated during power up and is only valid for
Hardware Ram ERROR TRANSmaster modules. It indicates that the self test on the
compression hardware has failed, and that compression reliability is no
longer guaranteed. Solution: Contact Carrier Access Customer
Support. Have ready your serial number and revisions which can be
obtained from the version screen.
Warm reset of card This message is generated when a card in the system has been
(card#) Performed instructed to warm reset.

Maintenance
The MASTERseries application modules support both near and far end performance monitoring
(PMON) capabilities on T1 ESF links compliant using ANSI T1.403 or AT&T TR 54016 protocols.
Near end performance monitoring capabilities are also implemented on T1 SF (D4) and E1 links.
NOTE: Performance monitoring is disabled by default. Enable it from the link screen. For
more information about the link screen refer to Specifying the Link Parameters on
page 3-16
The performance monitoring software collects performance parameters in one-second increments. The
performance data is organized and stored for the following intervals:
Current second
Previous second
Current 15 minutes
Previous 15 minutes
Current 24 hours
Current 48 hours
Current 72 hours
The current second and previous second displays provide a dynamic view of errors as they occur. These
errors then move into the current 15-minute period (900 seconds).
The current 15-min display dynamically updates as performance data is being collected in the current
interval. When the interval is complete the data moves to the Previous 15-min display and the most
recent 15- minute interval and the current interval restart.
The current 24-hr, current 48-hr, and current 72-hr summary displays have a maximum count of 65,535
errors and are based on a sliding window of 15-minute intervals. So the current 24-hr report is an
accumulation of the previous ninety-six 15-minute intervals, current 48-hr is an accumulation of the
previous 192 intervals, and current 72-hr is an accumulation of the previous 288 intervals. The long
report shows the same information as the short report and also includes the performance data for each
complete 15-minute interval in the current 24 hour window. Each time an interval is completed previous
intervals scroll down one in the list.

Maintenance
Performance Monitoring Statistics

For each interval, six types of performance statistics are measured. These statistics are described in the
following table.
Performance Monitoring Statistics

EE This field shows the number of Error Events (EE) that have occurred up to a
maximum of 65,535. If a link uses ESF framing, the following error conditions cause
a single EE to be counted: a transition to an LOS, or OOF, or AIS condition, a CRC-6
error, or a controlled slip (also referred to as a frame slip). If a link uses SF framing
then an EE is a BPV or a transition to an LOS, or OOF or CSS condition. If a link is
E1-CRC4 then an EE is a CRC-4 error or a transition to an LOS, or OOF condition.
NOTE: A single LOS, AIS, or OOF condition counts as a single EE, independent of
how long it lasts.
ES An Errored Second (ES) is a second that is not a UAS, with one or more EEs.
UAS The Unavailable Seconds (UAS) field is a count of one-second intervals during which
service is unavailable. A UAS is declared when ten consecutive SESs occur. The ten
SESs are subtracted from the SES count and added to the UAS count. Subsequent
seconds are added to the UAS count until the UAS state is cleared. The UAS state is
cleared when ten consecutive non-SESs occur. When the UAS state clears, the ten
consecutive non-SESs are subtracted from the UAS count.
SES A Severely Errored Second (SES) for an ESF link is a second that is not a UAS with
320 or more EEs, or one or more LOS, AIS, or OOF conditions. An SES for an SF
link is a second that is not a UAS with 1540 or more EEs, or one or more LOS, AIS,
or OOF conditions. An SES for an E1 link is a second that is not a UAS with 320 or
more EEs, or one or more LOS, AIS, or OOF conditions.
BES A Bursty Errored Second (BES) for an ESF link is a second that is not a UAS, and
contains more than one but less than 320 CRC-6 errors and NO LOS, AIS or OOF
conditions. A BES for an SF link is a second that is not a UAS, and contains more
than one but less than 1540 BPVs and NO LOS, AIS or OOF conditions. A BES for
an E1 link is a second that is not a UAS, and contains more than one but less than 320
CRC-4 errors and NO LOS, AIS or OOF conditions.
CSS A Controlled Slip Second (CSS) is any second that is not a UAS that contains one or
more controlled slips. A CSS (also referred to as a frame slip) occurs when there is a
difference of exactly one frame between the transmitted and received data streams,
resulting in the replication or deletion of a DS1 frame by the receiving terminal.
NOTE: If pressing the R key does not refresh the screen, press [ESC] once or twice. The
PMON screen does not refresh the Current 24, 48, and 72 hour summaries. Press [ESC]
to exit the screen and re-enter.

Maintenance
Displaying the Local Performance Statistics

Use the local performance statistics screen to display performance A (Alarms)
monitoring statistics for links with performance monitoring enabled.
Performance monitoring is enabled using the protocol field on the link screen P (Performance)
menu. L (Local_stats)

Local_stats reMote_stats Definitions
----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
Link => 1L01 Report_Type => UNSR
Protocol => T1_403 Name =>
Frame => T1 ESF Comp Intv=> 08 of 96
Interval EE ES UAS SES BES CSS

---------- ------ ------ ------ ------ ------ ------
Cur second 1 0 1 0 0 0
Pre second 1 0 1 0 0 0
Cur 15-min 525 0 525 0 0 0
Pre 15-min 900 0 900 0 0 0
Cur 24-hr 7200 0 7200 1 0 0
Cur 48-hr 7200 0 7200 1 0 0
Cur 72-hr 7200 0 7200 1 0 0
To View the Local_stats report:

1. Verify that performance monitoring is enabled. Performance monitoring is enabled on the link
screen. For more information about the link screen refer to Specifying the Link Parameters on
page 3-16. For the link you want to monitor, go to the link screen (Link). Ensure that the
Protocol field is active with a selected protocol.
T1.403 enables the unit to operate in PRM mode, updating local and remote statistics every
second.
54016 enables the unit to operate in FDL mode, updating local statistics every second and
remote statistics every 4 minutes.
PMON_D4 enables performance collection to operate in SF mode, local statistics only.
2. Select the link ID by typing the ID or using the N/P keys, then [ENTER].
3. Select UNSR or UNLR and press [ENTER]. (For descriptions of these reports, see the table
below.)
4. Press [ESC] to leave the screen. The Erase Near End PM Data n/y? prompt appears. To erase
the local performance monitoring statistics counters of the specified link press Y for yes. To
exit the screen without erasing performance monitoring data press N or [ESC]. If yes is
selected, you must enter the superuser password.

Maintenance
The following table describes the fields on the local performance statistics screen:
Local Statistics Screen Definitions

Link Identifies the link. Cycle through using the N/P keys.
Report Use the N/P keys to select the type.
Type UNSR—(User Network Short Report) Displays statistics for the following
intervals: current second, previous second, current 15-minute, previous
15-minute, current 24 hour, current 48 hour and current 72 hour summaries.
UNLR—(User Network Long Report) Displays statistics for a running 24 hour
period in ninety six 15-minute intervals. (T1 ESF only.)
Protocol These are protected fields which reflect the configuration in the link screen.
Frame
Name
Completed This is a protected field that displays the number of 15-minute performance
Intervals monitoring intervals that have been completed. Unless the MASTERseries unit
(Comp was restarted within the last 24 hours, the completed intervals field will count
Intv) up to 96 and remain at 96.
15-Minute Four 15-minute intervals are displayed at the bottom of the long report screen
Intervals (UNLR). Each 15-minute interval has an interval number and a time stamp.
Remote Performance Statistics

Use the remote performance statistics screen to show the performance
A (Alarms)
monitoring statistics for the far end of a link that has been configured
for T1_ESF framing and the performance monitoring protocol set to P (Performance)
AT&T_54016 or T1_403. Both of these fields are found in the link M (reMote_stats)
screen. This screen is updated every four minutes for links configured S (Show_remote_stats
for AT&T_54016. It is updated every second for links configured for
T1_403.

Show_remote_stats send_reMote_msg
----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
Link => 1L01 Report_Type => FESR
Protocol => T1_403 Name =>
Frame => T1 ESF Far Intv => 00
PRM loss => 000
Interval EE ES UAS SES BES CSS
---------- ------ ------ ------ ------ ------ ------
Cur 15-min 0 0 0 0 0 0
Pre 15-min 0 0 0 0 0 0
Cur 24-hr 0 0 0 0 0 0

Maintenance
To View the show_remote_stats report:

1. Select the link ID requested in the link field by typing the ID or using the N/P keys, then
[ENTER].
2. Select FESR or FELR, and press [ENTER].
3. To clear the performance monitoring data: select the desired link and press [ESC]. Erase Far
End PM Data: n (no) / y (yes) is presented at the bottom of the screen. Press N or Y, then
[ENTER]. If yes is selected, you must enter the superuser password.
The fields on the remote performance statistics screen are described in the table on the next page.
Show Remote Statistics Screen Definitions

Link Identifies the link. Cycle through using the N/P keys.
Report Type Use the N/P keys to select the type.
FESR—(Far End Short Report) TDisplays statistics for the far end: current
15-minute, previous 15-minute and current 24 hour statistics.
FELR—(Far End Long Report) Displays the 96 far end interval statistics
and totals.
Frame
Name
Far End This is a protected field that displays the number of far end 15 minute
Completed intervals that have been completed.
Intervals
(Far Intv)
Performance This is a protected field that is displayed when the T1.403 protocol has been
Report selected on the link screen. The PRM is received once per second from the
Message reporting far end. If the message is not received this counter will advance by
(PRM) Loss one.

Maintenance
Individual Performance Statistics

Use the remote performance statistics request screen to send a message A (Alarms)
to the far end to request individual statistics. The link must be
configured as AT&T_54016 using the protocol field in the link screen. P (Performance)
M (ReMote_stats)
M (send_reMote_ msg)

Show_remote_stats send_reMote_msg
----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
Link => 1L02 | Protocol => ATT_54016 | Frame => T1 ESF
64 : Send 1-Hour Performance Data
67 : Send Errored ESF Data
100 : Send 24-Hour ES Performance Data
101 : Send 24-Hour UAS Performance Data
103 : Send Enhanced 1-Hour UAS Performance Data
107 : Send Enhanced 24-Hour ES Performance Data
108 : Send Enhanced 24-Hour UAS Performance Data
109 : Send Enhanced 24-Hour BES Performance Data
110 : Send Enhanced 24-Hour SES Performance Data
111 : Send Enhanced 24-Hour CSS and LOFC Performance Data
231 : Send Enhanced CI Configuration Data
66/194 : Reset Remote Performance Monitoring Counters
68/196 : Reset Errored ESF Data
Message =>
Send Message =>
The following table describes the fields on the remote performance statistics request screen:
Send ReMote Message Screen Definitions

Link This is a cyclical field which contains the slot and link ID of the modules
installed in the chassis. When you have displayed the desired link, press
[ENTER].
Frame
Name
Send Message This is a cyclical field (Yes/No) which controls sending the message. The
message is sent each time you press [ENTER] if yes is selected. No message
is sent if no is selected.

Maintenance

Use the help screen to list the keyboard functions and commands for navigating through H (Help)
the menus and fields.

------------------------------- CACMasterSeries -------------------------------
----- EDIT: CFG 3 ------------------------------------------ RUN: CFG 3 -------
n or space bar : Select next menu option

p or alt-space : Select prior menu option
r : Refresh screen
Arrow keys : Go to next field
Esc : Return to the command menu line

Enter : Select menu option
BackSpace: Delete one character

Maintenance

Use the send linklog screen to save a copy of the general system log to a text file (.txt). S (Setup)
Downloading logs is helpful for troubleshooting or technical support. Superuser
password required. The alarm information put into this text file will be in the order that L (sendL)
the alarms were generated.
To send a copy of the linklog and syslog to a text file on your pc:
1. In the sendL screen press [ENTER] and type in your password.
Super user access is required. If the password is not entered correctly, read-only access is
provided.
2. Press [ENTER] to get the Confirm prompt. Choose Y to save the file log or N to cancel and
press [ENTER].
3. After you have confirmed the file upload, a second screen, appears. This screen indicates that
the log has been saved as a text file. Press [ESC] to leave this screen.
4. Navigate to the CLI: Setup > mGmt > CLI.

Maintenance
Uploading the log file

The saved log file, called almsys.txt, is accessible via the CLI.
Command Description
Open your TFTP program, and leave running in the background
/# cd system Change from Root mode to System mode
/system# show files Displays the current running and backup files.
/system# file-upload {name} Initiates a file upload of the log file.
ipaddr {ip addr} [destfile
{name}]
Example
/# cd system
/system# show files
---------------- ------------
ds11.cfg 38 bytes
ds12.cfg 38 bytes
.
.
.
aoc7.cfg 1128 bytes
aoc8.cfg 1128 bytes
sys.cfg 33 bytes
flash 272627 bytes
backup.mgh 2641067 bytes
jan26log.txt 1027 bytes
almsys.txt 399 bytes
/system# file-upload almsys.txt ipaddr 192.168.1.158

Uploading almsys.txt to TFTP server 192.168.1.158
.
Upload Complete
/system#

Maintenance

Use the file-upload command to upload the configuration files from a MASTERseries module to a PC
for the purpose of backup storage.
1. Connect to the FLEXmaster. Connect the network management cable (provided with your
FLEXmaster equipment) to the RS-232 port on your PC and the NMS port on the FLEXmaster
module. For more information about connecting see details see Local Access to the
FLEXmaster on page 3-12.
Command Description
/system# file-upload {name} Initiates a file upload of the log file.
{name}]
Example
/# cd system
/system# show files
---------------- ------------
ds11.cfg 38 bytes
ds12.cfg 38 bytes
.
.
.
aoc7.cfg 1128 bytes
aoc8.cfg 1128 bytes
sys.cfg 33 bytes
flash 272627 bytes
jan26log.txt 1027 bytes
almsys.txt 399 bytes
/system# file-upload ds11.cfg ipaddr 192.168.1.158

Uploading ds11.cfg to TFTP server 192.168.1.158
.
Upload Complete
/system#

Maintenance

Use the file-download command to download software or configuration files. The following are the
recommended processes for loading software on the FLEXmaster. For more information, regarding
the commands, see Chapter 4, CLI Commands.
Dowloading Application Files

Command Description
/system# file-rename {name} Rename the current application file to keep as a backup.
{name}
/system# file-download {name} Initiates a file download of the application file.
{name}]
/system# /exit Returns the user to the TUI.
TUI
Diag > Warmreset Reboots the module with the new application. Validate new
software version is displayed upper right corner of the TUI.
Example
1. From the CLI issue the following commands
/# cd system
/system# show files

HLink.mgh 43597 bytes
flash 278182 bytes
/system# file-rename vxWorks.mgh backup.mgh
/system# file-download vxWorks.mgh ipaddr 192.168.1.158
/ Downloading vxWorks.mgh from 192.168.1.158
...........................
Download Complete

Maintenance
/system# show files

---------------- ------------
HLink.mgh 43597 bytes
flash 278182 bytes
/system# exit
2. From the TUI go to Diag > Warmreset. Warm reset the module.
3. Validate the new software version is displayed upper right corner (Main Menu)
Downloading Configuration Files

Use the file-download command to download configuration files. The following is the
recommended process for loading configurations on the FLEXmaster. For more information,
regarding the commands, see Chapter 4, CLI Commands.
Command Description
/system# file-delete {file- Deletes the specified file from memory.
name}
/system# file-download {name} Initiates a file download of the application file.
{name}]
/system# /exit Returns the user to the TUI.
TUI
Diag > Warmreset Reboots the module with the new application. Validate new
software version is displayed upper right corner of the TUI.
NOTE: The configurations are stored in a file named “flash”.

Maintenance
Example
1. From the CLI issue the following commands
/# cd system
/system# show files

---------------- ------------
hlink.mgh 43715 bytes
vxworks.mgh 2641102 bytes
flash 271352 bytes
/system# file-delete flash

File deleted
/system# file-download flash ipaddr 192.168.2.105

Downloading flash from 192.168.2.105
..
Download Complete
/system# show files

---------------- ------------
hlink.mgh 43715 bytes
vxworks.mgh 2641102 bytes
flash 272083 bytes
2. From the TUI go to Diag > Warmreset. Warm reset the module.
3. Validate the new software version is displayed upper right corner (Main Menu)

Maintenance

CHAPTER
8
Troubleshooting
In this Chapter
Overview
Interpreting Alarm indications
Removing and Replacing Modules
Diagnosing a Fault
Loopback Test Paths
Configuration
Overview
Overview
This chapter describes the troubleshooting process for isolation and resolution of a fault in a network
associated with MASTERseries application modules. The troubleshooting process consists of visual
inspection, interpreting alarms, executing test procedures, and using a logical process of elimination to
isolate a fault, resolve the fault, and restore proper operation to the network. The hypothetical network
illustrated in this document is a simple example of one application, and the troubleshooting techniques
are general. Use the techniques and examples described here to develop a strategy for your specific
network application.
Interpreting Alarm indications

Red Alarm
Yellow Alarm
Trunk Conditioning
AIS Blue Alarm Propagation
The alarm indications of MASTERseries help to identify symptoms of problems in the network. The
unit displays several alarm conditions to indicate operational status of the T1/E1 links and the associated
channels. For the purposes of the alarm descriptions, each T1/E1 link consists of a transmit path and a
receive path being sent independently in opposite directions from the central office to the end point.
Each of the basic default alarm states are described in the following paragraphs and illustrated in the
following figure.
Central End
Office Point MASTERseries Blue
Red
Alarm Alarm
(AIS)
T R T R
Xmit X Rcv Xmit
T1/E1 Link T T1/E1 Link
Rcv Xmit Rcv
R T
R
Yellow
Alarm
The blue alarm (AIS) is indicated only when
PBX channels are bypassed to another T1/E1 link.
If any channels in the data stream are bypassed
to another link, the AIS will not be indicated.
Red Alarm
If one path of a T1/E1 link is broken (as indicated by the X in the figure above), the received signal is
lost at the receive end point, causing a red alarm at the receive end point.

Configuration
Yellow Alarm
When the received signal is lost at the receive end point, the receive end point will signal through its
transmit side that a Loss of Signal (LOS) condition has been detected, causing a yellow alarm to be
indicated at the central office, or other end point.
Trunk Conditioning
In addition to the yellow alarm at the central office, any T1/E1 port which receives a yellow alarm also
indicates a trunk condition in the DS0 channels for any lines or trunks that are connected to the affected
T1/E1 line. The PBX connected to an affected trunk at the central office will receive a trunk condition
indication. Upon receipt of the trunk condition, the PBX will then go out of service, or re-route its traffic
to another available T1/E1 link, if so equipped.
AIS Blue Alarm Propagation

The MASTERseries application modules support the blue alarm signaling convention which is user
configurable and is used to indicate that the associated T1/E1 link is disabled due to a problem beyond
the blue alarm end point, as shown in the following figure. However, if any DS0 channels are dropped
from a point in the T1/E1 link which is disabled, the blue alarm is not indicated beyond that node.
During a T1/E1 link outage, operational points in the T1/E1 link around the fault are in blue alarm,
except for the links on opposite sides of the fault; the transmit and receive sides of the fault are
respectively in yellow alarm and red alarm. This alarm color coding helps to isolate faults in T1/E1
links.
Blue Blue Blue

Alarm Alarm Alarm
(AIS) (AIS) (AIS)
Yellow Alarm Yellow Alarm

Yellow Alarm

WARNING! THE MASTERSERIES APPLICATION MODULE IS SENSITIVE TO ELECTROSTATIC
DISCHARGE (ESD) AND SHOULD NEVER BE REMOVED FROM THE CHASSIS WITHOUT PROPER USE
OF A GROUNDING WRIST STRAP ON A GROUNDED ANTISTATIC MAT. IMPROPER HANDLING CAN
CAUSE DAMAGE AND VOID YOUR WARRANTY.
All application modules are removable and replaceable without disruption to system performance (hot
swappable). After hot swapping a module, there can be up to a one minute delay before the master
module reports the slave module as active or removed. After a module has been configured, if it is

Configuration
Diagnosing a Fault
moved to a different location (that is, a different slot, or a different shelf), the configuration will be
defaulted to a new configuration. If the module is moved back before doing a commit (see Error
Checking, Saving, and Activating the Configuration on page 3-34), the original configuration will be
restored. If the module remains in the new location, a new configuration can be entered or a saved
configuration can be downloaded.
NOTE: If a module is removed from the chassis, a red alarm will occur indicating a card
is missing. If the module is being removed and will not be replaced, then disable links
before removing the module and no alarm condition will be generated.
NOTE: Master/Slave functionality is not supported in FLEXmaster 4.02
Diagnosing a Fault
Fault diagnosis consists of isolating a fault by process of elimination. The technique of signal loopback
is used to isolate faults to specific areas of the network.
Preliminary Checks
Prior to the start of fault analysis, the following preliminary checks should be performed:
Visually inspect the integrity of connections, such as data device cables, telephone cables (T1/
E1 lines), and power and ground connections.
Observe the status of front panel indicators.
Fault Analysis
Faults in the network are isolated by performing a sequence of tests and checks. Using the loopback
charts (Troubleshooting Flow Charts on page 8-5) the fault can be identified as existing in one of the
following areas:
Local data device
Local data device cable
Local MASTERseries module
Telephone lines (T1/E1 link)
Remote module
Remote data device cable
Remote data device

Configuration
Loopback Test Paths
Loopback Test Paths

The MASTERseries offers a variety of loopback paths to isolate faults in the network (see Chapter 6,
Diagnostics). Use these techniques and examples to develop a strategy for your specific network
application.
Fault Isolation
Loopback testing is used to verify elements of a network by sending test patterns through the network
to specific nodes where the data can be looped back and checked for errors. When using loopback
testing to isolate faults, the system can be partitioned into fewer elements until the fault is isolated.
A fault can be isolated by first initiating loopback tests and sending test patterns through the nearest
nodes in the network, then working outward toward the end nodes. The fault can be isolated as lying at
the point in the network between where the nearer node loopback test passes, and the farther node
loopback test fails.
The link and port loopback tests are described in detail in Chapter 6, Diagnostics. These loopbacks can
be initiated using the system console or using in-band command codes.
Troubleshooting Flow Charts

This section shows three troubleshooting flow charts to help isolate faults in a hypothetical system
application. These flow charts are divided into three categories:
Local Site Single Channel Problem—A problem is associated with a single channel timeslot.
All Links and Ports Problem—A problem is common to links or ports associated with the unit.
Local Site Link or Port Problem—A problem is detected at a local site which appears to be
isolated to one port or link.

Configuration
Loopback Test Paths
Local Site Single Channel Problem
At local site, one

channel has a problem
Initiate timeslot
loopback test for
affected channel
Test results Replace engine

No
O.K. module at local site
Yes
Initiate timeslot
loopback test for
affected channel
Done—no fault found in unit.
Check external data devices
and cables.
Test results Contact sales/service

No
O.K. representative
Yes
Done

Configuration
Loopback Test Paths
All Links and Ports Problem
All links and ports

have a problem
Initiate
preoperational
check
Replace power Test results

No
supply O.K.
Initiate
preoperational check Yes
Test results No Replace interface

O.K. adapter module
Yes
Initiate
preoperational
Done check
Test results Yes Done

O.K.
No
Replace engine
module
Initiate
preoperational
check

O.K.
No
Contact sales/service
representative

Configuration
Loopback Test Paths
Local Site Link or Port Problem
At local site, one link

or port has a problem
Port problem
or link?
Port
Initiate port
local loopback
test
Link
Test results No Replace engine
O.K. module
Initiate port
Yes
local loopback
test
Initiate
equipment
loopback test Contact sales/
Test results No service
O.K. representative
Replace engine No Test results
module O.K. Yes
Initiate Done
Yes
equipment
loopback test
Initiate
network
loopback test
Contact sales/ No Test results
service O.K.
representative Replace engine
Test results No
O.K. module
Yes
Done Yes Initiate network

loopback test
Initiate line
loopback test
at remote site
Contact sales/
Test results No service
O.K. representative
CONTINUED
ON
NEXT PAGE Yes
Done

Configuration
Loopback Test Paths
Local Link or Port Problem: Troubleshooting Flow Chart (Sheet 2 of 2)
Continued from
Previous Page
Replace interface
Test results adapter module
No
O.K. at remote site
Yes Initiate line

loopback test
Initiate port
at remote site
remote
loopback test

O.K.
No
Replace engine
module
at remote site
Initiate line
Replace engine loopback test
module at remote No Test results at remote site
site O.K.
Initiate port
remote Test results Yes Done
loopback test O.K.
No
Contact sales/ No Test results
service O.K.
Yes Link or cable fault.
representative
Replace link or
cables between
Yes
local and remote sites
Done
Done—no
fault found

Configuration
Loopback Test Paths

APPENDIX
A
Data Port Interfaces
In this Appendix
Adapter Cables
Network Management Cable
Configuration

The MASTERseries application modules are available with either a V.35 data port interface or an
RS530-A data port interface. The pinouts of these interfaces and available cable adapters are specified
in this appendix.
V.35 Data Ports
Connector Female, DB-25—Adaptable to standard V.35 connector with cable
adapter (DB25 male to 34 pin Winchester female)
Electrical Meets V.35 specification
Type DCE (Data Circuit-terminating Equipment)
V.35 Pin Assignments
CCITT 25 Pin D 34 Pin Circuit Name Source
1 A Protective GND
102 7 B Signal GND
105 4 C RTS DTE
106 5 D CTS DCE
107 6 E DSR DCE
108.2 20 H DTR DTE
109 8 F DCD Rec Line Det DCE
103a 2 P Tx Data A DTE
103b 14 S Tx Data B DTE
104a 3 R Rx Data A DCE
104b 16 T Rx Data B DCE
113a 24 U External Clk A DTE
113b 11 W External Clk B DTE
142 25 NN Test Mode DCE
114a 15 Y Tx Signal Timing A DCE
114b 12 AA Tx Signal Timing B DCE
115a 17 V Rx Signal Timing A DCE
115b 9 X Rx Signal Timing B DCE
A-2 FLEXmaster - Release 4.02

Configuration
RS530-A Data Ports

Connector Female, DB-25—adaptable to standard V.35 connector with cable
adapter (DB25 male to 34 pin Winchester female)
Electrical This interface complies with ANSI/TIA/RS530-A-A-1992 (V.36). The
electrical characteristics of this interface are specified by:
Category 1—EIA-422-A, Balanced Voltage Digital Interface Circuits
Category 2—EIA-423A, Unbalanced Voltage Digital Interface Circuits
RS530-A Pin Assignments
CCITT 25 Pin D Circuit Category Circuit Name Source
Mnemonic
1 A Protective GND (Shield)
102 7 AB Signal GND
105 4 CA (A) 1 RTS DTE
19 CA (B)
106 5 CB (A) 1 CTS DCE
13 CB (B)
107 6 CC 2 DSR DCE
108.2 20 CD 2 DTR DTE
109 8 CF (A) 1 DCD Rx Line Sig Det DCE
10 CF (B)
103a 2 BA (A) 1 Tx Data A DTE
103b 14 BA (B) Tx Data B
104a 3 BB (A) 1 Rx Data A DCE
104b 16 BB (B) Rx Data B
113a 24 DA (A) 1 External Clk A DTE
113b 11 DA (B) External Clk B
114a 15 DB (A) 1 Tx Signal Timing A DCE
114b 12 DB (B) Tx Signal Timing B
115a 17 DD (A) 1 Rx Signal Timing A DCE
115b 9 DD (B) Rx Signal Timing B
141 18 LL 2 Local Loopback DTE
140 21 RL 2 Remote Loopback DTE
125 22 CE 2 Ring Indicator DCE
102 23 AC Signal Common
142 25 TM 2 Test Mode DCE
FLEXmaster - Release 4.02 A-3

Configuration
Signal Definitions
Signal Ground Directly connects the DTE circuit ground to the DCE circuit ground to
provide a conductive path between the DTE and DCE signal commons.
Control Signal Definitions
The MASTERseries application module is a DCE with control signal outputs of: CTS, DSR,
and DCD. The input control signals are: RTS and DTR. The receiver for each control signal
shall interpret the situation where the control is not implemented or connected as an OFF
condition.
Data Terminal The DTR control is monitored by the DCE and is reflected on DSR.
Ready If data is being dropped to the DCE port and the cable is not connected,
(DTR, 108.2) then the data output to the network interface will be ones.
Data Set Ready Set on by the DCE to signal that the DCE is ready to receive data
(DSR, 107) PATHmaster/TRANSmaster/DATAmaster/LINKmaster/CLOCKmaster
modules—DSR follows DTR.
BANDmaster module—DSR follows DCD.
Request To Send This control is used by the DTE to condition the DCE for data
(RTS, 105) transmission. The RTS control is monitored by the DCE and reflected on
CTS.
Set ON by the DTE to indicate to the DCE that it is ready to transmit.
Set OFF by the DTE to indicate to the DCE that it has no data to transmit
Clear To Send This control indicates that the DCE is ready to receive data
(CTS, 106) On the PATHmaster/TRANSmaster/DATAmaster/LINKmaster/
CLOCKmaster CTS follows RTS.
On BANDmaster modules CTS follows DCD.
Received Line This control indicates whether the DCE is ready to receive data
Signal Detector Set on when channels are assigned to the data port and the T1 link the port
(DCD, 109) is connected to is green.
On MASTERseries modules: DCD is set off when channels are not

assigned to the data port or the link the port is connected to is not green.
On BANDmaster modules. There are two special cases:

If Fallback is off: then DCD is set off when any of the T1 links the port is
connected to are not green.
If Fallback is on: Then DCD will remain on and the data port will rate
adapt as long as at least one or more of the T1 links the port is connected to
is green. DCD is set off when all of the T1 links the port is connected to are
in an alarm condition.

Configuration
Signal Definitions (Continued)

Timing Signal Definitions
Transmit Signal Signals on this circuit provide the DTE with transmit clocking.
Element Timing Off to on—The DTE uses the off to on transition of this timing element to
(DB/114) clock data on the transmit data circuit.
Receiver Signal Signals on this circuit provide the DTE with receive clocking. This will be
Element Timing a smooth clock without gaps.
(DD/115) On to off—The on to off transition shall indicate the center of each binary
element on receive data.
External Clock Signals on this circuit provide the DCE with transmit clocking.
A (DA/113) On to off—The on to off transition shall indicate the center of each binary
element on transmitted data.
OPTIONS—
1. External clock selected—The on to off transition of the external clock
input (DA) is used to clock transmit data into the DCE.
2. Internal clock selected—The DCE input clock is not used to clock
transmit data into the DCE, instead the on to off transition of the Transmit
Signal Element Timing (DB) is used.
Data Signal Definitions
Received Data Data signals generated by the DCE and clocked out on the OFF to ON
(BB/104) transition of Receiver Signal Element Timing to the DTE.
Transmitted Data signals generated by the DTE and transmitted to the local DCE.
Data
(BA/103)
Ring Indicator This control is always set off by the Carrier Access DCE.
(RI, 125)
Diagnostics
The following data port pins are not currently supported. Port diagnostics including local and
remote port loopbacks are supported through the network management interface.
Local Loopback Local port loopbacks are only supported through the Carrier Access
(LL/141) network management interface. When a local port loopback is performed
to the TELEport, the telephone will ring.
Remote Remote port loopbacks are only supported through the Carrier Access
Loopback network management interface.
(LL/140)
Test Mode This control is always set off by the Carrier Access DCE.
(TM/142)

Configuration
Adapter Cables
Adapter Cables
The following table describes the pin assignments for the RS530-A to RS449 adapter cable. Pins
grouped together indicate twisted pair.
RS530-A DCE to RS449 DTE Interconnection Cable
RS530-A Signal DB-25 Male DB-37 EIA-449 Signal
Name DCE Pin No. Pin No. Name DTE
Shield 1 1 Shield
TDA 2 4 Send Data
TDB 14 22
RDA 3 6 Rx Data
RDB 16 24
RTS A 4 7 RTS
RTS B 19 25
CTS A 5 9 CTS
CTS B 13 27
DSR A 6 11 Data Mode
DSR B 23 29
DTR A 20 12 Term Rdy
DTR B NC 30
SG 7 19 Signal Ground
DCD A 8 13 Rx Rdy
DCD B 10 31
TSET A 15 5 Tx Timing
TSET B 12 23
RSET A 17 8 Rx Timing
RSET B 9 26
LL 18 10 LL
RL 21 14 RL
XTC 24 17 Term Timing
11 35
TM 25 18 TM
Signal Common AC 23 20 Receive Common

Configuration
Adapter Cables
The following table describes the RS530-A to X.21 adapter cable. Pins grouped together indicate
twisted pair.
RS530 to X.21 Interconnection Cable
RS530-A Signal DB-25 Male DB-15 Female X.21 Signal Name
Name Pin No. Pin No.
Shield 1 1 Shield
TDA 2 2 Tx Data
TDB 14 9
RDA 3 4 Rx Data
RDB 16 11
RTS A 4 3 Indication
RTS B 19 10
CTS A 5 5 Control
CTS B 13 12
RSET A 17 6 Rx Sig Element
RSET B 9 13 Timing
NC 7, 14, 15 Unassigned
The following table describes the RS530-A to RS232 cable pin assignments. Pins grouped together
indicate twisted pair.
RS530-A (DCE) to EIA-232 (DTE)
Non-Powered Interface Converter Cable
RS530-A Signal DB-25 Male DB-25 Female EIA-232 Signal Name
Shield 1 1 Protective Ground
RTS A 4 4 Request to Send
RTS B 19 R-Gnd
CTS A 5 5 Clear to Send
CTS B 13 R-Gnd
DSR A 6 6 Data Set ready
DSR B 22 R-Gnd
DTR A 20 20 Data Terminal Ready
DTR B 23 R-Gnd
DCD A 8 8 Received Line Signal
DCD B 10 R-Gnd Detector

Configuration
RS530-A (DCE) to EIA-232 (DTE)

Non-Powered Interface Converter Cable (Continued)
TSET 15 15 Tx Signal Element
12 R-Gnd Timing (DCE Source)
RSET 17 17 Rx Signal Element
9 R-Gnd Timing (DCE Source)
XTC 24 24 Tx Signal Element
11 R-Gnd Timing (DTE Source)
TDA 2 2 Transmitted Data
TDB 14 R-Gnd
RDA 3 3 Received Data
RDB 16 R-Gnd
LL 18 NC Unassigned
RL 21 NC Signal Quality
Detector
TM 25 25 Unassigned

The following table specifies the pinout for Carrier Access’ network management interface. This is a
typical configuration for a standard null modem cable and will operate in PPP or console mode.
Carrier Access’ Network Management System (NMS) Cable
PC Com Port Signal DB-9 Female RJ-45 Male NMS Signal Name
DCD/DTR/DSR 1 to 4 to 6 NC Controls
RXD 2 2 Tx Data
TXD 3 3 Rx Data
GND 5 5 Ground
RTS 7 to 8 NC
CTS 8 to 7 NC
RI NC NC

APPENDIX
B
SNMP Trap List
In this Appendix
SNMP Trap List
SNMP Trap List
SNMP Trap List
SNMP Trap List

The following table lists the SNMP traps.
Trap Name Generic Specific Description Variable Variable Comments
Trap # Trap # Binding 1 Binding 2
Link Down 2 2 The DS1 link or the Index Msg (STRING) Major: Red OOF,
Management Interface (INTEGER) “1LA” or “6LC” or Red LOS, Red
has changed its state “3M1” OOMF, Yellow,
from green to red AIS, Red UAS
Threshold
Link Up 3 3 The DS1 link or the Index Msg (STRING) Informational

Management Interface (INTEGER) “1LA” or “6LC” or
has come up “3M1”
Authentica- 4 4 An erroneous None None Informational

tion Failure community name has
been received
Card In 6 2 A new card has Msg None Informational

reported to the master (STRING) “Slot 1” or “Slot 2”
card
Alarm 7 7 System is still in alarm Msg None Informational

(STRING)
B-2 FLEXmaster - Release 4.02

GLOSSARY
Glossary
10Base-T The most widely installed Ethernet local area networks (LANs) use ordinary telephone
twisted-pair wire. When used on Ethernet, this carrier medium is known at 10BASE-T.
10BASE-T supports Ethernet’s 10 Mbps transmission speed.
100Base-T Also called "Fast Ethernet," it is a 100 Mbps version of Ethernet. 100Base-T transmits at
100 Mbps rather than 10 Mbps. Like regular Ethernet, Fast Ethernet is a shared media LAN.
All nodes share the 100 Mbps bandwidth. 100Base-TX uses two pairs of Category 5
cabling, one pair for transmission, one pair for receiving.
AC Alternating Current.
Adapter The adapter module is the I/O module and is the rear portion of the MASTERseries units.
Module
Address A coded representation of the origin or destination of data.
ADPCM Adaptive Differential Pulse Code Modulation. A speech coding method which uses fewer
bits than the traditional PCM (Pulse Code Modulation). ADPCM allows encoding of voice
signals in half the space PCM allows.
AIS Alarm Indication Signal (blue alarm). All ones—used as keep-alive signal. Propagates
through a T1 link network to indicate a link outage.
Alarm Instantaneous alarm event.

Condition
Alarm State An alarm condition that has been integrated over time to an Alarm State.
AMI Alternate Mark Inversion. Line coding pattern used in T1 spans.
ANSI American National Standards Institute.
APS Automatic Protection Switching.
ARP Address Resolution Protocol. A method for finding a host’s Ethernet address from its
Internet address. The sender broadcasts an ARP packet containing the Internet address of
another host and waits for the second host to send back its Ethernet address. ARP is defined
in RFC 826.
Glossary
B8ZS Binary Eight Zero Suppression is a technique in T1 that modifies the AMI encoding to
ensure minimum pulse density without altering customer data. When eight "zeros" in a row
are detected, a pattern with intentional bipolar violations is substituted. These violations
enable the receiving end to detect the pattern and replace the "zeros."
Bandwidth The amount of data that can travel through a channel in a given period of time. Bandwidth
is usually measured in cycles per second (hertz) or in bits per second (BPS). The larger the
bandwidth, the more information the network can handle. ISDN is usually 64KB, 128KB
or 256KB. ASDL and DSL are generally faster than ISDN and sometimes faster than cable.
Cable connections are usually 500KB or 1MB. T1 is 1.5MB and T3 is 45MB.
BES Bursty Errored Seconds. Short duration disruptions of a digital bit stream.
Bit Stuffing The process of inserting extra bits into a T1 link to restore the bit rate of link.
Broadcast Broadcast is a transmission to multiple, unspecified recipients. On an Ethernet network, a

broadcast packet is a special type of multicast packet which nodes on the network are
always willing to receive.
Bypass Exchanging bytes among timeslots and T1/E1 links.
CAS Channel Associated Signaling (E1 signaling protocol).
CCS Common Channel Signaling. Signaling in which one channel in each link is used for
signaling to control, account for, and manage traffic on channels of the link.
Central Office Where telephone companies terminate customer lines and locate switching equipment to
(CO) interconnect those lines with other networks.
Challenge A strong authentication method used with PPP for user login. A type of authentication in
Handshake which the authentication agent (typically a network server) sends the client program a key
Authorization to be used to encrypt the username and password. This enables the username and password
to be transmitted in an encrypted form to protect them against eavesdroppers. When using
Protocol CHAP, the username/password is sent encrypted over the connection, preventing sniffing.
(CHAP) See also PAP.
Channel A generic reference to a data path, such as a voice channel or a high speed data channel,
which can include one or more time slots.
CLI Command Line Interface.
Customer On digital circuits provided by the telephone company, any terminating hardware owned
Premise by the user and not by the Telco (telephone company) is generically referred to as CPE.
Equipment
(CPE)
Glossary-2 FLEXmaster - Release 4.02

Glossary
Cyclic A check sum indicator based on the remainder of a polynomial calculation performed on
Redundancy the transmitted data that is used to verify, with some fixed probability of correctness,
Check (CRC) whether that data was transmitted.
CSS Controlled Slip Second. A controlled slip is the replication or deletion of the payload bits
of a DS1 frame. A Controlled slip can be performed when there is a difference between the
timing of a synchronous receiving terminal and the received signal.
CSU Channel Service Unit. A device used to protect the telephone network from equipment
faults at a customer location.
DACS Digital Access Cross Connect System. Equipment that separates a number of T1 signals
into their component DS0s and rearranges and redirects them in an unrestricted fashion,
then reconstructs new T1s consisting of a mix of DS0s from the original T1s. Used for
grooming or grouping DS0 channels originating from various sources, but destined for the
same location.
DC Direct Current.
DCE Data Circuit Terminating Equipment. Usually a modem, though it can be a data set, DSU,
or other device that is used to connect a computer to a data communications service.
Default Default Gateway is a routing table entry which is used to direct packets addressed to hosts
Gateway or networks not explicitly listed in the routing table.
Digital Access A digital switch for routing and switching T1 lines (and individual DS0 channels within T1
& Cross- lines), among multiple T1 ports. It performs all the functions of a normal switch, except
connect System connections are typically set up in advance of a call, not together with a call, as in most,
low bandwidth voice-band voice and data communications systems. A DACS is basically
(DACS) a manual T1 switch.
DLCI Data Link Control Identifier. DLCI is a channel number which is attached to data frames
to tell the network how to route the data in Frame Relay Networks.
DNS Domain Name System. DNS is a general-purpose distributed, replicated, data query service
chiefly used on Internet for translating host names into Internet IP addresses. DNS is
defined in STD 13, RFCs 1034 and 1035.
DS0 Digital Signal Zero, the standard bandwidth for digitized voice channels
DS1 Digital Signal Level 1. A digital signal transmitted at a nominal rate of 1.544 Mbps.
DSU Digital Service Unit. A device used to condition a data signal for transmission over the
relatively long wires from the customer location to the telephone office.
DSX-1 Digital Signal Cross Connect level 1. Such as a DS-1, but without the proper protection
circuitry (CSU) for transmission to the WAN. Used as a port for connection to local
equipment such as a PBX.
FLEXmaster - Release 4.02 Glossary-3

Glossary
DTE Data Terminal Equipment (user terminal equipment). Usually a computer terminal or a PC
emulating one, or a computer.
DTS Digital Transcoding Switch.
Dynamic Host A network configuration that allows maintenance to be performed from a central site rather
Configuration than by end users.
Protocol
(DHCP)
Dynamic A dynamic station is a host which is added automatically to an ARP or LAN table.
Station
E1 A digital transmission link with a total signaling speed of 2.048 Mbps.

E1 is a standard for the digital transmission in Europe (The European equivalent to the
North American T1).
Earth ground A wire conductor that terminates in the earth for electrical purposes. It is generally the
negative side of the circuit and is most important in alternating current (AC) circuits.
Chassis Ground is the general term used in direct current (DC) circuits.
ECT Easy Configuration Tool. A basic PACKETcore device configuration tool based on
command menus.
ESD ElectroStatic Discharge.
EE Errored Event.
Electro- Equipment used in high speed data systems, including ATM, that generate and transmit
magnetic many signals in the radio frequency portion of the electromagnetic spectrum. Interference
Interference to other equipment or radio services may result if sufficient power from these signals
escape the equipment enclosures or transmission media. National and international
(EMI) regulatory agencies (FCC, CISPR, etc.) set limits for these emissions. Class A is for
industrial use and Class B is for residential use.
Engine Six engines exist in the MASTERseries product line. They are the FLEXmaster,
PATHmaster, BANDmaster, LINKmaster, CLOCKmaster, DATAmaster, and the
TRANSmaster.
ES Errored Second.
ESF Extended SuperFrame. Comprises 24 frames.
Ethernet Ethernet is a particular network topology and protocol, especially useful in LANs. It comes
in various speeds and is often regarded as THE current technology for general network
direct connection. The current connectivity is generally considered to be 10Base-T or
100Base-T, while the backbone, if one is used, is coaxial cable or Fiber optics. There is also
a 1000Base-T for certain specialty copper joining situations.

Glossary
File Transfer An Internet protocol that enables you to transfer files between computers on the Internet.
Protocol (FTP)
filter An operating parameter used with routers that can be set to block the transfer of packets
from one LAN to another.
flash A particular type of memory that is ROM in nature, but can be updated and upgraded by
special programs. Many BIOS chips are of this technology.
Frame Relay Frame Relay is a packet-switching protocol for connecting devices on a WAN. Frame
Relay networks support data rates up to 1.544 Mbps.
FT1 Fractional T1. Partially used T1 line (some vacant channel timeslots).
Full Duplex A communications method where each end simultaneously transmits and receives.
Grooming Grooming refers to either consolidating or segregating traffic to make more efficient use of
the facilities.
High Density A bipolar coding method that does not allow more than 3 consecutive zeros.
Bipolar 3
(HDB3)
High level Data The HDLC protocol secures information in a data frame that allows devices to control data
Link Control flow and correct errors. For any HDLC communications session, one station is designated
(HDLC) primary and the other secondary.
IAD Integrated Access Device. A device that can combine functionality into a single, remotely
managed device.
ICMP Internet Control Message Protocol. Handles errors and sends error messages for TCP/IP.
IGMP Internet Group Management Protocol. A protocol used by IP hosts to report their multicast
group memberships to an adjacent multicast router.
IMUX Inverse Multiplexer.
Integrated Access to more than one carrier service over a combined higher speed line. For example, a
Access single T1 access line can be used to connect to an 800 service as well as a frame relay
service offered by a carrier. The services are multiplexed together over the one line.
Internet Internet Protocol, the method by which most Internet activity takes place. Members with
Protocol (IP) access to TCP/IP through a SLIP or PPP connection can connect to many ISP services in
this manner. As the name implies, it is a protocol for network activity. Most current
networks support some sort of TCP or IP directly or indirectly.

Glossary
IP address A string of four numbers separated by periods (such as 111.22.3.144) used to represent a
computer on the Internet. The format of the address is specified by the Internet Protocol in
RFC 791. Each of the four number must be 255 or less; they may be 0.
IP Mask The IP mask is a unique 4 byte (32 bit) value that allow the recipient of IP packets to
distinguish between different host IDs.
IP Multicast The transmission of an IP datagram to a host group, a set of zero or more hosts identified
by a single IP destination address. A multicast datagram delivered to members of its
destination host group with the same "best efforts" reliability as regular unicast IP
datagrams, for example, the datagram is not guaranteed to arrive intact at members of the
destination group or in the same order relative to other datagrams.
IP Routing IP Routing is the process, performed by a router, of selecting the correct interface and next
hop for a packet being forwarded. Routing is done to send a packet to a specific destination.
ITU International Telecommunications Union (formally known as CCITT).
IXC Inter-Exchange Carrier. The long distance phone company that provides connections
between POPs and connects to the customer premises using local telephone companies at
both ends. These are unregulated and there is a competitive choice for the customer. AT&T
and MCI are examples.
Jitter Undesirable short-term frequency deviation which is encountered in data transmission

lines.
LAN (Local A group of computers at a single location (usually an office or home) that are connected by
Area Network) phone lines, network cables of various configurations or coaxial cable. Usually controlled
and administered by a system or network administrator.
LBO Line Build Out. Insertion of attenuation (loss) in a short transmission line to make the line
behave as a longer line.
Link A connection to the wide area network, usually a T1 or E1 interface, but can also be an
ISDN (PRI) or other arrangement.
LOF Loss Of Framing. A red alarm.
loopback A diagnostic test in which a signal is transmitted across a medium while the sending device
waits for its return.
LOS Loss Of Signal. A red alarm.
LSB Least Significant Bit. Lowest order bit in the binary representation of numerical value.
MAC Address Media Access Control. The MAC Address is the hardware address of a device connected
to a shared network medium.

Glossary
Management A data base of objects, with attributes and values, representing the manageable components
Information of a network device. Used in SNMP. There are industry standardized MIBs and proprietary
Base (MIB) MIBs
Mask A mask is a filtering aid that is used to define classes of addresses. By defining classes, any
packet can be judged as to whether it should pass the filter or not.
Media Access The lower of the two sub-layers of the data link layer defined by the IEEE. The MAC sub-
Control (MAC) layer handles access to shared media, such as whether token passing or contention will be
used. The MAC contains the standardized data link layer address that is required for every
port or device that connects to a LAN. Other devices in the network use these addresses to
locate specific ports in the network and to create and update
MTU Maximum Transmission Unit. The largest frame length which can be sent on a physical
medium.
Modem MOdulator-DEModulator, a device that takes digital computer signal, converts it to analog,
and sends it across the phone line. Another modem on the reverse does the exact opposite
action. Modems transfer data at different speeds or rates, called baud.
MSB Most Significant Bit. The highest order bit in the binary representation of a numerical
value.
Multicast Multicast is an Ethernet addressing scheme used to send packets to devices of a certain type
or for broadcasting to nodes.
Multiplexer A complex piece of telephone equipment which combines the data stream of several leased
lines for transmission over a single higher bandwidth leased line. Multiplexors are used in
the construction of WANs.
Network An Internet standard that enables a local-area network (LAN) to use one set of IP addresses
Address for internal traffic and a second set of addresses for external traffic. A NAT box located
Translation where the LAN meets the Internet makes all necessary IP address translations.
(NAT)
Network A system which allows a provider or end user to manage portions or all of a
Management telecommunications network; in xDSL, network management systems allow providers to
System (NMS) control and monitor those services based on the ADSL streams, at both the physical and
logical layers of the services.
Network Socket A network socket is defined to be the unique identification to or from which information is
transmitted in the network.
Node Junction point in a network.
packet A unit of data sent across a network. When a large block of data is to be sent over a network,
it is broken up into several packets, sent, and the reassembled at the other end. The exact
layout of an individual packet is determined by the protocol and network architecture being
used.

Glossary
Password An authentication protocol that allows Point-to-Point Protocol peers to authenticate one
Authentication another.
Protocol (PAP)
PCM Pulse Code Modulation. The standard 64 kbps digital voice format.
PING Packet InterNet Groper. A protocol and program for sending a signal to see whether another
network host or other device is online and responding. PING is used to test reachability of
destinations by sending them an ICMP echo request and waiting for a reply.
Point of A site that has a collection of telecommunications equipment, usually refers to ISP or
Presence (POP) telephone company sites.
Point-to-Point Provides a standard means of encapsulating data packets sent over a single-channel WAN
Protocol (PPP) link. It is the standard WAN encapsulation protocol for the interoperability of bridges and
routers.
Port A connection to local data equipment (typically within the building). For example, V.35 or
RS-232.
Port Module There is one port module in the MASTERseries product line. It is the DATAmaster.
Private Branch A small telephone switching system (exchange) usually on a customer's premises that also
eXchange connects to the public switched telephone network.
(PBX)
Protocol A protocol is a set of formal rules describing how to transmit data across a network. Low
level protocols define the electrical and physical standards to be observed, bit- and byte-
ordering, and the transmission, error detection and correction of the bit stream. High level
protocols deal with the data formatting, including the syntax of messages, the terminal to
computer dialogue, character sets, sequencing of messages and so on.
Public Switched Public Switched Telephone Network, which refers to the international telephone system
Telephone based on copper wires carrying analog voice data. This is in contrast to newer telephone
Network networks base on digital technologies, such as ISDN and FDDI. Telephone service carried
by the PSTN is often called plain old telephone service (POTS). Most telephone companies
(PSTN) are trying to filter data and streaming services into one network and leave the PSTN for
mostly voice usage.
QoS Quality of Service.
RAM Random Access Memory. Volatile storage that loses its contents when power is off.
RFC Request For Comment. A numbered Internet informational documents and standards
widely followed by commercial software and freeware in the Internet and UNIX
communities.

Glossary
RIP Routing Information Protocol.
Robbed-bit A signaling method which uses the least-significant bit in every sixth sample of each voice
signaling channel, devoted to convey on/off hook conditions, busy, ringing, and so on.
Routing The process of selecting the most efficient circuit path for a message.
RJ-45 An 8-pin USOC plug and jack arrangement providing a unipolar electrical interface.
RJ-48C An 8-pin USOC plug and jack arrangement providing a bipolar electrical interface.
RS-232C Collection of specifications defining unipolar electrical and mechanical interfaces between
terminals, computers, and modems; generally limited to 19.2 kbps.
RS-422 Collection of specifications defining bipolar electrical and mechanical interfaces between
terminals, computers, and modems; generally limited to 2 Mbps.
SES Severely Errored Second.
Simple Network SNMP is the most common method by which network managements applications can
Management query a management agent using a supported MIB (Management Information Base).
Protocol SNMP operates at the OSI application layer.
(SNMP)
slot The position in the chassis for a Module, Adapter or Power Supply.
Socket See Network Socket.
SS7 Signaling System no. 7. Standard signaling protocol between major phone system switches.
switch In networks, a device that filters and forwards packets between LAN segments. Switches
operate at the data link layer (layer 2) of the OSI Reference Model and therefore support
any packet protocol. LANs that use switches to join segments are called switched LANs or,
in the case of Ethernet networks, switched Ethernet LANs.
synchronous See asynchronous as an opposing technology. Data transmission using synchronization

bytes, instead of start/stop bits, to control the transmission. In xDSL, video streams are
considered to be synchronous in nature.

Glossary
T1 Trunk Level 1. A digital transmission link with a total signaling speed of 1.544 Mbps. A
powerful, high speed transmission line connection to the Internet; it can also alternatively
handle 24 voice channels. There are also Fractional T1 lines. A T1 line can send a gigabyte
of information in less than 10 seconds. It has the capability of many simultaneous
"conversations" or connections within. T1 supports voice, data and video at different
frequencies on the same connection. T1 is a "full time connection" as opposed to dial-up.
Also known as T-1 and sometimes DS1. T-1 is a standard for the digital transmission in
North America, the European equivalent is an E1.
TCP Transmission Control Protocol. TCP is the most common transport layer protocol used on
Ethernet and the Internet. TCP is built on top of Internet Protocol (IP) and is nearly always
seen in the combination TCP/IP (TCP over IP). It adds reliable communication, flow-
control, multiplexing and connection-oriented communication. It provides full-duplex,
process-to-process connections. TCP is defined in STD 7, RFC 793.
TCP/IP Stack Transmission Control Protocol over Internet Protocol. TCP/IP stack is the standard
Ethernet protocols incorporated into 4.2BSD UNIX. While TCP and IP specify two
protocols at specific layers, TCP/IP is often used to see the entire DoD (Department of
Defense) protocol suite based upon these, including Telnet, FTP, UDP and RDP.
Telnet A terminal emulation program for TCP/IP networks such as the Internet. The Telnet
program runs on your computer and connects your PC to a server on the network. It lets you
connect to other computers on the Internet.
throughput Throughput is the amount of data a communications channel can carry, usually in bytes per
second.
Time Division TDM systems offer a synchronous transmission of data over a fixed bandwidth channel.
Multiplexing The most popular TDM transports are a T1 (1.5 Mbps) transport and a T3 (45 Mbps)
(TDM) transport. This transmission medium is ideal for traffic requiring a CBR transport, such as
voice.
timeslot A single 64 kbps channel within a T1 or E1 signal; also called a DS-0 in North America.
May also see a byte time on a circuit switched bus within a system.
Trivial File Trivial File Transfer Protocol. A simplified version of FTP that transfers files but does not
Protocol provide password protection or user-directory capability.
(TFTP)
trunk A communication path between two offices that carries voice or data.
TSI Time Slot Interchange.

Glossary
UDP User Datagram Protocol. UDP is an Internet standard network layer, transport layer and
session layer protocols which provide simple but unreliable datagram services. It adds a
checksum and additional process-to-process addressing information. UDP is a
connectionless protocol such as TCP, is layered on top of IP. UDP is defined in STD 6, RFC
768.
Unavailable UAS are calculated by counting the number of seconds that the interface is unavailable.
Seconds (UAS)
V.35 A CCITT standard protocol for transmitting data.
Virtual Circuit A circuit connection created to connect two devices between two networks. This
(VC) connection is identified by a VPI/VCI pair and can be a permanent connection or a switched
connection. See also VP, PVC and SVC.
WebMaster Browser-based PACKETcore configuration tool.
Wide Area A private long distance network that uses leased lines to connect computers or LANs. A
Network wide area network is a linking of computers not physically attached through conventional
(WAN) network connectivity. Usually the WAN connection is a dedicated or high grade dial up
phone link. It is often done with T1 or T3 connections but can also be through satellite or
other technologies.
Wideband A service or system with operating speeds 1.5 Mbps and above.

Glossary

Index INDEX
A ANSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
ABCD Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39 Application Module
ABCD/abcd Signaling Patterns . . . . . . . . . . . . . . . . . 3-23 Physical description . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Accessing the Software . . . . . . . . . . . . . . . . . . . . . . . 3-33 Applications
Adapter Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6 APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32
Adapter Module Dacs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 APS Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31
Eight slot chassis . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26 Attenuation level
Part number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4 LBO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Two slot chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 B
Alarm Contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 BERT
Alarm Screen On links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Alarm contacts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 On ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11
Card missing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Commit failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 C
Management ports . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 Card Diagnostics Screen . . . . . . . . . . . . . . . . . . . . . . 6-12
Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5 CLI command
Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3, 7-4 ? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Blue alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 add pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Conditions and states . . . . . . . . . . . . . . . . . . . . 7-6, 7-7 autoexit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Red alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2 boot server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
Yellow alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3 cd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Alarms Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
all modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 clear key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5 date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
autoexit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 delete binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33
cd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 delete interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
clear . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6 delete pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
clear key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 dhcp trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 dhcpc trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42
end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 dhcprelay trace . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43
exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 echo enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-36
help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8 end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 exclude pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34
key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9 exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 global option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
run script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
screen pause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11 history . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
show mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12 host option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-35
show running config . . . . . . . . . . . . . . . . . . . . . . . 4-13 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
show version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 ethernet
traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 address alloc . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
altitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 authentication . . . . . . . . . . . . . . . . . . . . . . . . 4-47
AMI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17 autoneg force . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Index
autonegotiation . . . . . . . . . . . . . . . . . . . . . . . 4-47 update interval . . . . . . . . . . . . . . . . . . . . . . . .4-68

cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48 pppt
delete interval . . . . . . . . . . . . . . . . . . . . . . . . 4-48 route age . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-63
encapsulation . . . . . . . . . . . . . . . . . . . . . . . . 4-49 ip
ip arp
config . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49 add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-70
rip enable . . . . . . . . . . . . . . . . . . . . . . . . . 4-50 max retries . . . . . . . . . . . . . . . . . . . . . . . . . . .4-70
ip rip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50 timrout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-70
no icmp send echo reply . . . . . . . . . . . . . . . . . . . . .4-71
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . 4-51 ip
no ip aggregate route . . . . . . . . . . . . . . . . . . . . . . . .4-71
config . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50 default ttl . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-71
rip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51 directed broadcast . . . . . . . . . . . . . . . . . . . . .4-72
recv ip-addr . . . . . . . . . . . . . . . . . . . . . . . . . 4-51 forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . .4-72
route age . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52 fragments . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-72
send ip-addr . . . . . . . . . . . . . . . . . . . . . . . . . 4-52 path mtu . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-73
show rip interface . . . . . . . . . . . . . . . . . . . . . 4-53 path mtu age . . . . . . . . . . . . . . . . . . . . . . . . . .4-73
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53 path mtu discover . . . . . . . . . . . . . . . . . . . . . .4-73
testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54 process option . . . . . . . . . . . . . . . . . . . . . . . .4-73
update interval . . . . . . . . . . . . . . . . . . . . . . . 4-54 proxy option . . . . . . . . . . . . . . . . . . . . . . . . . .4-74
hdlc reassembly . . . . . . . . . . . . . . . . . . . . . . . . . . .4-74
no shutdown . . . . . . . . . . . . . . . . . . . . . . . . . 4-55 redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-75
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55 route add . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-75
testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55 route age . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-76
ppp route age del . . . . . . . . . . . . . . . . . . . . . . . . . .4-76
address alloc . . . . . . . . . . . . . . . . . . . . . . . . . 4-57 unreachables . . . . . . . . . . . . . . . . . . . . . . . . . .4-76
authentication . . . . . . . . . . . . . . . . . . . . . . . . 4-57 no
cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58 arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-77
delete interval . . . . . . . . . . . . . . . . . . . . . . . . 4-59 icmp send echo reply . . . . . . . . . . . . . . . . . . .4-77
ip ip directed broadcast . . . . . . . . . . . . . . . . . . .4-77
rip enable . . . . . . . . . . . . . . . . . . . . . . . . . 4-59 ip forwarding . . . . . . . . . . . . . . . . . . . . . . . . .4-78
rip split-horizon . . . . . . . . . . . . . . . . . . . . 4-60 ip path mtu . . . . . . . . . . . . . . . . . . . . . . . . . . .4-78
ip config . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59 ip path mtu discover . . . . . . . . . . . . . . . . . . . .4-78
keep-alive-timer . . . . . . . . . . . . . . . . . . . . . . 4-60 ip process option . . . . . . . . . . . . . . . . . . . . . .4-78
lqr enable . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60 ip proxy arp . . . . . . . . . . . . . . . . . . . . . . . . . .4-79
magic number . . . . . . . . . . . . . . . . . . . . . . . . 4-61 ip redirects . . . . . . . . . . . . . . . . . . . . . . . . . . .4-79
no ip unreachables . . . . . . . . . . . . . . . . . . . . . . .4-79
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . 4-62 rarp
no authentication . . . . . . . . . . . . . . . . . . . . . 4-61 add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-79
no ip del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-80
rip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-80
no keep-alive-timer . . . . . . . . . . . . . . . . . . . 4-61 key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-9
no lqr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61 lease time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-36
no magic number . . . . . . . . . . . . . . . . . . . . . 4-61 list options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-37
recv ip-addr . . . . . . . . . . . . . . . . . . . . . . . . . 4-63 no global option . . . . . . . . . . . . . . . . . . . . . . . . . . .4-38
send ip-addr . . . . . . . . . . . . . . . . . . . . . . . . . 4-64 no host option . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39
show rip interface . . . . . . . . . . . . . . . . . . . . . 4-65 no icmp echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39
show stackinterface . . . . . . . . . . . . . . . . . . . 4-65 no service dhcp . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66 no subnet option . . . . . . . . . . . . . . . . . . . . . . . . . . .4-40
stackinterface . . . . . . . . . . . . . . . . . . . . . . . . 4-67 ping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10
testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68 ppp
unstackinterface . . . . . . . . . . . . . . . . . . . . . . 4-68 ip address local-pool . . . . . . . . . . . . . . . .4-57, 4-81
Index - 2 FLEXmaster - Release 4.02

Index
no ip address local-pool . . . . . . . . . . . . . . . . . . . 4-81 redistribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96

ppp authentication aaa . . . . . . . . . . . . . . . . . . . . 4-82 re-transmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96
ppp trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82 rip trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97
show security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97
interface config . . . . . . . . . . . . . . . . . . . . . . . 4-83 show neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98
ip address local-pool . . . . . . . . . . . . . . . . . . . 4-83 spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98
rai-option-control . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43 rtm
relay as-num . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99
dns relay deny add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100
cache ttl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84 deny all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100
default-nameserver . . . . . . . . . . . . . . . . . . . . 4-85 deny del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-100
maxCacheEntries . . . . . . . . . . . . . . . . . . . . . . 4-85 permit add . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101
maxNameServer . . . . . . . . . . . . . . . . . . . . . . 4-85 permit all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101
maxQueries . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85 permit del . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-101
maxUrlFilters . . . . . . . . . . . . . . . . . . . . . . . . 4-86 router-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-102
port type . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86 run script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
primary name-server . . . . . . . . . . . . . . . . . . . 4-86 screen pause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
query timeout . . . . . . . . . . . . . . . . . . . . . . . . 4-86 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
relay cache . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87 server dhcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41
trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87 server timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-40
relay servers-only
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87 disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87 enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44
show show arp cache . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
dns relay cache . . . . . . . . . . . . . . . . . . . . . . . 4-88 show arp config . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
dns relay message info . . . . . . . . . . . . . . . . . 4-88 show arp stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
dns relay name-server table . . . . . . . . . . . . . . 4-88 show dhcp relay info . . . . . . . . . . . . . . . . . . . . . . . 4-18
remove exclude pool . . . . . . . . . . . . . . . . . . . . . . . 4-40 show dhcpclnt config . . . . . . . . . . . . . . . . . . . . . . 4-18
resolver show dhcpclnt stats . . . . . . . . . . . . . . . . . . . . . . . . 4-19
dns-resolver trace . . . . . . . . . . . . . . . . . . . . . . . 4-89 show dhcpsrv bindings . . . . . . . . . . . . . . . . . . . . . 4-19
resolver show dhcpsrv boot config . . . . . . . . . . . . . . . . . . . 4-20
cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90 show dhcpsrv config . . . . . . . . . . . . . . . . . . . . . . . 4-20
cache ttl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90 show dhcpsrv exclude addresses . . . . . . . . . . . . . . 4-20
clear query info . . . . . . . . . . . . . . . . . . . . . . . 4-90 show dhcpsrv global options . . . . . . . . . . . . . . . . . 4-21
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90 show dhcpsrv global stats . . . . . . . . . . . . . . . . . . . 4-21
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90 show dhcpsrv hostoptions . . . . . . . . . . . . . . . . . . . 4-22
nameserver domain . . . . . . . . . . . . . . . . . . . . 4-91 show dhcpsrv pools . . . . . . . . . . . . . . . . . . . . . . . . 4-22
name-server table . . . . . . . . . . . . . . . . . . . . . 4-93 show dhcpsrv subnet options . . . . . . . . . . . . . . . . 4-22
safetybelt delete domain . . . . . . . . . . . . . . . . 4-91 show eth stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
sefetybelt addr . . . . . . . . . . . . . . . . . . . . . . . . 4-91 show icmp config . . . . . . . . . . . . . . . . . . . . . . . . . 4-23
show show icmp stats . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
resolver cache . . . . . . . . . . . . . . . . . . . . . . . . 4-92 show inarp stats . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
resolver config . . . . . . . . . . . . . . . . . . . . . . . . 4-92 show interface config . . . . . . . . . . . . . . . . . . . . . . 4-25
resolver queries . . . . . . . . . . . . . . . . . . . . . . . 4-93 show interface stats . . . . . . . . . . . . . . . . . . . . . . . . 4-26
resolver statistics . . . . . . . . . . . . . . . . . . . . . . 4-93 show ip global config . . . . . . . . . . . . . . . . . . . . . . 4-26
rip show ip interface . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27
neighbor add . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94 show ip path mtu . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
neighbor del . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94 show ip traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
neighbor disable . . . . . . . . . . . . . . . . . . . . . . . . 4-95 show mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
neighbor enable . . . . . . . . . . . . . . . . . . . . . . . . . 4-95 show rarp config . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
no distribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95 show rarp stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
no spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95 show rip config . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29
FLEXmaster - Release 4.02 Index - 3

Index
show rip interface stats . . . . . . . . . . . . . . . . . . . . . 4-30 Control Signal Definitions . . . . . . . . . . . . . . . . . . . . . A-4

show rip stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30 Craft Cable
show route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30 see NMS cable
show rrd deny routes . . . . . . . . . . . . . . . . . . . . . . . 4-30
show rrd permit routes . . . . . . . . . . . . . . . . . . . . . 4-31 D
show rtm config . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31 Data Port Interface . . . . . . . . . . . . . . . . . . . . . . . A-2, B-2
show running config . . . . . . . . . . . . . . . . . . . . . . . 4-13 Adapter cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
show snmp-community config . . . . . . . . . . . . . . . 4-31 Data signal definition . . . . . . . . . . . . . . . . . . . . . . . A-5
show snmp-trap config . . . . . . . . . . . . . . . . . . . . . 4-31 NMS cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
show version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 RS530 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
snmp V.35 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
no Data Set Ready (DSR, 107) . . . . . . . . . . . . . . . . . . . . A-4
snmp-community . . . . . . . . . . . . . . . . . . . . 4-103 Datacodes Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-24
snmp-shutdown . . . . . . . . . . . . . . . . . . . . . 4-103 DC Power
snmp-trap . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104 Protection and Isolation (Eight slot) . . . . . . . . . . . .2-28
snmp-community . . . . . . . . . . . . . . . . . . . . . . 4-104 Protection and Isolation (Two slot) . . . . . . . . . . . .2-11
snmp-shutdown . . . . . . . . . . . . . . . . . . . . . . . . 4-104 Default IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-40
snmp-trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105 Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16
sntp dhcp
clock timezone . . . . . . . . . . . . . . . . . . . . . . . . 4-106 add pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-33
no boot server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-33
clock timezone . . . . . . . . . . . . . . . . . . . . . . 4-106 delete binding . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-33
poll-interval . . . . . . . . . . . . . . . . . . . . . . . . 4-107 delete pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-34
sntp server . . . . . . . . . . . . . . . . . . . . . . . . . 4-107 dhcp trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-34
show sntp config . . . . . . . . . . . . . . . . . . . . . . . 4-107 echo enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-36
show time . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108 exclude pool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-34
sntp enable . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108 global option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-35
sntp poll-interval . . . . . . . . . . . . . . . . . . . . . . . 4-108 host option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-35
sntp server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108 lease time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-36
state list options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-37
disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44 no global option . . . . . . . . . . . . . . . . . . . . . . . . . . .4-38
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44 no host option . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39
subnet option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-41 no icmp echo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39
system no service dhcp . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-39
file-delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109 no subnet option . . . . . . . . . . . . . . . . . . . . . . . . . . .4-40
file-download . . . . . . . . . . . . . . . . . . . . . . . . . 4-109 remove exclude pool . . . . . . . . . . . . . . . . . . . . . . . .4-40
file-rename . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110 server dhcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-41
file-upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110 server tirmeout . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-40
show files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111 subnet option . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-41
traceroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14 dhcp client mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42
CLI Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 dhcp mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32
modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 dhcpc
Clock (Clk) Screen . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19 dhcpc trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42
Command Line Interface Help . . . . . . . . . . . . . . . . . . 4-2 dhcprelay
coMmit screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34 dhcprelay trace . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43
Configuring rai-option-control . . . . . . . . . . . . . . . . . . . . . . . . . .4-43
Remote modem . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-44
Configuring Links for Alarms . . . . . . . . . . . . . . . . . . 3-37 servers-only
Configuring System Timing . . . . . . . . . . . . . . . . . . . 3-19 disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-44
Connect screen . . . . . . . . . . . . . . . . . . . . . . . . 3-25, 3-30 enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-44
Connection Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27 state
Console Configuration Screen . . . . . . . . . . . . . . . . . 3-12 disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-44

Index
enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-44 I
dhcprelay mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43 Idle Signaling
Diagnostic Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Signaling bit patterns . . . . . . . . . . . . . . . . . . . . . . 3-39
Diagnostics IdleCode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 Installation
Diagnostics Signal Definitions . . . . . . . . . . . . . . . . . . A-5 23-inch rackmounting . . . . . . . . . . . . . . . . . . . . . . 2-22
DS0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-3 Application modules (eight slot) . . . . . . . . . . . . . . 2-25
Eight slot chassis power . . . . . . . . . . . . . . . . . . . . 2-28
E Engine module . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-4 Redundant power supplies . . . . . . . . . . . . . . . . . . 2-22
Eight Slot Chassis Special considerations . . . . . . . . . . . . . . . . . . . . . . 2-27
Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8 Two slot power . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22 Installation Environment
Slot positioning . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26 operating altitude . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
Electrical Characteristics . . . . . . . . . . . . . . . . . . . . . . A-4 interface
Enable Performance Monitoring Statistics . . . . . . . . 3-18 commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-45
Engine Module ethernet
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 address alloc . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Eight slot chassis . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26 authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
Two slot chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 autoneg force . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Environment Requirements autonegotiation . . . . . . . . . . . . . . . . . . . . . . . . . 4-47
operating altitude . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
Error Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17 delete interval . . . . . . . . . . . . . . . . . . . . . . . . . . 4-48
ES Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37 encapsulation . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
ESF Error Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19 ip
ethernet mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-46 config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-49
Examples rip enable . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
APS application . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32 ip rip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
DACs connection . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20 no
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
F no ip
Fan Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13 config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-50
Far End Long Report . . . . . . . . . . . . . . . . . . . . . . . . . 7-21 rip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Far End Short Report . . . . . . . . . . . . . . . . . . . . . . . . . 7-21 recv ip-addr . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-51
Fault Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 route age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
Fault Isolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5 send ip-addr . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-52
FDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 show rip interface . . . . . . . . . . . . . . . . . . . . . . . 4-53
Fields shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-53
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Fractional BERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 update interval . . . . . . . . . . . . . . . . . . . . . . . . . 4-54
Fractional Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 hdlc
Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 no shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Front Panel shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
HUBmaster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23 testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
Full Duplex Cross Connects . . . . . . . . . . . . . . 3-20, 3-30 ppp
address alloc . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
H authentication . . . . . . . . . . . . . . . . . . . . . . . . . . 4-57
HDB3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-5 cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-58
hdlc mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-55
delete interval . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
ip
Hot Key Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 rip enable . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59
Hot Swappable Modules . . . . . . . . . . . . . . . . . . . 2-4, 8-3
rip split-horizon . . . . . . . . . . . . . . . . . . . . . . 4-60

Index
ip config . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-59 ip path mtu discover . . . . . . . . . . . . . . . . . . . . . .4-78

keep-alive-timer . . . . . . . . . . . . . . . . . . . . . . . . 4-60 ip process option . . . . . . . . . . . . . . . . . . . . . . . .4-78
lqr enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-60 ip proxy arp . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-79
magic number . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61 ip redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-79
no ip unreachables . . . . . . . . . . . . . . . . . . . . . . . . . .4-79
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62 rarp
no authentication . . . . . . . . . . . . . . . . . . . . . . . . 4-61 add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-79
no ip del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-80
rip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-62 server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-80
no keep-alive-timer . . . . . . . . . . . . . . . . . . . . . . 4-61 ip mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-69
no lqr . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-61 IP Router Plug-on . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9
no magic number . . . . . . . . . . . . . . . . . . . . . . . 4-61
recv ip-addr . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63 L
route age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-63 Link Adapter with Pin-out Diagrams . . . . . . . . . . . . . .2-9
send ip-addr . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-64 Link Alarm Log Screen . . . . . . . . . . . . . . . . . . . . . . .7-11
show rip interface . . . . . . . . . . . . . . . . . . . . . . . 4-65 Link Diagnostics
show stackinterface . . . . . . . . . . . . . . . . . . . . . . 4-65 Enable/disable fractional loopback . . . . . . . . .6-5, 6-11
shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-66 Link Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18
stackinterface . . . . . . . . . . . . . . . . . . . . . . . . . . 4-67 Local Performance Statistics Screen . . . . . . . . . . . . . .7-19
testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-68 Loopback
unstackinterface . . . . . . . . . . . . . . . . . . . . . . . . 4-68 BiDirectional . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10
update interval . . . . . . . . . . . . . . . . . . . . . . . . . 4-68 Fractional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10
Interface Stacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3 Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9
ip Local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9, 6-12
arp Local AIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9
add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70 None . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9
max retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70 Payload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9
timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-70 Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-12
icmp send echo reply . . . . . . . . . . . . . . . . . . . . . . 4-71 Remote Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10
ip Remote payload . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10
aggregate route . . . . . . . . . . . . . . . . . . . . . . . . . 4-71 Loopback Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5
default ttl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-71 LoopUp Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17
directed broadcast . . . . . . . . . . . . . . . . . . . . . . . 4-72
forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72 M
fragments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-72 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33
path mtu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73 Redundant NMS ports . . . . . . . . . . . . . . . . . . . . . .7-24
path mtu age . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13
path mtu discover . . . . . . . . . . . . . . . . . . . . . . . 4-73 Origin type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
process option . . . . . . . . . . . . . . . . . . . . . . . . . . 4-73 Management Link . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
proxy arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74 mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4
reassembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-74 all modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5
redirects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75 dhcp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-32
route add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-75 dhcp client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-42
route age . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76 dhcprelay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-43
route age del . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76 interface
unreachables . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-76 ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-46
no hdlc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-55
arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-77 ppp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-56
icmp send echo reply . . . . . . . . . . . . . . . . . . . . 4-77 ip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-69
ip directed broadcasr . . . . . . . . . . . . . . . . . . . . . 4-77 ppp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-81
ip forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78 relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-84
ip path mtu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-78 resolver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-89

Index
rip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94 port type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86

root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15 primary-nameserver . . . . . . . . . . . . . . . . . . . . . 4-86
rtm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99 query timeout . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86
snmp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103 relay cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
sntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106 trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109 relay
Module Installation disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
Eight slot chassis . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25 enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-87
Two slot chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10 show
Module Removal and Replacement . . . . . . . . . . . . . . . 8-3 dns relay cache . . . . . . . . . . . . . . . . . . . . . . . . . 4-88
dns relay message info . . . . . . . . . . . . . . . . . . . 4-88
O dns relay name-server table . . . . . . . . . . . . . . . 4-88
operating relay mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84
altitude . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 Remote Access Modem . . . . . . . . . . . . . . . . . . . . . . . 2-31
Dipswitch settings . . . . . . . . . . . . . . . . . . . . . . . . . 2-32
P Modem/NMS adapter . . . . . . . . . . . . . . . . . . . . . . 2-31
Parity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
PATHmaster Remote Performance Message
Configuring the Internal Timeslot Connections . . 3-25 Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Pcore or DACS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Performance Monitoring Message select . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17 Send message . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Physical Description . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3 Remote Performance Stats
Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 Request screen . . . . . . . . . . . . . . . . . . . . . . . 7-22, 7-23
Port Diagnostics Screen . . . . . . . . . . . . . . . . . . . . . . . 6-11 Report
Powering User network, short . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Two slot chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11 Resetting the Modules . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Powering the Eight Slot Chassis . . . . . . . . . . . . . . . . 2-28 resolver
PPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 dns-resolver trace . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
ppp resolver
ip address local-pool . . . . . . . . . . . . . . . . . . 4-57, 4-81 cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
no ip address local-pool . . . . . . . . . . . . . . . . . . . . . 4-81 cache ttl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
ppp authentication aaa . . . . . . . . . . . . . . . . . . . . . . 4-82 clear query info . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
ppp trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82 disable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
show enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-90
interface config . . . . . . . . . . . . . . . . . . . . . . . . . 4-83 nameserver domain . . . . . . . . . . . . . . . . . . . . . . 4-91
ip address local-pool . . . . . . . . . . . . . . . . . . . . . 4-83 name-server table . . . . . . . . . . . . . . . . . . . . . . . 4-93
ppp mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-56, 4-81 safetybelt addr . . . . . . . . . . . . . . . . . . . . . . . . . . 4-91
Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18 safetybelt delete domain . . . . . . . . . . . . . . . . . . 4-91
show
R resolver cache . . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
Received Data (BB/104) . . . . . . . . . . . . . . . . . . . . . . A-5 resolver config . . . . . . . . . . . . . . . . . . . . . . . . . 4-92
relay resolver queries . . . . . . . . . . . . . . . . . . . . . . . . . 4-93
dns relay resolver statistics . . . . . . . . . . . . . . . . . . . . . . . . 4-93
cache ttl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-84 resolver mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-89
default-nameserver . . . . . . . . . . . . . . . . . . . . . . 4-85 rip
maxCacheEntries . . . . . . . . . . . . . . . . . . . . . . . . 4-85 neighbor add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
maxNameServer . . . . . . . . . . . . . . . . . . . . . . . . 4-85 neighbor del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
maxQueries . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-85 neighbor disable . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95
maxUrlFilters . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-86 neighbor enable . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95

Index
no distribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95 deny add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-100

no spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-95 deny all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-100
redistribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96 deny del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-100
re-transmit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96 permit add . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-101
rip trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97 permit all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-101
security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-97 permit del . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-101
show neighbor . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98 router-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-102
spacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-98 rtm mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-99
RIP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2 RUN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31
rip mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-94
root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15 S
delete interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16 Screen Definitions
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3, 7-4
show arp cache . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17 APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31
show arp config . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17 Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19
show arp stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17 Connect . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26, 3-27
show dhcp relay info . . . . . . . . . . . . . . . . . . . . . . . 4-18 Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13
show dhcpclnt config . . . . . . . . . . . . . . . . . . . . . . 4-18 Dacs/Management . . . . . . . . . . . . . . . . . . . . . . . . .3-20
show dhcpclnt stats . . . . . . . . . . . . . . . . . . . . . . . . 4-19 Error checking/save (Commit) . . . . . . . . . . . . . . . .3-35
show dhcpcsrv boot config . . . . . . . . . . . . . . . . . . 4-20 Error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-12
show dhcpcsrv config . . . . . . . . . . . . . . . . . . . . . . 4-20 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-23
show dhcpcsrv exclude addresses . . . . . . . . . . . . . 4-20 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16
show dhcpcsrv global options . . . . . . . . . . . . . . . . 4-21 Link log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11
show dhcpcsrv global stats . . . . . . . . . . . . . . . . . . 4-21 Local status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-20
show dhcpcsrv host options . . . . . . . . . . . . . . . . . 4-22 Management port . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
show dhcpcsrv pools . . . . . . . . . . . . . . . . . . . . . . . 4-22 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33
show dhcpcsrv subnet options . . . . . . . . . . . . . . . 4-22 Performance monitoring . . . . . . . . . . . . . . . . . . . . .7-18
show dhcpsrv bindings . . . . . . . . . . . . . . . . . . . . . 4-19 Remote status . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-21
show eth stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23 Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23, 3-24
show icmp config . . . . . . . . . . . . . . . . . . . . . . . . . 4-23 Threshold Alarms . . . . . . . . . . . . . . . . . . . . . . . . . .3-37
show icmp stats . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24 Warm reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13
show inarp stats . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24 Screen Diagnostics
show interface config . . . . . . . . . . . . . . . . . . . . . . 4-25 Port diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . .6-11
show interface stats . . . . . . . . . . . . . . . . . . . . . . . . 4-26 Screens
show ip global config . . . . . . . . . . . . . . . . . . . . . . 4-26 Alarm cutoff . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10
show ip interface . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
show ip path mtu . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28 APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31
show ip traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28 Commit (error checking and save) . . . . . . . . . . . . .3-34
show rarp config . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29 Dacs port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20
show rarp stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29 Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-2
show rip config . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-29 Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-23
show rip interface stats . . . . . . . . . . . . . . . . . . . . . 4-30 Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16
show rip stats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30 Link alarm log . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11
show route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-30 Link diagnostics (BERT) . . . . . . . . . . . . . . . . . . . .6-11
show rrd deny routes . . . . . . . . . . . . . . . . . . . . . . . 4-30 Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-22
show rrd permit routes . . . . . . . . . . . . . . . . . . . . . 4-31 Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
show rtm config . . . . . . . . . . . . . . . . . . . . . . . . . . 4-31 Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33
show snmp-community config . . . . . . . . . . . . . . . 4-31 Remote performance statistics . . . . . . . . . . . . . . . .7-20
show snmp-trap config . . . . . . . . . . . . . . . . . . . . . 4-31 Remote performance statistics request . . . . . . . . . .7-22
RS-530 Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . A-4 Send link log in progress . . . . . . . . . . . . . . . . . . . .7-26
rtm Send linklog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-24
as-num . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-99 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

Index
System event history log . . . . . . . . . . . . . . . . . . . . 7-12 Telnet Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40

System timing configuration . . . . . . . . . . . . . . . . . 3-19 Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Threshold alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37 TFTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Trunk conditioning datacodes . . . . . . . . . . . . . . . . 3-24 The . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13
Trunk conditioning signaling . . . . . . . . . . . . . . . . . 3-23 Threshold Alarm Screen . . . . . . . . . . . . . . . . . 3-29, 3-37
Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Threshold Alarms
Warm reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13 Errored seconds threshold . . . . . . . . . . . . . . . . . . . 3-38
Send Link Log In Progress Screen . . . . . . . . . . . . . . . 7-26 Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-38
Send Linklog Screen . . . . . . . . . . . . . . . . . . . . . . . . . 7-24 Unavailable seconds . . . . . . . . . . . . . . . . . . . . . . . 3-38
Send Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23 Time Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Send Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26 Timeslot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Setting Ethernet Interfaces . . . . . . . . . . . . . . . . . . . . . . 5-3 Timeslot Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17, 3-23 Timing Signal Definitions . . . . . . . . . . . . . . . . . . . . . . A-5
snmp External clock A . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
no Receiver signal element timing . . . . . . . . . . . . . . . . A-5
snmp-community . . . . . . . . . . . . . . . . . . . . . . . 4-103 Transmit signal element timing . . . . . . . . . . . . . . . . A-5
snmp-shutdown . . . . . . . . . . . . . . . . . . . . . . . . 4-103 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
snmp-trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104 Blue alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
snmp-community . . . . . . . . . . . . . . . . . . . . . . . . . 4-104 Diagnosing a fault . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
snmp-shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . 4-104 Interpreting alarm indications . . . . . . . . . . . . . . . . . 8-2
snmp-trap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-105 Loopback test paths . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
snmp mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
sntp Problem, one channel . . . . . . . . . . . . . . . . . . . . . . . 8-5
clock timezone . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106 Trunk conditioning . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
no Troubleshooting Flowchart
clock timezone . . . . . . . . . . . . . . . . . . . . . . . . . 4-106 Local single channel . . . . . . . . . . . . . . . . . . . . . . . . 8-6
sntp poll-interval . . . . . . . . . . . . . . . . . . . . . . . 4-107 Local site link/port . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
sntp server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-107 Trunk Conditioning Datacodes . . . . . . . . . . . . . . . . . 3-24
show sntp config . . . . . . . . . . . . . . . . . . . . . . . . . 4-107 Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
show time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108 Two Slot Chassis
sntp enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
sntp poll-interval . . . . . . . . . . . . . . . . . . . . . . . . . 4-108 Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
sntp server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-108 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9
sntp mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-106
Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 U
Sysname . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41 UAS Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37
system Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
file-delete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109 Uploading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
file-download . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109 User Network Long Report . . . . . . . . . . . . . . . . . . . . 7-20
file-rename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110
file-upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-110 V
show files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-111 V.35 Data Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
System Event History
Drop errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
System errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
System Event History Log Screen . . . . . . . . . . . . . . . 7-12
System Information . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
system mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-109
System Start-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
T
T1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16, 3-18

Index

FLEXmaster User Manual 4 02

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FLEXmaster User Manual 4 02

Uploaded by

Copyright:

Available Formats

FLEXmaster

Part Number: 770-0149-AB

Supporting Software Version:

FCC Requirements, Part 15

FCC Requirements, Part 68

iv FLEXmaster - Release 4.02

FLEXmaster - Release 4.02 v

Industry Canada ICES-003

Industry Canada CS-03

vi FLEXmaster - Release 4.02

DANGER! A DANGER NOTICE INDICATES THE PRESENCE OF A HAZARD THAT CAN OR

CAUTION! A CAUTION NOTICE INDICATES THE POSSIBILITY OF INTERRUPTING NETWORK

WARNING! A WARNING NOTICE INDICATES THE POSSIBILITY OF EQUIPMENT DAMAGE IF

FLEXmaster - Release 4.02 vii

Electrostatic Discharge (ESD) Precautions

WARNING! INTEGRATED CIRCUITS (ICS) ARE EXTREMELY SUSCEPTIBLE TO ELECTROSTATIC

viii FLEXmaster - Release 4.02

FLEXmaster - Release 4.02 ix

Limitation of Warranty & Limitation of Remedies

Warranty Product Returns

x FLEXmaster - Release 4.02

Keyboard Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

xii FLEXmaster - Release 4.02

FLEXmaster - Release 4.02 xiii

Error Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-12

A Data Port Interfaces

B SNMP Trap List

xiv FLEXmaster - Release 4.02

1-2 FLEXmaster - Release 4.02

There are three chassis available for the MASTERseries:

FLEXmaster - Release 4.02 1-3

T1 Scalability and Processing to Grow with Future Demands

1-4 FLEXmaster - Release 4.02

FLEXmaster Technical Specifications

FLEXmaster - Release 4.02 1-5

1-6 FLEXmaster - Release 4.02

FLEXmaster - Release 4.02 1-7

1-8 FLEXmaster - Release 4.02

2-2 FLEXmaster - Release 4.02

FLEXmaster - Release 4.02 2-3

2-4 FLEXmaster - Release 4.02

8608 Ejector/Top Handle.

RxD TxD PST ALM

ENET 2 Ethernet Port 2

FLEXmaster - Release 4.02 2-5

2-6 FLEXmaster - Release 4.02

FLEXmaster Adapter Module

8-pin RJ-48C Connectors

FLEXmaster - Release 4.02 2-7

LED State Description

Green DC input present

24/-48 VDC Power Supply (eight-slot)

24/-48 VDC Power Supply (two-slot)

Power Supply Input Power

2-8 FLEXmaster - Release 4.02

Installing a Two-Slot Chassis

23–inch mounting ears

FLEXmaster - Release 4.02 2-9

Installing Application Modules in a Two-Slot Chassis

2-10 FLEXmaster - Release 4.02

Two-slot Power Supply

Power Entry Panel Alarm Terminal Block

DC Line Input Fuses