S2500 Hwug 102813

Motorola Network Router
(MNR) S2500
Hardware User Guide
October 2013
THIS PAGE INTENTIONALLY LEFT BLANK.
MOTOROLA NETWORK ROUTER
MNR S2500 HARDWARE USER GUIDE
2013 MOTOROLA SOLUTIONS, INC.

ALL RIGHTS RESERVED
OCTOBER 28, 2013
PRINTED IN U.S.A.
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs stored in semiconductor memories or
other media. Laws in the United States and other countries preserve for Motorola certain exclusive rights for copyright computer programs,
including the exclusive right to copy or reproduce in any form the copyright computer program. Accordingly, any copyright Motorola computer
programs contained in the Motorola products described in this document may not be copied or reproduced in any manner without the express
written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication,
estoppel, or otherwise, any license under the copyrights, patents, or patent applications of Motorola, except for the rights that arise by operation
of law in the sale of a product.
Restrictions
The software described in this document is the property of Motorola. It is furnished under a license agreement and may be used and/or
disclosed only in accordance with the terms of the agreement. Software and documentation are copyright materials. Making unauthorized
copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system,
or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola.
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola assumes no liability resulting from any
inaccuracies or omissions in this document, or from the use of the information obtained herein. Motorola reserves the right to make changes to
any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes
from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola does not assume any liability arising
out of the application or use of any product or circuit described herein; neither does it convey license under its patent rights of others.
Trademarks
MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark
Holdings, LLC and are used under license. All other trademarks are the property of their respective owners.
DOCUMENT
HISTORY
DOCUMENT HISTORY
...................................
....
Date Description
7/29/2009 Updates to 04/09 version (part number 8971715H06-A):

Removed references to the X.25 service, which is no
longer supported in EOS.
Added specific security features (protocol
authentication, dynamic security policies, MD5
authentication for OSPF/BGP, SSH, and SNMP) to Table
4-2 (Where to Go From Here).
Removed part number (MNR hardware user guides are
delivered as part of the EOS .tar file and are no longer
tracked by a separate part number).
12/17/2009 Updated note regarding support for tagged VLAN ports

to read:
NOTE
The 10BASE-T module does not support
tagged VLAN ports with certain versions of
EOS software certified for system releases prior
to the ASTRO 25 7.8 system release. If you
attempt to configure a tagged VLAN port on
the 10BASE-T module interface of an S2500
router running a version of EOS software that
does not support tagged VLAN ports, the
system returns an error message similar to the
following:
VLANs are currently supported only
on Ethernet.
This note appears on pages 1-2, 1-7, and 4-7.
2/10/10 Added Diffie-Hellman Group 14 to list of public key

execution security features.
Updated V.24 null modem cable pinouts.
6/15/2010 Updated the descriptions of the startup status for the

V.24 and E&M LEDs.
Made clarifications in the section documenting
FlexWAN cabling and moved some FlexWAN cabling
information to Chapter 2.
(Continued)
O CT OB ER 28 , 2 01 3 III
DOCUMENT HISTORY MNR S2500 HARDWARE USER GUIDE
Date Description
7/20/2010 Clarified that the T1/E1 interfaces include CSU/DSU

functionality.
Clarified that the default LineDistance setting for
ASTRO 25 systems is SH1, which minimizes cross talk
issues and works for implementations where the T1
interface and the MNR S2500 are collocated in the same
room (within 133 cable feet of each other).
9/14/2010 Updated the descriptions of the E&M module LEDs.
10/5/2010 Corrected chapter headers in Chapters 2-4
3/23/2011 Added an appendix with instructions for installing

tamper evidence labels to meet Common Criteria
requirements.
4/5/2011 Updated the Changing the root and admin

Passwords section to document increased maximum
password length (31 characters) for RADIUS-
authenticated users.
4/25/2011 Added information about connecting analog base stations

to the MNR S2500 E&M (analog) interfaces, including
E&M pin functions.
5/9/2011 Updated Installing Tamper Evidence Labels appendix

to document installation of four (as opposed to two)
tamper evidence labels on the MNR S2500.
6/14/2011 Corrected the instructions for setting the V.24 clock

source.
10/25/2011 Updated CCGW Functionality section.
12/13/2011 Usability enhancement: moved cable pinout information

to Chapter 2, so it is consolidated with connection
instructions.
8/31/2012 Added an appendix documenting how to copy files

between the MNR S2500 and a TFTP or FTP server.
10/2/2012 Updated the Installing the S2500 Hardware chapter to

include instructions for replacing and removing, as well
as installing, optional modules.
10/22/2012 Updated the information for how to access related

manuals in the Additional Documentation section.
4/19/2013 Added note to SysconF Command Menus appendix

documenting how to avoid situation in which boot
counters may wrap and report negative numbers.
(Continued)
IV O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE DOCUMENT HISTORY
Date Description
7/29/2013 Changed grounding to grounding (earthing)

throughout document.
Updated the URL for Motorola Online in the Related
Documentation section.
9/4/2013 Changed definition of SCC acronym from System Support

Center to Solution Support Center.
10/28/2013 Updated the URL for the Motorola Online website in the
Related Documentation section.
O CT OB ER 28 , 2 01 3 V
TABLE
OF
CONTENTS
Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xi
Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Procedures & Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xvii
ABOUT THIS GUIDE

Who Should Use This Guide? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xix
How This Guide is Organized . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xx
Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxi
Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Notice Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii
Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii
CHAPTER 1: S2500 OVERVIEW

S2500 Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2
Front Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
S2500 Supported Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Using the S2500 in Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9
Telco Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9
CCGW Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
Encryption Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-13
CHAPTER 2: INSTALLING THE S2500 HARDWARE

Pre-Installation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Selecting the Installation site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Gathering the Required Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3
Reviewing the Contents of the Shipping Carton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4
Installing, Replacing, and Removing Optional Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
Installing an I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6
Replacing an I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10
Removing an I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-13
Installing An Encryption Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-16
Replacing an Encryption Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20
Mounting the S2500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24
Installing on a Tabletop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24
Stacking with Brackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-25
Installing in a Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26
Cabling the Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-27
Cabling the Power Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-27
Connecting a Chassis Ground (Earth). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-28
Cabling the Ethernet Connector(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29
Cabling the FlexWAN Serial Connector(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-36
Cabling the WAN/Telco (T1/E1 CSU/DSU) Connector(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-49
O CT OB ER 28 , 2 01 3 VII
CONTENTS MNR S2500 HARDWARE USER GUIDE
Cabling the V.24 Connector(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50

Cabling the E&M (Analog) Connector(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Connecting a PC, Terminal, or Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
Powering the Router On and Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
CHAPTER 3: LOGGING ON AND PERFORMING ADMINISTRATIVE TASKS

Starting the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Verifying Successful Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Logging on to the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Using the Command-line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Using the Menu-Driven Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Performing Basic Administrative Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Changing the root and admin Passwords. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Changing the Default Console Port Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Managing User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Setting the Time and Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Setting System Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Setting Up Security Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Configuring The MNR S2500 to Perform IP Routing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Accessing the S2500 Remotely . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS

Understanding Connectors, Paths and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Path and Port Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Mapping Multiple Paths to a Single Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Mapping Multiple Ports to a Single Path (Virtual Ports) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
S2500 Port and Path Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Path, Port, and Connector Services and Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-6
Configuring the Ethernet Interface(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Configuring the FlexWAN Serial Interface(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Configuring FlexWAN Interfaces with DCE Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Configuring FlexWAN Serial Interfaces with DTE Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Configuring the WAN/Telco (T1/E1 CSU/DSU) Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
WAN/Telco (T1/E1 CSU/DSU) Interface Configuration Prerequisites . . . . . . . . . . . . . . . . . . . . . . 4-12
WAN/Telco (T1/E1 CSU/DSU) Interface Configuration Procedure . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Configuring the V.24 (CCGW Digital Conventional) Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Configuring the E&M (CCGW Analog Conventional) Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16
Where To Go From Here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17
APPENDIX A: COMPLIANCE
EMC/EMI Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Modifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Shielded Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Product Safety Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
VIII O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE CONTENTS
FCC Part 15 Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

Telephony Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
FCC Part 68 Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Canadian Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8
Japanese Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
CE Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
EU WEEE Directive Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Caring for the Environment by Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Disposal of your Electrical Accessories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
CMM Labeling and Disclosure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
APPENDIX B: TECHNICAL SUPPORT
APPENDIX C: TROUBLESHOOTING
Using the S2500 Firmware Boot Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Boot Mode (BM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Boot (BT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
Configure Load (CL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Display Files (DF) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Flash Load (FL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Recovery Action (RA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Reboot (RB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Show System Information (SI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
Set Self Test Action (ST). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
Help (H, ?) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
Normal LED Meanings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
System LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
LAN (Ethernet) LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
FlexWAN Serial LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11
WAN/Telco (T1/E1 CSU/DSU) LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12
V.24 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
E&M Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Error LED Meanings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Troubleshooting During the Load Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Troubleshooting During the Test Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
Errors Indicated by the Serial LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Performing Loopback Tests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Configuring a Serial Line Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Configuring an Rx-to-Tx Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Configuring a Local Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-24
Configuring a Rx-to-Tx Loopback on the Link Partner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-25
Responses to Loopback Assertions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-26
O CT OB ER 28 , 2 01 3 IX
CONTENTS MNR S2500 HARDWARE USER GUIDE
Performing a Memory Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27

Performing a Full Memory Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27
Performing a Partial Memory Dump. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-32
Verifying the Memory Dump Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-34
APPENDIX D: RELOADING THE SYSTEM SOFTWARE

System Software Reload Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Reloading the Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Load Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
APPENDIX E: SYSCONF COMMAND MENUS

Using the SysconF Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
S2500 SysconF Command Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
Console Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-2
Self-Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
Primary Boot Source and Secondary Boot Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-3
Test Boot Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-4
Boot Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-6
Recovery Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7
Boot Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7
APPENDIX F: INSTALLING TAMPER EVIDENCE LABELS

Securing the MNR S2500 with
Tamper Evidence Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-2
Removing the Tamper Evidence Labels from the Power Receptacle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . F-4
APPENDIX G: COPYING FILES TO AND FROM A TFTP OR FTP SERVER

Copying Files between an MNR S2500 and a TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-2
Copying Files between an MNR S2500 and an FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-3
Configuring FTP Login Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-4
Troubleshooting TFTP/FTP File Transfer Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . G-5
X O C T OBE R 2 8, 20 1 3
LIST
OF
FIGURES
FIGURES
...................................
..
Figure 1-1: Front Panel of the S2500
(WAN/Telco (T1/E1) Module in Slot A; FlexWAN Module in Slot B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
Figure 1-2: Front Panel of the S2500
(WAN/Telco (T1/E1) Module in Slot A; 10BASE-T Module in Slot B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4
Figure 1-3: Front Panel of the S2500 (V.24 Module in I/O Slot A; E&M Module in Analog Slot). . . . . . . . .1-5
Figure 1-4: Rear Panel of the S2500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6
Figure 2-1: Removing the Screws that Secure the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
Figure 2-2: Removing the Cover from the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8
Figure 2-3: I/O Module Slot, Connector, and Standoff Locations on the S2500 Motherboard . . . . . . . . . . .2-9
Figure 2-5: Removing the Screws that Secure the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10
Figure 2-4: Replacing the Cover on the S2500 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10
Figure 2-6: Removing the Cover from the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11
Figure 2-7: Replacing the Cover on the S2500 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-12
Figure 2-8: Removing the Screws that Secure the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-13
Figure 2-9: Removing the Cover from the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-14
Figure 2-10: S2500 Blank Filler Panels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-15
Figure 2-11: Replacing the Cover on the S2500 Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-15
Figure 2-12: Removing the Screws that Secure the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-16
Figure 2-13: Removing the Cover from the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-17
Figure 2-14: Encryption Module Connector and Standoff Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-18
Figure 2-16: Removing the Screws that Secure the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20
Figure 2-17: Removing the Cover from the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-21
Figure 2-18: Locating the S2500 Encryption Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-22
Figure 2-20: Mounting Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24
Figure 2-21: Attaching Rubber Feet for Tabletop Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24
Figure 2-22: Stacking S2500s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-25
Figure 2-23: Attaching the Rack-Mounting Screws . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26
Figure 2-24: Attaching the S2500 to the Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26
Figure 2-25: Cabling the Power Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-27
Figure 2-26: Grounding (Earthing) the S2500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-28
Figure 2-27: Cabling the Ethernet Connector(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29
Figure 2-28: S2500 Ethernet LAN Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-30
Figure 2-29: Collision Domain Diameter Examples. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-32
Figure 2-30: Collision Domain Diameter with No Repeater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-33
Figure 2-31: Collision Domain Diameter with One Repeater. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-34
Figure 2-32: Collision Domain Diameter with Two Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-34
O CT OB ER 28 , 2 01 3 XI
FIGURES MNR S2500 HARDWARE USER GUIDE
Figure 2-33: Cabling a FlexWAN Serial Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37

Figure 2-34: Connecting the S2500 to a DTE Using a DCE Cable and a DTE Cable . . . . . . . . . . . . . . . . . . 2-38
Figure 2-35: Connecting the S2500 to a DCE Using a DTE Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-38
Figure 2-36: FlexWAN and RS-232 DTE Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
Figure 2-37: FlexWAN and RS-232 DCE Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-41
Figure 2-38: FlexWAN and V.35 DTE Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42
Figure 2-39: FlexWAN and V.35 DCE Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-43
Figure 2-40: FlexWAN and X.21 DTE Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-44
Figure 2-41: FlexWAN and X.21 DCE Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Figure 2-42: FlexWAN and RS-449 DTE Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-46
Figure 2-43: FlexWAN and RS-449 DCE Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-47
Figure 2-44: FlexWAN and EIA-530 DTE Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
Figure 2-45: S2500 WAN/Telco (T1/E1 CSU/DSU) Connector Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
Figure 2-46: Cabling a WAN/Telco (T1/E1 CSU/DSU) Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
Figure 2-47: MNR S2500 V.24 Connector (RJ-45) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Figure 2-48: Signal Diagram: MNR S2500 V.24 Interface to Base Station . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-52
Figure 2-49: Alternative Signal Diagram: S2500 V.24 Interface to Base Station. . . . . . . . . . . . . . . . . . . . . . 2-52
Figure 2-50: RJ45-to-25 D Cable Adapter Pin Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-53
Figure 2-51: Signal Diagram: MNR S2500 V.24 Interface to Modem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Figure 2-52: Signal Diagram: S2500 V.24 Interface to SRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
Figure 2-53: S2500 E&M Analog Connector (RJ-1CX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
Figure 2-54: MNR S2500 E&M Port-to-QUANTAR Base Station Interconnections . . . . . . . . . . . . . . . . . 2-60
Figure 2-55: S2500 Console Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
Figure 2-56: 9-pin-to-9-pin PC Cable (Null Modem Type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
Figure 2-57: 9-pin-to-25-pin Terminal Cable (Null Modem Type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-64
Figure 2-58: 9-pin-to-25-pin Modem Cable (Straight-Through Type). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
Figure 2-59: Location of Power Receptacle on S2500 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
Figure 3-1: S2500 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Figure 3-2: Enterprise OS Command-Line Interface Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Figure 4-1: Relationship Between Connectors, Paths, and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Figure 4-2: S2500 Path-to-Port Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Figure 4-3: S2500 Path-to-Port Mappings (V.24 Module in I/O Slot A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Figure C-1: S2500 System LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
Figure C-2: S2500 LAN (Ethernet) LEDs (LAN Port 1 on S2500 Base Unit) . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Figure C-3: S2500 LAN (Ethernet) LEDs (Optional 10BASE-T Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
Figure C-4: S2500 FlexWAN Serial LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11
Figure C-5: S2500 WAN/Telco (T1/E1 CSU/DSU) LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12
Figure C-6: S2500 V.24 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
Figure C-7: S2500 E&M Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
Figure C-8: Serial Loopback Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
Figure C-9: Rx-to-Tx Loopback Testing Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Figure C-10: Local Loopback Testing Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-24
Figure C-11: Line Partner Remote Loopback Testing Data Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-25
XII O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE FIGURES
Figure F-1: Applying Tamper Evidence Labels 1 and 2 to Secure the Front of the MNR S2500. . . . . . . . . F-2
Figure F-2: Applying Tamper Evidence Labels 3 and 4 to Secure the Rear of the MNR S2500 . . . . . . . . . F-3
O CT OB ER 28 , 2 01 3 XIII
LIST
OF
TABLES
TABLES
...................................
..
Table 1-1: S2500 Supported Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7
Table 1-2: Dial-Up and Leased Line Services Supported by S2500 Routers . . . . . . . . . . . . . . . . . . . . . . . . . .1-9
Table 1-3: Packet-Switched Services Supported by S2500 Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10
Table 1-4: Required EOS and LDAP Server Database Versions by Channel Type . . . . . . . . . . . . . . . . . . . .1-11
Table 1-5: CCGW LED Status Indicators (All Supported Channels In Service) . . . . . . . . . . . . . . . . . . . . . .1-12
Table 2-1: Environmental Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2
Table 2-2: 10BASE-T Cable Types and Emissions Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-30
Table 2-3: 100BASE-TX Cable Types and Emissions Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-31
Table 2-4: Maximum Cable Length in Example Collision Domain Diameters . . . . . . . . . . . . . . . . . . . . . . .2-35
Table 2-5: FlexWAN Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-39
Table 2-6: RS-232 DTE Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-40
Table 2-7: RS-232 DCE Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-41
Table 2-8: V.35 DTE Cable Pinouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-42
Table 2-9: V.35 DCE Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-43
Table 2-10: X.21 DTE Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-44
Table 2-11: X.21 DCE Cable Pinouts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-45
Table 2-12: RS-449 DTE Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-46
Table 2-13: RS-449 DCE Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-47
Table 2-14: EIA-530 DTE Cable Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-48
Table 2-15: MNR S2500 V.24 Connector Pin Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-51
Table 2-16: S2500 E&M Analog r Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-57
Table 2-17: Pin Functions for Analog Base Station Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-61
Table 2-18: Console Port Configuration Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-63
Table 3-1: LED Status at Successful Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3
Table 3-2: Command-Line Interface Syntax Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7
Table 3-3: Administrative Task Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
Table 4-1: S2500 Path/Port Syntax Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6
Table 4-2: S2500-Supported Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-17
Table C-1: S2500 WAN/Telco (T1/E1 CSU/DSU) Module LED Definitions . . . . . . . . . . . . . . . . . . . . . . . . . C-12
Table G-1: Troubleshooting MNR S2500 to TFTP/FTP Server File Transfers . . . . . . . . . . . . . . . . . . . . . . . . G-5
O CT OB ER 28 , 2 01 3 XV
LIST OF
PROCEDURES
& PROCESSES
PROCEDURES & PROCESSES

...................................
..
Procedure 2-1: Installing an Optional I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7
Procedure 2-2: Replacing an S2500 I/O Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10
Procedure 2-3: Removing an Optional I/O Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-13
Procedure 2-4: Installing an Optional Encryption Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-16
Procedure 2-5: Replacing an Optional Encryption Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20
Procedure 2-6: Stacking S2500 Routers with Brackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-25
Procedure 2-7: Installing an S2500 Router in a Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26
Procedure 2-8: Connecting a Chassis Ground (Earth). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-28
Procedure 2-9: Cabling the Ethernet (LAN) Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29
Procedure 2-10: Determining a Valid Fast Ethernet Collision Domain Diameter . . . . . . . . . . . . . . . . . . . . . . . . . .2-33
Procedure 2-11: Cabling the FlexWAN Serial Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-37
Procedure 2-12: Cabling a WAN/Telco (T1/E1 CSU/DSU) Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-49
Procedure 2-13: How to Connect the S2500 V.24 Module to a Base Station . . . . . . . . . . . . . . . . . . . . . . . . .2-52
Procedure 2-14: How to Connect the S2500 V.24 Module to a Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-53
Procedure 2-15: How to Connect the MNR S2500 to an SRU Card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-55
Procedure 2-16: Connecting a PC, Terminal, or Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-64
Procedure 3-1: Starting the S2500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2
Procedure 3-2: Logging on to the S2500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5
Procedure 3-3: Using the Command-Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8
Procedure 3-4: Using the Menu-Driven Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10
Procedure 3-5: Changing the Default Console Port Baud Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14
Procedure 3-6: Configuring the MNR S2500 to Perform IP Routing Functions . . . . . . . . . . . . . . . . . . . . . .3-18
Procedure 4-1: Configuring Ports and Paths for LAN (Ethernet) Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . .4-8
Procedure 4-2: Configuring FlexWAN Interfaces with DCE Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10
Procedure 4-3: Configuring FlexWAN Interfaces with DTE Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-11
Procedure 4-4: Configuring WAN/Telco (T1/E1 CSU/DSU) Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-13
Procedure C-1: Entering the S2500 Firmware Boot Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
Procedure C-2: Restoring the S2500 to Factory Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Procedure C-3: Performing a Loopback Test on the Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-22
Procedure C-4: Performing an Rx-to-Tx Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Procedure C-5: Performing a Local Loopback Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-24
Procedure C-6: Performing a Rx-to-TX Loopback Test on the Link Partner . . . . . . . . . . . . . . . . . . . . . . . . C-25
Procedure C-7: Configuring the Dump Destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-28
Procedure C-8: Creating Full Dump Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-30
Procedure C-9: Verifying the TFTP Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-31
Procedure C-10: Creating a Partial Dump File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-33
Procedure D-1: Reloading the System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
Procedure F-1: How to Secure the MNR S2500 with Tamper Evidence Labels . . . . . . . . . . . . . . . . . . . . . . F-2
O CT OB ER 28 , 2 01 3 XVII
PROCEDURES & PROCESSES CHAPTER :
Procedure G-1: How to Copy Files between an MNR S2500 and a TFTP Server . . . . . . . . . . . . . . . . . . . . . G-2
Procedure G-2: How to Copy Files between an MNR S2500 and an FTP Server . . . . . . . . . . . . . . . . . . . . . G-3
Procedure G-3: How to Configure FTP Login Parameters on an MNRS2500 . . . . . . . . . . . . . . . . . . . . . . . . G-4
XVIII O C T OBE R 2 8, 20 1 3
ABOUT
THIS
GUIDE
ABOUT THIS GUIDE

...................................
....
This guide includes hardware installation, basic software configuration, and cabling
instructions for Motorola Network Router (MNR) S2500 routers.
WHO SHOULD USE THIS GUIDE?

...................................
..
This guide is intended for:
Experienced network administrators
Experienced system integrators
O CT OB ER 28 , 2 01 3 XIX
ABOUT THIS GUIDE HOW THIS GUIDE IS ORGANIZED
HOW THIS GUIDE IS ORGANIZED

...................................
..
This guide is organized as follows:
Chapter 1, S2500 Overview." This chapter provides an overview of the S2500
hardwareincluding descriptions of the supported interfacesand summarizes
how to implement the S2500 in your network.
Chapter 2, Installing the S2500 Hardware." This chapter describes how to install
the S2500 hardware.
Chapter 3, Logging on and Performing Administrative Tasks." This chapter
describes how to start up the S2500, log on, use the command-line interface, and
perform basic administrative tasks.
Chapter 4, Configuring Paths, Ports, and Connectors." This chapter provides
conceptual information about ports, paths, and connectors, and basic
configuration procedures for each of the interfaces on the S2500.
Appendix A, Compliance. This appendix provides information about agency
approvals and regulatory compliance.
Appendix B, Technical Support. This appendix tells you how to contact
Motorola for technical support for the S2500.
Appendix C, Troubleshooting. This appendix provides troubleshooting
procedures, including information on the S2500 firmware boot monitor and LED
descriptions.
Appendix D, Reloading the System Software. This appendix describes how to
reload your system software if the boot image has been accidentally deleted or
corrupted, or if the S2500 is unable to boot.
Appendix E, SysconF Command Menus. This appendix describes how to
configure the SysconF menu parameters to customize the operation of the S2500.
Appendix F, Installing Tamper Evidence Labels. This appendix describes how
to apply tamper evidence labels on the MNR S2500 to meet Common Criteria
requirements, and how to remove tamper evidence labels from the power
receptacle prior to connecting power to the unit.
Appendix G, Copying Files to and From a TFTP or FTP Server. This appendix
describes how to copy files between the MNR S2500 and a TFTP or FTP server.
XX O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE ABOUT THIS GUIDE
RELATED DOCUMENTATION
...................................
..
In addition to this guide, the following documents may help you use Enterprise OS
software and manage your S2500 routers:
Enterprise OS Software Reference Guide Provides detailed information about
commands and syntax for all service parameters.
Enterprise OS Software User Guide Provides information about how to use
Enterprise OS (EOS) software to operate and configure your router.
To access the manuals listed above, extract the .tar file from the Motorola Network
Router EOS CD-ROM onto a directory on your PC and navigate to:
X:/<directory>/aa.b.c.dd/docs
where X:/ is the drive letter for the directory, <directory> is the name of the directory
into which you extracted the .tar file, and aa.b.c.dd is the specific build of EOS software
provided on the CD-ROM. For example, if you extracted the .tar file into directory
D:/EOS_SW, and the CD-ROM contains EOS version 16.6.0.26, you would navigate to:
D:/EOS_SW/16.6.0.26/docs
The manuals listed above are also available on the Motorola Online website:
https://motonline.mot-solutions.com
To access the manuals, select Resource Center -> Product Information -> Manuals ->
Network Infrastructure -> Routers and Gateways
O CT OB ER 28 , 2 01 3 XXI
ABOUT THIS GUIDE CONVENTIONS
CONVENTIONS
...................................
..
The following tables list conventions that are used throughout this guide.
NOTICE CONVENTIONS
Notice Type Alerts you to...
Important features or instructions

NOTE
Crucial features or instructions

IMPORTANT
Risk of personal injury, system damage, or loss of

CAUTION data
Risk of severe personal injury

WARNING
XXII O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE ABOUT THIS GUIDE
TEXT CONVENTIONS
Convention Description
Syntax Evaluate the syntax provided and supply the appropriate

values. Placeholders for values you must supply appear in
angle brackets. Example:
Enable RIPIP using:
SETDefault !<port> -RIPIP CONTrol = Listen
In this example, you must supply a port number for <port>.
Commands Enter the command exactly as shown in text and press

<Return> or <Esc>. Example:
To remove the IP address, enter:
SETDefault !0 -IP NETaddr = 0.0.0.0
This guide generally gives the full form of a command in
uppercase and lowercase letters. However, you can
abbreviate commands by entering only the uppercase letters
and the appropriate value. Commands are not case-sensitive.
Screen displays This typeface represents information as it appears on the

screen.
User entries This typeface represents text that you type or enter.
<Key> names Key names appear in the user entry typeface written with
angle brackets, such as <Return> or <Esc>.
Key names linked with a plus sign (+) indicate that you must
press two or more keys simultaneously. Example:
Press <Ctrl>+<Alt>+<Del>.
Words in italicized Italicized text emphasize a point or denotes new terms at the
type place where they are defined in the text.
Words in bold-face Bold text denotes option, parameter, and service names;
type menu commands; button names; and key features.
O CT OB ER 28 , 2 01 3 XXIII
CHAPTER
S2500 OVERVIEW 1
1
...................................
....
This chapter provides an overview of the S2500 hardwareincluding descriptions of
the supported interfacesand summarizes how to implement the S2500 in your
network.
The information in this chapter is organized as follows:
S2500 Hardware Overview on page 1-2
S2500 Supported Interfaces on page 1-7
Using the S2500 in Your Network on page 1-9
NOTE
The services supported by the S2500 depend on which, if any, optional I/O
modules are installed in the router.
O CT OB ER 28 , 2 01 3 1-1
S2500 HARDWARE OVERVIEW CHAPTER 1: S2500 OVERVIEW
S2500 HARDWARE OVERVIEW

...................................
..
The S2500 is part of the Motorola Network Router (MNR) family of modular routers,
incorporating two I/O slots for WAN and LAN connectivity and one slot for analog
connectivity. The S2500 supports a variety of hardware configurations, constructed by
adding optional modules to the base system, which provides a single 10/100 Mbps
Ethernet interface.
The S2500 supports the following optional modules:
WAN/Telco (T1/E1 CSU/DSU) (one port; supported in WAN/LAN I/O module slot
A and/or B)
FlexWAN Serial (one port; supported in WAN/LAN I/O module slot A and/or B)
Ethernet 10BASE-T (one port; supported in WAN/LAN I/O module slot A or B)
NOTE
The S2500 also supports hardware configurations with two 10BASE-T
modules for 10BASE-T connectivity; however, performance levels for these
configurations may not match your system requirements.
NOTE
The 10BASE-T module does not support tagged VLAN ports with certain
versions of EOS software certified for system releases prior to the
ASTRO 25 7.8 system release. If you attempt to configure a tagged VLAN
port on the 10BASE-T module interface of an S2500 router running a version
of EOS software that does not support tagged VLAN ports, the system
returns an error message similar to the following:
VLANs are currently supported only on Ethernet.
V.24 (two ports; supported in WAN/LAN I/O module slot A and/or B)
NOTE
You can install the V.24 module in either I/O slot A or I/O slot B; however,
the software supports only one V.24 module per router.
Conventional-to-IP Interface Kit (consists of a four-wire E&M module and a DSP
SIMM; supported in the analog slot)
For further details about the interfaces supported on S2500 routers, see S2500
Supported Interfaces on page 1-7.
The following sections provide an overview of key hardware components on S2500
routers.
1-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE S2500 HARDWARE OVERVIEW
FRONT PANEL
The front panel of the S2500 (Figure 1-1, Figure 1-2, and Figure 1-3) features the
following components:
Service interface ports and LEDs The S2500 base unit provides a single
10BASE-T/100BASE-TX Ethernet port. Additional interface ports are supported
based on the hardware configuration.
Console port Use this port to connect the S2500 to a PC, terminal, or modem.
See Connecting a PC, Terminal, or Modem on page 2-63 in for details.
Reset button You can press the this button to reboot the S2500.
Hardware interrupt button You can use the hardware interrupt button to
access the firmware boot monitor for initial software installation. For details about
how to use the boot monitor, see Using the S2500 Firmware Boot Monitor on
page C-2.
WARNING
Use only a nonconductive object, such as a plastic stylus, to press the
reset button or the hardware interrupt button. Do not use the tip of a
pencil. Graphite particles from the pencil may cause you to receive an
electric shock and may damage components on the motherboard.
System LEDs These LEDs indicate the status of the system as a whole. See
Appendix D, Reloading the System Software for details.
Figure 1-1 illustrates the front panel of the S2500 configured with a T1/E1 CSU/DSU
module in I/O module slot A and a FlexWAN serial module in I/O module slot B
FIGURE 1-1 FRONT PANEL OF THE S2500 (WAN/TELCO (T1/E1) MODULE IN SLOT A; FLEXWAN MODULE IN SLOT B)
FlexWAN
T1/E1 Link, Serial Port
Active, and (RS-232, V.35,
Fault LEDs X.21, RS-449,
10BASE-T/100BASE-TX or EIA-530)
Ethernet FlexWAN
Port WAN/Telco
(RJ-45) Port Link, Active, and
(RJ-45) Fault LEDs

"# SYSTEM
LAN
T1/E1

CSU/

Console !
DSU Status
"! #

$

4 5 6 7
1 I/O Module A 2 I/O Module B 3 Analog
T1/E1 FlexWAN System Fwd and

Module in Module in Console Power/Fault LEDs
LAN/Ethernet I/O Slot A I/O Slot B Port
Link, Active, Fault, (DB-9) System
and 100Mb LEDs Hardware Interrupt Button Run, Load,
Reset Button and Test LEDs
System
Status
LEDs
O CT OB ER 28 , 2 01 3 1-3
Figure 1-2 illustrates the front panel of the S2500 configured with a T1/E1 CSU/DSU
module in I/O module slot A and a 10BASE-T module in I/O module slot B.
FIGURE 1-2 FRONT PANEL OF THE S2500 (WAN/TELCO (T1/E1) MODULE IN SLOT A; 10BASE-T MODULE IN SLOT B)
T1/E1 Link, 10BASE-T

Active, and Ethernet Port
Fault LEDs (RJ-45)
10BASE-T/100BASE-TX
Ethernet 10BASE-T
Port WAN/Telco
Port Link, Transmit, Receive,
(RJ-45) and Collision LEDs
(RJ-45)

SYSTEM
LAN
T1/E1 "
CSU/

Console
DSU 10BaseT Status

#
!
4 5 6 7
1 I/O Module A 2 I/O Module B 3 Analog Module
T1/E1 10BASE-T System Fwd and

Module in Module in Console Power/Fault LEDs
LAN/Ethernet I/O Slot A I/O Slot B Port
System
Status
LEDs
1-4 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE S2500 HARDWARE OVERVIEW
Figure 1-3 illustrates the front panel of the S2500 configured with a V.24 module in I/O
module slot A and an E&M module in the analog module slot.
NOTE
The S2500 used as a conventional channel gateway (CCGW) ships with both
a V.24 module and E&M module installed. Although both modules are
physically present in the router, the site type configuration received from
the LDAP server determines the function of the CCGW, and only the
corresponding module is operational:
--If the site type is configured as digital, only the V.24 module is
operational.
--If the site type is configured as analog, only the E&M module is
operational.
FIGURE 1-3 FRONT PANEL OF THE S2500 (V.24 MODULE IN I/O SLOT A; E&M MODULE IN ANALOG SLOT)
V.24 Serial
10BASE-T/100BASE-TX Ports (RJ-45)
Ethernet E&M Analog Ports (RJ-1CX)
Port
(RJ-45) Port Status LEDs E&M Analog Port Status LEDs

V.24 SYSTEM
LAN

Console
Status

!
4 5 6 7
1 I/O Module A 2 I/O Module B 3 Analog
V.24 System Fwd an

Module in E&M Module in Console Power/Fault LED
LAN/Ethernet I/O Slot A Analog Slot Port
System
Status
LEDs
O CT OB ER 28 , 2 01 3 1-5
REAR PANEL
The rear panel of the S2500 supports a power receptacle, grounding (earthing) screw,
and configuration label, as shown in Figure 1-4.
FIGURE 1-4 REAR PANEL OF THE S2500
Power Configuration label

Grounding screw
receptacle
To apply power to the S2500, plug in the power cord. To remove power from the S2500,
unplug the power cord. For grounding (earthing) instructions, see Connecting a
Chassis Ground (Earth) on page 2-28. For details about starting the S2500, see
Starting the System on page 3-2.
1-6 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE S2500 SUPPORTED INTERFACES
S2500 SUPPORTED INTERFACES

...................................
..
Table 1-1 lists the interfaces supported by the S2500. The interfaces available on your
system depend on the hardware configuration.
TABLE 1-1 S2500 SUPPORTED INTERFACES
Interface # of Ports Description

Ethernet 1 LAN port that provides connection to Ethernet LANs
(part of S2500 base system) using either 10BASE-T or 100BASE-TX Ethernet
FlexWAN Serial 1 per I/O module; High-speed multifunction serial interfaces that provide
On each S2500 router, two I/O connection to industry- standard V.35, RS-232, RS-449,
module slots are available for the EIA-530, or X.21 Data Communications Equipment
installation of FlexWAN serial (DCE) or Data Terminal Equipment (DTE) serial
modules. devices.
WAN/Telco 1 per I/O module; On each S2500 WAN/Telco interfaces that support T1/E1 CSU/DSU.
router, two I/O module slots are
available for the installation of
WAN/Telco modules.
10BASE-T 1 per I/O module; LAN port that provides connection to Ethernet LANs
(optional) On each S2500 router, using 10BASE-T Ethernet.
one I/O module slot is available
for the installation of a 10BASE-T
module.
NOTE
The 10BASE-T module is supported in either
I/O module slot (A or B). The S2500 also
supports hardware configurations with two
10BASE-T modules for 10BASE-T
connectivity; however, performance levels
for these configurations may not match your
system requirements.
NOTE
The 10BASE-T module does not support
tagged VLAN ports with certain versions of
EOS software certified for system releases
prior to the ASTRO 25 7.8 system release. If
you attempt to configure a tagged VLAN
port on the 10BASE-T module interface of an
S2500 router running a version of EOS
software that does not support tagged
VLAN ports, the system returns an error
message similar to the following:
VLANs are currently supported
only on Ethernet.
(Continued)
O CT OB ER 28 , 2 01 3 1-7
S2500 SUPPORTED INTERFACES CHAPTER 1: S2500 OVERVIEW
TABLE 1-1 S2500 SUPPORTED INTERFACES (CONTINUED)
Interface # of Ports Description

V.24 2 per I/O module; On each S2500 Provides two V.24 serial ports. Each port communicates
router, one I/O module slot is at 9600 bps. The S2500 ports connect either directly to a
available for the installation of a base station or to a modem to support CCGW digital
V.24 module. conventional operation.
NOTE
The V.24 modules require the EOS software
version certified for the digital conventional
feature. You can install the V.24 module in
either I/O module slot (A or B); however, the
software supports only one V.24 module per
router.
Conventional- 4 per I/O module; On each 2500 Provides 4 four-wire with E&M relay interfaces to
to-IP (E&M) router, one I/O slot is available for analog conventional base stations. In addition to
the installation of an E&M performing normal IP routing tasks, an S2500 router
module, which is part of the configured with E&M expansion hardware provides an
conventional-to-IP interface kit. analog-to-IP network gateway for analog conventional
calls.
NOTE
The S2500 Conventional-to-IP Kit requires
the following:
--An MNR S2500 router base unit model
number ST2500B (part number CLN1713B).
The ST2500B base unit features a new
revision of the programmable logic device
(PLD) on the motherboard. The base unit
model number and part number are listed
on the rear of the router.
--EOS software version 13.0.0.50 or higher.
1-8 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE USING THE S2500 IN YOUR NETWORK
USING THE S2500 IN YOUR NETWORK

...................................
..
The S2500 integrates voice and data traffic over a single converged network,
compressing and routing voice calls between telephones or PBXs through an IP data
network. It is ideal for maintaining connectivity among small, midsize, and large
branch offices and the corporate LAN.
TELCO SERVICES
To use the S2500s WAN functionality, you must buy lines and services from a
telecommunications company (Telco). Services include but are not limited to dial-up
lines, leased lines, and packet-switched services.
Dial-up lines allow you to dial your destination when necessary and hang up when you
no longer need the connection. A leased line is always available between two locations.
Dial-up lines use the Point-to-Point Protocol (PPP). Leased lines typically use either
PPP or Frame Relay.
Packet-switched services, such as Frame Relay, use a combination of leased or dial-up
lines with Telco-owned switching. Frame Relay is a typical protocol used for packet-
switched services.
Table 1-2 and Table 1-3 describe the dial-up, leased, and packet-switched services
supported by S2500 routers.
TABLE 1-2 DIAL-UP AND LEASED LINE SERVICES SUPPORTED BY S2500 ROUTERS
Data Transfer
Telco Line Protocol Serial Device Requirements
Rate
Dial-Up Lines:
Plain Old Telephone PPP Modem Up to 115 Kbps
Service (POTS)
ISDN PPP Terminal Adapter Up to 128 Kbps
Leased Lines:
T1 / Fractional T1 Frame Relay, CSU/DSU Up to 1.544 Mbps
PPP
E1/Fractional E1 Frame Relay, CSU/DSU Up to 2.048 Mbps
PPP
Digital Data Service PPP CSU/DSU Up to 64 Kbps
(DDS)
O CT OB ER 28 , 2 01 3 1-9
USING THE S2500 IN YOUR NETWORK CHAPTER 1: S2500 OVERVIEW
TABLE 1-3 PACKET-SWITCHED SERVICES SUPPORTED BY S2500 ROUTERS
Packet-Switched Serial Device

Telco Line Data Transfer Rate
Services/Protocol Requirements
Frame Relay Leased line CSU/DSU 1.544 Mbps
USING PPP ON DIAL-UP AND LEASED LINES

All dial-up and many leased lines use PPP. If you want to use multiple PPP lines or
channels to connect to the same destination, you can bundle them together using
Multilink PPP.
USING PACKET-SWITCHED NETWORK SERVICES

You can use packet-switched services with your S2500 instead of dial-up or leased lines
to leverage the Telco-owned switching infrastructure.
Frame Relay provides a packet-switched network that transfers data between DTEs,
which can be routers, bridges, and host computers, by creating virtual circuits and
using DCEs to transfer the data to its destination.
Frame Relay has been designed to work within complex internetworking environments
with extensions referred to as the local management interface (LMI). LMI provides
information about all devices that are accessible on the Frame Relay network by listing
all data link connection identifiers (DLCIs) connecting the local system with the remote
ones. The LMI improves reliability between the DTE and DCE through frequent
exchange of keepalive packets that contain status information.
1-10 O C T OBE R 2 8, 20 1 3
CCGW FUNCTIONALITY
The MNR S2500 conventional channel interface (also referred to as the conventional
channel gateway (CCGW)) supports the following channel types:
Analog conventional interfaces 4-wire analog audio connections (across LAN
or WAN links) with certain types of Motorola public safety network equipment
that support digital audio connections.
Digital conventional (digital over V.24 interface) interfaces V.24 ports carrying
digital audio (across LAN or WAN links) with certain types of Motorola public
safety network equipment that support digital audio connections.
The site type (analog or digital) is configured in the LDAP database.
When used for analog conventional operation, the S2500 is configured with an
E&M module and DSP SIMM in the routers analog I/O slot. The E&M module
supports four analog ports and four analog conventional channels.
When used for digital conventional operation, the S2500 is configured with a V.24
module in either the routers I/O slot A (port 2) or I/O slot B (port 3). The V.24
module supports two digital ports and two digital conventional channels.
Table 1-4 provides a matrix of the EOS software version and LDAP server database
version required for each channel type.
Issue the SHow - SYS VERSion command to view the EOS software
version.
Issue the SHOW -CCGW CCGWDBVersion command to view the
LDAP server database version.
TABLE 1-4 REQUIRED EOS AND LDAP SERVER DATABASE VERSIONS BY CHANNEL TYPE
Required LDAP Server

Channel Type Required EOS Version
Database Version
Analog conventional 15.3 or higher A73 or higher
Digital conventional 15.4 or higher A76 or higher
If the CCGW receives a configuration from the LDAP server, and the corresponding
hardware does not exist on the box (a V.24 module for digital conventional channels, or
an E&M module for analog conventional channels), the CCGW:
Accepts the configuration.
Sends a state change trap (ccgwChannelStateChangeTrap) with channel state
DOWN, and fault cause 6 (User Configured Channel).
CCGW commands are executed in the router boot.cfg file upon router bootup. After
the boot.cfg file has been executed, EOS initializes CCGW, which sets up
communication with the network management systems LDAP server. EOS then listens
to the UDP notification port and configures the CCGW based on the network
management systems LDAP configuration.
O CT OB ER 28 , 2 01 3 1-11
A CCGW configuration file (CCGWDB) is created on the EOS flash. This file contains
the latest CCGW configuration from the network management LDAP server. It is
updated when changes are received from the network management LDAP server after
the CCGW router has been rebooted and is used for bootup persistence. If the CCGW
cannot communicate with the LDAP server, it attempts to read the configuration from
the EOS flash.
NOTE
The CCGWDB file is refreshed from the LDAP server. When a router is
replaced, the LDAP server is the source for refreshing the CCGWDB file.
Table 1-5 describes how the S2500 E&M port and V.24 port LEDs should appear if all
supported channels are in-service, depending on the channel type.
TABLE 1-5 CCGW LED STATUS INDICATORS (ALL SUPPORTED CHANNELS IN SERVICE)
Channel Type E&M LEDs V.24 LEDs
Analog conventional Green Off
Digital conventional or Off Green

secure-capable digital
E&M INTERFACE OVERVIEW

The E&M physical interface was developed for use in the analog tie trunks used to
interconnect PBXs. The interface has two line-control signals (the E-lead and the M-
lead) and separate signals for audio. In the CCGW implementation, the E&M interface
controls the state of the E-lead and monitors the state of the M lead, while the other side
of the connections monitors the E-lead and controls the M-lead. The specific logical
state of either the E-lead or the M-lead control lines corresponds to whether electrical
current is flowing (the Off-Hook state) or not flowing (the On-Hook state) through the
leads.
IMPORTANT
The definitions for the E-lead and M-lead used on the CCGW are the reverse
of most other pieces of network equipment.
Five different E&M signalling schemes are defined (E&M Types I, II, III, IV, and V),
although only Types I, II, III, and V are in common use. The CCGW E&M interface
supports tie line side E&M Types I, II, III, and V (all four ports set to the same type) and
only 4-wire audio. The E&M interface on the S2500 router is configured to operate in
E&M Type II mode.
1-12 O C T OBE R 2 8, 20 1 3
CONVENTIONAL IV&D
Conventional IV&D adds data service to the existing voice-only analog conventional
and digital conventional architecture. The CCGW provisions and integrates voice calls
and data transport simultaneously.
The CCGW call manager interacts with the CCGW data manager to mitigate voice and
data contention. To ensure that voice calls are not compromised while data
transmission is in progress, a single outbound call is buffered up to 1200 ms for a
channel. Upon finishing the transmission of an outbound packet PDU, the buffered
audio is played out.
ENCRYPTION SUPPORT
Beginning with EOS software version 15.0, the MNR S2500 router supports the
following security features:
Data encryption (Data Encryption Standard (DES), Triple DES (3DES), and
Advanced Encryption Standard (AES) algorithms)
Data authentication (Message Digest 5 (MD5) algorithm and Secure Hash
Algorithm (SHA))
Public key execution (Diffie-Hellman Group 1, Group 2, Group 5, and Group 14
negotiation)
The S2500 supports encryption of data over Ethernet and Frame Relay links using the
following protocols under the EOS CRYPTO service:
IPSec provides security at the network layer. Because it is integrated into IP itself,
IPSec adds security to any link, regardless of what application you are using.
IP Security Protocol (IPSec) tunnel mode Tunnel mode security associations
protect IP traffic forwarded by the router on IPSec tunnel ports. You can use
IPSec with the following tunneling protocols: PPTP, L2TP, and IPIP. See the
Configuring L2Tunnel Connections chapter in the Enterprise OS Software
User Guide for more information about PPTP/L2TP.
IPSec transport mode Transport mode security associations protect traffic
that is viewed on an end system from an IPSec perspective. For example,
you can use transport mode security with PPTP/L2TP/IPIP tunnels or to
secure network management traffic such as Telnet or SNMP.
FRF.17 with IKE negotiation provides security at the link layer and adds security
to Frame Relay links only. IKE negotiates the shared session keys used to encrypt
or decrypt data messages with the peer and passes these keys to the FRF.17
protocol. IKE-negotiated session keys allow the FRF.17 protocol to further secure
its data channel.
O CT OB ER 28 , 2 01 3 1-13
ENCRYPTION REQUIREMENTS
MNR S2500 encryption requires the following:
An encryption-capable MNR S2500 router with an encryption module (ST2516A).
installed.
NOTE
Only the MNR S2500 router base unit model number S2500B with part
number CLN1713E or higher is certified for encryption. The base unit model
and part numbers are listed on the rear of the router.
NOTE
You can add an encryption module to a router that is certified for an
encryption module but is initially installed without the encryption module.
For details about how to install the hardware encryption module, see
Installing An Encryption Module on page 2-16.
EOS software version 15.0 or higher, XS package.
1-14 O C T OBE R 2 8, 20 1 3
CHAPTER
INSTALLING THE S2500

2
HARDWARE 2
...................................
....
This chapter describes how to install an MNR S2500 router.
Pre-Installation Considerations on page 2-2
Installing, Replacing, and Removing Optional Modules on page 2-5
Mounting the S2500 on page 2-24
Cabling the Connectors on page 2-27
Connecting a PC, Terminal, or Modem on page 2-63
Powering the Router On and Off on page 2-66
O CT OB ER 28 , 2 01 3 2-1
PRE-INSTALLATION CONSIDERATIONS CHAPTER 2: INSTALLING THE S2500 HARDWARE
PRE-INSTALLATION CONSIDERATIONS
...................................
..
Before you install an S2500 router, you should consider the environmental conditions
your site must meet to maintain normal operation and the tools and equipment you
will need to install the router.
SELECTING THE INSTALLATION SITE

Table 2-1 lists the environmental requirements of the S2500. Be sure that the installation
site you select for the router meets these requirements. Keep in mind that the unit
requires proper ventilation and consider present and future cabling requirements.
TABLE 2-1 ENVIRONMENTAL REQUIREMENTS
Minimum
Maximum Requirement
Requirement
Temperature
Operating 0 C 50 C
Non-operating -30 C 60 C
Altitude
At Operating 10,000 ft
Temperature Range
At 0 C 40,000 ft
Relative Humidity
At Operating 5% noncondensing 95% noncondensing

Temperature Range
At Non-operating 5% noncondensing 95% noncondensing

Temperature Range
Vibration .25G, Sine wave, 5-500-5 Hertz
2-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE PRE-INSTALLATION CONSIDERATIONS
GATHERING THE REQUIRED EQUIPMENT
Before you begin unpacking and installing the S2500, gather the items you will need in
order to complete the installation:
Terminal, PC, or modem for console connection.
Pan-head screws (4) Optional, for rack-mounting.
Cables
10BASE-T or 100BASE-TX Ethernet cables Use 10BASE-T or
100BASE-TX cabling for the LAN connector provided on the base system.
Use 10BASE-T cabling for the LAN connector provided on the 10BASE-T
module.
Serial cables Use FlexWAN-to-RS-232, V.35, X.21, or RS-449 (DTE or
DCE), or FlexWAN-to-EIA-530 (DCE only) cabling (required only if the
S2500 is configured with a FlexWAN module). See FlexWAN Serial
Connectors and Serial Cables on page 2-39 for more information about
ordering FlexWAN cables from Motorola.
RJ-45 cables Use RJ-45 cabling for the WAN/Telco (T1/E1 CSU/DSU)
connectors (required only if the S2500 is configured with a T1/E1 module)
V.24 null modem cables Use V.24 null modem cables to connect the V.24
ports to a base station (required only if the S2500 is configured as a digital
conventional CCGW and is being connected directly to a base station)
RJ45-to-25-pin D cable adapter (CLN8488A) Use this adapter to
connect the V.24 ports to a modem (required only if S2500 is configured as a
digital conventional CCGW and is being connected to a modem)
Terminal, PC, or modem cable
CAUTION
To eliminate cable noise emission in excess of FCC regulations, part
15, subpart J, and EN55022B, all interconnection cables should be
equipped with shielded connectors, the backshells of which must
completely surround the cable shield.
For more information on cables, including pinouts, see Appendix C,

Troubleshooting.
#6 AWG (minimum) grounding (earthing) wire with UL-listed lug and
grounding (earthing) screw Required only if your network topology requires
an additional grounding (earth) on the chassis, separate from the AC ground.
NOTE
If the length of the grounding (earthing) wire must exceed 4 meters before it
is terminated, grounding (earthing) wire larger than #6 AWG is required.
See the Motorola R56 manual Standards and Guidelines for Communication
Sites for details.
O CT OB ER 28 , 2 01 3 2-3
PRE-INSTALLATION CONSIDERATIONS CHAPTER 2: INSTALLING THE S2500 HARDWARE
REVIEWING THE CONTENTS OF THE SHIPPING

CARTON
When you receive the S2500, review the contents of the shipping carton to ensure that
the following items are included:
MNR S2500 router
Power cable
Rack-mount kit (see Figure 2-20)
EOS Software and User Documentation CD and CD booklet
NOTE
The software is preinstalled in the flash memory drive of the S2500 and
automatically loads when you turn on the power. Software provided on a
CD is for software recovery purposes only
Release Notes
License agreement
2-4 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE INSTALLING, REPLACING, AND REMOVING OPTIONAL MODULES
INSTALLING, REPLACING, AND REMOVING

OPTIONAL MODULES
...................................
..
This section provides procedures for installing, replacing, and removing the optional
I/O and encryption modules supported on the MNR S2500 router. Before you rack-
mount the S2500, you must install any optional modules included in the hardware
configuration.
IMPORTANT
In order to install or replace optional I/O and encryption modules, you must
remove the MNR S2500 cover. If the MNR S2500 is secured with tamper
evidence labels, removing the cover will break these labels. You must either
return the unit to Motorola for optional module installation or replacement
or follow the instructions in Securing the MNR S2500 with Tamper
Evidence Labels on page F-2 to install new tamper evidence labels after
you have installed or replaced an optional module.
CAUTION
ESD PRECAUTIONS
When removing or installing modules, take the following precautions
to prevent ESD (electrostatic discharge) from damaging the internal
components of the router:
Always wear a properly-grounded anti-static wrist strap.
Transport static-sensitive components in anti-static packaging.
Keep static-sensitive components in their anti-static packaging until

you are ready to install them.
--Just before removing components from their anti-static packaging,

discharge static electricity from your body by touching an unpainted
metal surface.
--When you handle modules, place them printed circuit side down on a
nonconducting, static-free, flat surface.
O CT OB ER 28 , 2 01 3 2-5
INSTALLING, REPLACING, AND REMOVING OPTIONAL MODULES CHAPTER 2: INSTALLING THE S2500 HARDWARE
INSTALLING AN I/O MODULE

This section describes how to install the optional I/O modules supported on the MNR
S2500 router.
The S2500 provides two I/O slots and one analog module slot, which support optional
modules as follows:
2 WAN/LAN I/O slots support any of the following modules:
FlexWAN
WAN/Telco (T1/E1 CSU/DSU)
10BASE-T
NOTE
The 10BASE-T module is supported in either I/O module slot (A or B). The
S2500 also supports hardware configurations with two 10BASE-T modules
for 10BASE-T connectivity; however, performance levels for these
V.24
NOTE
The V.24 module is supported in either I/O module slot (A or B) and requires
the EOS software version certified for the digital conventional feature.
1 analog I/O slot supports the E&M module, which is part of the Conventional-to-
IP Interface Kit.
IMPORTANT
The Conventional-to-IP Interface Kit requires an MNR S2500 base unit
model number ST2500B (part number CLN1713B). The base unit model
number and part number are listed on the rear of the router. If you install the
Conventional-to-IP Interface Kit in a router at a previous hardware revision
level, it will not function. In addition, if you are running a version of
software lower than 13.0.0.50 on the S2500 router, you must upgrade to at
least version 13.0.0.50 BEFORE installing the Conventional-to-IP Interface
Kit.
2-6 O C T OBE R 2 8, 20 1 3
To install an optional I/O module in the S2500 chassis, follow Procedure 2-1.
PROCEDURE 2-1 INSTALLING AN OPTIONAL I/O MODULE
1 Remove the cover from the S2500 chassis.
1.1 Unplug the power cord from the S2500 system and remove any cables that may be installed on
the chassis.
WARNING
Always unplug the S2500 power cord before removing the router cover.
1.2 Remove the two screws that secure the cover to the chassis on the rear of the router, as illustrated
in Figure 2-1.
FIGURE 2-1 REMOVING THE SCREWS THAT SECURE THE CHASSIS
Remove screws
(Continued)
O CT OB ER 28 , 2 01 3 2-7
PROCEDURE 2-1 INSTALLING AN OPTIONAL I/O MODULE (CONTINUED)
1.3 Remove the cover from the chassis, as illustrated in Figure 2-2.
FIGURE 2-2 REMOVING THE COVER FROM THE CHASSIS
With the front panel facing you, push down on cover with both hands
Slide cover back slightly
Lift cover away from chassis
(Continued)
2-8 O C T OBE R 2 8, 20 1 3
2 If you are installing the conventional-to-IP interface kit, install the DSP SIM using Figure 2-3 as a
guide.
2.1 Locate the rearmost DSP SIMM slot and insert the DSP SIMM into the slot at a 30 degree angle,
with the SIMM angled forward (toward the front of the chassis).
2.2 Press back on the SIMM to seat it into position. The socket clips automatically engage the SIMM
as you move it into position.
FIGURE 2-3 I/O MODULE SLOT, CONNECTOR, AND STANDOFF LOCATIONS ON THE S2500 MOTHERBOARD
Match to standoffs
on motherboard T1/E1 CSU/DSU Module
E&M Module
Install DSP SIMM
in rearmost DSP
SIMM slot
Standoffs
Match connectors on
I/O Module Slot A underside of modules to
connectors on motherboard
I/O Module Slot B
Analog Module Slot

Connectors
3 Using Figure 2-3 as a guide, locate the slot on the S2500 motherboard into which you want to install
the module and the corresponding standoffs and connector.
4 Pushing from the inside of the chassis, pop out the blank filler panel on the I/O or analog module slot.
5 Insert the new module.

5.1 Coming from the back of the chassis, insert the front of the module through the front panel of
the chassis.
5.2 Line up the connector pins carefully.
5.3 Press down gently on the module.
(Continued)
O CT OB ER 28 , 2 01 3 2-9
6 Secure the module with the two screws provided with the module.
IMPORTANT
To ensure that the module is seated properly, you must tighten the screws to a torque of
6.5 - 8.5 inch-pounds.
7 Replace the cover and secure it to the chassis with the two screws you removed in step 1.2, as
illustrated in Figure 2-4.
FIGURE 2-4 REPLACING THE COVER ON THE S2500 CHASSIS
REPLACING AN I/O MODULE
To replace an optional S2500 I/O module, follow Procedure 2-2.
PROCEDURE 2-2 REPLACING AN S2500 I/O MODULE
1 Remove the cover from the chassis.
the chassis.
WARNING
1.2 Remove the two screws that secure the cover to the chassis, as illustrated in Figure 2-5.
Remove screws
(Continued)
2-10 O C T OBE R 2 8, 20 1 3
2 If you are replacing the DSP SIMM, follow these steps:

2.1 Locate the DSP SIMM (installed in the rearmost DSP SIMM slot) and gently remove it.
2.2 Insert the new DSP SIMM into the slot at a 30 degree angle, with the SIMM angled forward
(toward the front of the chassis).
2.3 Press back on the SIMM to seat it into position. The socket clips automatically engage the SIMM
as you move it into position.
3 Remove the existing module.

3.1 Locate the module you want to replace and remove the screws from the standoffs. Set the screws
aside, as you will need them later in this procedure.
3.2 Gently remove the module from the connector pins by pulling the connector up and off.
(Continued)
O CT OB ER 28 , 2 01 3 2-11
4 Insert the new module.

4.1 Coming from the back of the chassis, insert the front of the module through the front panel of
the chassis.
5 Install the screws you removed in step 3.1 on the standoffs to secure the module.
IMPORTANT
To ensure that the module is seated properly, you must tighten the screws to a torque of
2-12 O C T OBE R 2 8, 20 1 3
REMOVING AN I/O MODULE

To remove an optional I/O module from the S2500 chassis, follow Procedure 2-3.
PROCEDURE 2-3 REMOVING AN OPTIONAL I/O MODULE
the chassis.
WARNING
in Figure 2-8.
Remove screws
(Continued)
O CT OB ER 28 , 2 01 3 2-13
PROCEDURE 2-3 REMOVING AN OPTIONAL I/O MODULE (CONTINUED)
2 If you are removing the conventional-to-IP interface kit, locate the DSP SIMM (installed in the
rearmost DSP SIMM slot) and gently remove it.
3 Locate the module you want to remove and remove the screws from the standoffs.
4 Gently remove the module from the connector pins by pulling the connector up and off.
5 Replace the screws you removed in step 3 onto the standoffs.
(Continued)
2-14 O C T OBE R 2 8, 20 1 3
PROCEDURE 2-3 REMOVING AN OPTIONAL I/O MODULE (CONTINUED)
6 Install a blank filler panel to cover the hole in the S2500 front panel that was previously filled by the
module you just removed. Insert the blank filler panel from the front of the unit, with the tabs aligned
to the edges of the opening.
CAUTION
Use caution when installing a blank filler panel; the edges of the panel are sharp.
part number6483857Y01 (I/O (Telco) module slot filler panel)

part number 6483843Y01 (analog module slot filler panel)
Figure 2-10 shows the S2500 with blank filler panels installed in both I/O slots and the analog slot.
FIGURE 2-10 S2500 BLANK FILLER PANELS
Blank filler panels

(part number 6483857Y01)
installed on I/O module slots
Blank filler panel
(part number 6483843Y01)
installed on analog module slot
O CT OB ER 28 , 2 01 3 2-15
INSTALLING AN ENCRYPTION MODULE

To install an optional encryption module in the S2500 chassis, follow Procedure 2-4.
IMPORTANT
The S2500 encryption module requires an MNR S2500 base unit module
number ST2500B with part number CLN1713E or higher. The base unit
model number and part number are listed on the rear of the router. If you
install the encryption module in a router at a previous hardware revision
level, it will not function. In addition, if you are running a version of
software lower than 15.0 on the S2500 router, you must upgrade to at least
version 15.0 BEFORE installing the encryption module.
PROCEDURE 2-4 INSTALLING AN OPTIONAL ENCRYPTION MODULE
the chassis.
WARNING
in Figure 2-12.
Remove screws
(Continued)
2-16 O C T OBE R 2 8, 20 1 3
PROCEDURE 2-4 INSTALLING AN OPTIONAL ENCRYPTION MODULE (CONTINUED)
(Continued)
O CT OB ER 28 , 2 01 3 2-17
2 Using Figure 2-14 as a guide, locate the encryption module connector and standoff locations on the
S2500 motherboard.
FIGURE 2-14 ENCRYPTION MODULE CONNECTOR AND STANDOFF LOCATIONS
Match to standoffs
on motherboard
Standoff locations
Connector
Match connector on
underside of module to
connector on motherboard
3 Remove the screws from the standoff locations and discard.
4 Using a torque screwdriver, install the standoffs shipped with the encryption module in the standoff
locations.
IMPORTANT
To ensure that the standoffs are seated properly, you must tighten them to a torque of
5 Position the encryption module.

6 Using a torque screwdriver, secure the encryption module with the screws provided with the module.
IMPORTANT
To ensure that the module is seated properly, you must tighten the screw to a torque of
(Continued)
2-18 O C T OBE R 2 8, 20 1 3
8 Verify the installation.

8.1 From the EOS command line interface, issue the SysInfo command.
8.2 In the SysInfo display, locate the Encryption Card Information line.
If the Encryption Card Information line lists the name of the encryption card (for example
MPC184), the encryption module has been successfully installed.
If the Encryption Card Information line lists Unavailable, the router is not recognizing
the encryption module. Make sure that you have installed EOS software version 15.0 or higher (XS
package) on the router, and that the base unit is at the proper hardware revision level (see
Encryption Requirements on page 1-14 for details.
O CT OB ER 28 , 2 01 3 2-19
REPLACING AN ENCRYPTION MODULE

To replace an optional encryption module in the S2500 chassis, follow Procedure 2-4.
PROCEDURE 2-5 REPLACING AN OPTIONAL ENCRYPTION MODULE
the chassis.
WARNING
in Figure 2-16.
Remove screws
(Continued)
2-20 O C T OBE R 2 8, 20 1 3
PROCEDURE 2-5 REPLACING AN OPTIONAL ENCRYPTION MODULE (CONTINUED)
(Continued)
O CT OB ER 28 , 2 01 3 2-21
2 Using Figure 2-18 as a guide, locate the encryption module and the screws securing the encryption
module to the S2500 motherboard.
FIGURE 2-18 LOCATING THE S2500 ENCRYPTION MODULE

3 Remove the screws from the standoffs.
4 Gently remove the encryption module from the connector pins by pulling the connector up and off.
5 Position the new encryption module.

6 Using a torque screwdriver, secure the encryption module with the screws provided with the module.
IMPORTANT
To ensure that the module is seated properly, you must tighten the screw to a torque of
(Continued)
2-22 O C T OBE R 2 8, 20 1 3
8 Verify the installation.

8.1 From the EOS command line interface, issue the SysInfo command.
8.2 In the SysInfo display, locate the Encryption Card Information line.
If the Encryption Card Information line lists the name of the encryption card (for example
MPC184), the encryption module has been successfully installed.
If the Encryption Card Information line lists Unavailable, the router is not recognizing
the encryption module. Make sure that you have installed EOS software version 15.0 or higher (XS
package) on the router, and that the base unit is at the proper hardware revision level (see
Encryption Requirements on page 1-14 for details.
O CT OB ER 28 , 2 01 3 2-23
MOUNTING THE S2500 CHAPTER 2: INSTALLING THE S2500 HARDWARE
MOUNTING THE S2500

...................................
..
Each S2500 ships with a mounting kit containing the hardware shown in Figure 2-20.
You can mount the router on a tabletop, stack several routers with brackets, or mount
the router in a rack.
FIGURE 2-20 MOUNTING KIT CONTENTS
Two brackets
Four adhesive-backed
rubber feet
Four 8-32 Phillips

flathead screws for use
when stacking routers
INSTALLING ON A TABLETOP
To install the S2500 on a tabletop, attach the rubber feet as shown in Figure 2-21.
FIGURE 2-21 ATTACHING RUBBER FEET FOR TABLETOP MOUNTING
Attach feet to corners

of chassis bottom
Flex plastic sheet until

feet pop loose
2-24 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE MOUNTING THE S2500
STACKING WITH BRACKETS

To stack two or more routers on a tabletop, follow Procedure 2-6.
CAUTION
Do not restrict air flow around the sides and back of the S2500.
PROCEDURE 2-6 STACKING S2500 ROUTERS WITH BRACKETS
1 Attach the rubber feet to the S2500 you will use on the bottom of the stack, as illustrated earlier in
Figure 2-21.
2 Stack the routers, using one bracket as a support for the bottom router and other brackets to lock
subsequent units together, as illustrated in Figure 2-22.
FIGURE 2-22 STACKING S2500S
Attach brackets as shown

to lock two units together
Place screws in holes as shown
Bottom bracket acts as a support
O CT OB ER 28 , 2 01 3 2-25
MOUNTING THE S2500 CHAPTER 2: INSTALLING THE S2500 HARDWARE
INSTALLING IN A RACK
To install the router in a rack, follow Procedure 2-7.
CAUTION
Do not restrict air flow around the sides and back of the S2500.
PROCEDURE 2-7 INSTALLING AN S2500 ROUTER IN A RACK
1 Secure the rack-mount brackets to each side of the chassis using two 8/32 flathead Phillips screws per
bracket, as illustrated in Figure 2-23.
FIGURE 2-23 ATTACHING THE RACK-MOUNTING SCREWS
2 Hold the chassis between the poles of the rack and attach the brackets to the rack using panhead
screws (you must provide these screws), as illustrated in Figure 2-24.
CAUTION
Using fewer than four screws (two on each side) to secure the brackets to the rack
may cause the router to fall and sustain damage not covered by the warranty.
FIGURE 2-24 ATTACHING THE S2500 TO THE RACK
3 Tighten each screw securely.
2-26 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE CABLING THE CONNECTORS
CABLING THE CONNECTORS

...................................
..
The S2500 features one 10BASE-T/100BASE-TX Ethernet interface on the base system
and may have any of the following additional interfaces depending on which optional
modules are included in the hardware configuration:
WAN/Telco (T1/E1 CSU/DSU)
FlexWAN serial
10BASE-T Ethernet
Conventional-to-IP (E&M)
This section describes how to cable each interface on the router. For a list of the
interfaces supported by the S2500, see S2500 Supported Interfaces on page 1-7.
CABLING THE POWER CONNECTOR

To cable the power connector, attach the female end of the power cable to the power
receptacle on the rear panel of the S2500 and the male end of the power cable to a wall
outlet, as illustrated in Figure 2-25.
NOTE
When the MNR S2500 is configured for use in a secure environment, it is
shipped with tamper evidence labels covering the power receptacle on the
rear of the chassis. Before you connect power to the unit, you must remove
these labels. For details, see Removing the Tamper Evidence Labels from
the Power Receptacle on page F-4.
FIGURE 2-25 CABLING THE POWER CONNECTOR
S2500
Wall outlet
Power cable
O CT OB ER 28 , 2 01 3 2-27
CABLING THE CONNECTORS CHAPTER 2: INSTALLING THE S2500 HARDWARE
CONNECTING A CHASSIS GROUND (EARTH)

Some network topologies require that a grounding (earthing) stud, separate from the
AC ground, be provided on the chassis of the networking equipment. If this type of
grounding (earthing) is required for your topology, follow Procedure 2-8 to connect the
chassis grounding (earth).
PROCEDURE 2-8 CONNECTING A CHASSIS GROUND (EARTH)
1 Using a minimum #6 AWG wire, terminate one end of a length of wire with a UL-listed ring lug.
NOTE
If the length of the grounding (earthing) wire must exceed 4 meters before it is terminated,
grounding (earthing) wire larger than #6 AWG is required. See the Motorola R56 manual
Standards and Guidelines for Communication Sites for details.
2 Using a grounding (earthing) screw, attach the lug to the rear of the chassis, as illustrated in Figure
2-26.
FIGURE 2-26 GROUNDING (EARTHING) THE S2500
Connect grounding (earthing) conductor To ground (earth)

using grounding (earthing) screw
3 Terminate the other end of the wire on a permanently-connected protective grounding (earthing)
conductor.
2-28 O C T OBE R 2 8, 20 1 3
CABLING THE ETHERNET CONNECTOR(S)

The S2500 provides one RJ-45 Ethernet connector (labeled LAN 1) on the base unit. If an
optional 10BASE-T I/O module is installed, the S2500 also provides an RJ-45 Ethernet
connector in I/O slot A (port 2) or I/O slot B (port 3).
NOTE
You can cable the Ethernet connectors using either 10BASE-T or 100BASE-TX cabling;
however, to cable the Ethernet port on the base system for a 100BASE-TX connection,
you must use a 100BASE-TX cable.
To cable the 10BASE-T/100BASE-TX Ethernet connectors on the base system or the
10BASE-T Ethernet connector on the optional 10BASE-T module, follow Procedure 2-9.
For further information about Ethernet connectors and cables, including connector
pinouts, see Ethernet Connectors and Cables, following Procedure 2-9.
PROCEDURE 2-9 CABLING THE ETHERNET (LAN) CONNECTORS
1 Connect one end of a 10BASE-T or 100BASE-TX cable to the S2500, as illustrated in Figure 2-27.
NOTE
To cable the Ethernet port on the base system for a 100BASE-TX connection, you must use a
100BASE-TX cable.
FIGURE 2-27 CABLING THE ETHERNET CONNECTOR(S)
LAN

1
10BASE-T or 100BASE-TX cables
2 Connect the other end of the cable to the Ethernet device.
O CT OB ER 28 , 2 01 3 2-29
ETHERNET CONNECTORS AND CABLES

Figure 2-28 shows the pinouts for the RJ-45 Ethernet LAN connectors. The connector
bodies connect the cable shield to chassis grounding (earth).
FIGURE 2-28 S2500 ETHERNET LAN CONNECTOR PINOUTS
TX- RX-
TX+ RX+
1 2 34 5 67 8
RJ-45 female (shielded)
10BASE-T CABLING
Table 2-2 lists supported 10BASE-T cable types and emissions classes.
NOTE
Shielding of all cable types should be terminated 360 degrees at the cable
plug.
NOTE
All UTP compliance testing was done using cables built with Stewart
Connector Co. connectors, part number 940 SP-36-08-08.
TABLE 2-2 10BASE-T CABLE TYPES AND EMISSIONS COMPLIANCE
Emissions Compliance
Cable Type FCC and VCCI Class A EN55022 Class B
UTP 100 ohm:
Category 3 yes no
Category 4 yes no
Category 5 yes no
Shielded TP 100 ohm:
Category 3 yes yes
2-30 O C T OBE R 2 8, 20 1 3
TABLE 2-2 10BASE-T CABLE TYPES AND EMISSIONS COMPLIANCE
Cable Type FCC and VCCI Class A EN55022 Class B
Category 4 yes yes
Category 5 yes yes
CABLING STANDARDS
You should install 10BASE-T cabling in accordance with the following standards:
EIA/TIA-568 Commercial building telecommunications wiring standard
TSB-36 Additional cable specifications for unshielded twisted pair cables
IBM cabling guidelines
100BASE-TX CABLING
Table 2-3 lists supported 100BASE-TX cable types and emissions classes.
NOTE
Shielding of all cable types should be terminated 360 degrees at the cable
plug.
TABLE 2-3 100BASE-TX CABLE TYPES AND EMISSIONS COMPLIANCE
FCC Class A EN55022 Class B

Cable Type Connectors
VCCI Class A VDE Class B
Category 5 UTP Category 5 RJ-45 yes no

(including jacks)
Category 5 shielded Category 5 RJ-45 yes yes

UTP (including jacks)
The three types of Fast Ethernet interfaces are:

TX Runs over Category 5 UTP and Category 5 shielded UTP.
FX Runs over fiber. FX does not connect to the S2500, but you can use FX in
your network between appropriate devices.
T4 Runs over Category 3 or better UTP or shielded UTP. T4 does not connect to
the S2500, but you can use T4 in your network between appropriate devices.
Follow Procedure 2-10 in the next section to design a valid Fast Ethernet network.
O CT OB ER 28 , 2 01 3 2-31
CREATING A VALID FAST ETHERNET NETWORK

A Fast Ethernet network consists of collision domain diameters formed by cabling and/
or repeaters between two DTE devices. A DTE device is a router or end station that
contains a media access controller (MAC). Repeaters usually do not contain MACs.
To create a valid collision domain diameter, you must adhere to the following
maximum cable span lengths, along with the collision domain diameter guidelines
listed in Table 2-4:
UTP (running TX or T4) Maximum cable span length is 100 meters.
Fiber (running FX) Maximum cable span length is 412 meters.
Figure 2-29 shows examples of collision domain diameters.
FIGURE 2-29 COLLISION DOMAIN DIAMETER EXAMPLES
Collision domain
DTE device diameter 3
DTE device
S2500
Fast Eth
ernet R
epeate
r
Collision domain
diameter 1
End Sta
tions
Fast Eth
ernet R
epeate
r DTE
Collision domain device
diameter 2
DTE device
S2500
2-32 O C T OBE R 2 8, 20 1 3
To determine a valid collision domain diameter, follow Procedure 2-10.
PROCEDURE 2-10 DETERMINING A VALID FAST ETHERNET COLLISION DOMAIN DIAMETER
1 Determine which interfaces will be used: TX, FX, or T4.
2 Add up the combined length of all cabling to be used.
3 Determine which class of repeaters, if any, are used in the collision domain
diameter.
4 Determine the maximum cable length by referring to Table 2-4, which

provides cabling and repeater guidelines for three scenarios shown in
Figure 2-30, Figure 2-31, and Figure 2-32.
For expanded guidelines, refer to the IEEE Standard 802.3.
FIGURE 2-30 COLLISION DOMAIN DIAMETER WITH NO REPEATER

F
DTE device
S2500
DTE device
S2500
O CT OB ER 28 , 2 01 3 2-33
FIGURE 2-31 COLLISION DOMAIN DIAMETER WITH ONE REPEATER
DTE
device
Fast Eth
ernet re
peater
DTE device
S2500
FIGURE 2-32 COLLISION DOMAIN DIAMETER WITH TWO REPEATERS

Fast Eth
ernet re
peater
DTE
device
Fast Eth
ernet re
peater
DTE device
S2500
2-34 O C T OBE R 2 8, 20 1 3
TABLE 2-4 MAXIMUM CABLE LENGTH IN EXAMPLE COLLISION DOMAIN DIAMETERS
Maximum Combined Cable Length, by Interface
FX
Scenario TX and/or T4 FX & TX FX & T4
Only
No Repeaters 100 m 412 m not applicable not applicable
(see Figure
2-30)
One Class 1 200 m 100 m max. 272 m 260.8 m 231 m
repeater1 on each side of the 100 m max. TX 100 m max. T4
(see Figure repeater
2-31) Remaining length of FX Remaining length of FX
One Class 2 200 m 100 m max. 320 m 308.8 m 304 m3

repeater2 on each side of the 100 m max. TX 100 m max. T4
(see Figure repeater
2-31) Remaining length of FX Remaining length of FX
Two Class 2 205 m 100 m max. 228 m 216.2 m 263.3 m3

repeaters per cable span 105 m max. total TX, 100 105 m max. total T4, 100 m
(see Figure m max. per TX cable span max. per T4 cable span
2-32)
Remaining length of FX Remaining length of FX
1
A high-delay repeater as specified in IEEE 802.3 standards. A Class 1 repeater usually connects dissimilar media,
for instance, UTP to fiber.
2
A low-delay repeater as specified in IEEE 802.3 standards. A Class 2 repeater usually connects similar media, for
instance, UTP to UTP.
3
This scenario is unlikely, because Class 2 repeaters do not usually connect FX to T4.
O CT OB ER 28 , 2 01 3 2-35
CABLING THE FLEXWAN SERIAL CONNECTOR(S)

The S2500 supports up to two FlexWAN serial connectors (one per optional I/O
module). You can connect the FlexWAN serial connectors labeled 2 and/or 3 to
DTE and DCE devices with the following interfaces:
RS-232
V.35
X.21
RS-449
EIA-530 (DCE only)
NOTE
FlexWAN serial connectors are supported only if the optional FlexWAN
module is installed (one connector per I/O module).
You can order the FlexWAN cable that is appropriate for your serial device from
Motorola. See FlexWAN Serial Connectors and Serial Cables on page 2-39 for more
information. To connect the FlexWAN serial cables, follow Procedure 2-11.
2-36 O C T OBE R 2 8, 20 1 3
PROCEDURE 2-11 CABLING THE FLEXWAN SERIAL CONNECTORS
1 Attach the 60-pin FlexWAN connector to the S2500, as shown in Figure 2-33.
A DCE must always connect to a DTE, and vice versa. An MNR S2500 is a DTE but can provide the
necessary clocking signals to act as a DCE.
NOTE
The interface of the device to which you connect the MNR S2500 FlexWAN connector must
be the opposite of the cable attached to the MNR S2500.
If you attach a DCE cable to the MNR S2500, the device on the other end of the connection must be a
DTE.
If you attach a DTE cable to the MNR S2500, the device on the other end of the connection must be a
DCE or a device acting as a DCE.
FIGURE 2-33 CABLING A FLEXWAN SERIAL CONNECTOR
Link
Active
Fault
FlexWAN
3
FlexWAN cable
Connect to RS-232, RS-449,
V.35, or X.21 DTE or DCE,
or RS-530 DCE
(Continued)
O CT OB ER 28 , 2 01 3 2-37
PROCEDURE 2-11 CABLING THE FLEXWAN SERIAL CONNECTORS (CONTINUED)
2 Connect the other end of the serial cable to the RS-232, V.35, X.21, RS-449, or EIA-530 connector on the
DTE or DCE device.
To connect the S2500 to another DTE, such as another MNR S2500 router or an MNR S6000 router or
GGM 8000 gateway, attach a FlexWAN DCE cable to the MNR S2500 and a FlexWAN DTE cable to
the other DTE, then attach the DCE and DTE connectors on the ends of the cables to each other, as
FIGURE 2-34 CONNECTING THE S2500 TO A DTE USING A DCE CABLE AND A DTE CABLE

! " #$#%%& '

To connect the S2500 to a DCE, such as a modem, attach a FlexWAN DTE cable to the S2500, then
attach the DTE connector on the end of the cable to the modem, as illustrated in Figure 2-35.
FIGURE 2-35 CONNECTING THE S2500 TO A DCE USING A DTE CABLE

2-38 O C T OBE R 2 8, 20 1 3
FLEXWAN SERIAL CONNECTORS AND SERIAL CABLES

You can purchase FlexWAN cables from Motorola. Table 2-5 lists each FlexWAN cable
and part number. The subsections following the figure provide cable pinouts.
TABLE 2-5 FLEXWAN CABLES
Cable Part
Cable Type Pinouts
Length Number
10 ft. RS-232 DTE DKN6117A page 2-40
10 ft. RS-232 DCE DKN6118A page 2-41
10 ft. V.35 DTE DKN6119A page 2-42
10 ft. V.35 DCE DKN6120A page 2-43
10 ft. X.21 DTE DKN6121A page 2-44
10 ft. X.21 DCE DKN6122A page 2-45
10 ft. RS-449 DTE DKN6123A page 2-46
10 ft. RS-449 DCE DKN6124A page 2-47
10 ft. EIA-530 DTE DKN6125A page 2-48
O CT OB ER 28 , 2 01 3 2-39
FLEXWAN RS-232 DTE CABLE PINOUTS

The RS-232 DTE cable connects the S2500 to an RS-232 DCE device. Figure 2-36
illustrates the connectors on either end of the RS-232 DTE cable. Table 2-6 lists the cable
pinouts.
FIGURE 2-36 FLEXWAN AND RS-232 DTE CONNECTORS
To S2500
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 To DCE
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
1 2 3 4 5 6 7 8 9 10 11 12 13
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
14 15 16 17 18 19 20 21 22 23 24 25
60-pin Flex-WAN male connector 25-pin male connector
.
TABLE 2-6 RS-232 DTE CABLE PINOUTS
FlexWAN Connector RS-232 DTE Connector

Signal Pin Direction Pin Signal Twisted Pair1
DCD/LL 33 8 DCD 1
DSR/DTR 34 6 DSR 2
CTS/RTS 35 5 CTS 3
RxD/TxD 36 3 RxD 4
TxC/Nil 37 15 TxC 5
RxC/TxCE 38 17 RxC 6
TxCE/TxC 39 24 TxCE 7
TxD/RxD 41 2 TxD 8
RTS/CTS 42 4 RTS 9
DTR/DSR 43 20 DTR 10
LL/DCD 44 18 LTST 11
Circuit Ground 45 - 7 Circuit Ground 12
Shield Ground 46 Cable Shield 1 Shield Ground -
Shorting Group 1 50, 51, - - - -
52
1.Unused twisted wires of a twisted pair should be connected to Shield Ground. In
this cable this is one wire of each of the twisted pairs 1 to 12.
2-40 O C T OBE R 2 8, 20 1 3
FLEXWAN RS-232 DCE CABLE PINOUTS

The RS-232 DCE cable connects the S2500 to an RS-232 DTE device. Figure 2-37
illustrates the connectors on either end of the RS-232 DCE cable. Table 2-7 lists the cable
pinouts.
FIGURE 2-37 FLEXWAN AND RS-232 DCE CONNECTORS
To S2500
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 To DTE
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
1 2 3 4 5 6 7 8 9 10 11 12 13
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
14 15 16 17 18 19 20 21 22 23 24 25
60-pin FlexWAN male connector 25-pin female connector
TABLE 2-7 RS-232 DCE CABLE PINOUTS
FlexWAN Connector RS-232 DCE Connector

Twisted
Signal Pin Direction Pin Signal
Pair1
DCD/LL 33 18 LTST 1
DSR/DTR 34 20 DTR 2
CTS/RTS 35 4 RTS 3
RxD/TxD 36 2 TxD 4
RxC/TxCE 38 24 TxCE 5
TxCE/TxC 39 15 TxC 6
Nil/RxC 40 17 RxC 7
TxD/RxD 41 3 RxD 8
RTS/CTS 42 5 CTS 9
DTR/DSR 43 6 DSR 10
LL/DCD 44 8 DCD 11
Circuit Ground 45 - 7 Circuit Ground 12
Shorting Group 1 50, 51 - - - -
1.Unused twisted wires of a twisted pair should be connected to Shield Ground.
In this cable this is one wire of each of the twisted pairs 1 to 12.
O CT OB ER 28 , 2 01 3 2-41
FLEXWAN V.35 DTE CABLE PINOUTS

The V.35 DTE cable connects the S2500 to a V.35 DCE device. Figure 2-38 illustrates the
connectors on either end of the V.35 DTE cable. Table 2-8 lists the cable pinouts.
FIGURE 2-38 FLEXWAN AND V.35 DTE CONNECTORS

NN
JJ
DD
B
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
LL
FF
BB
D
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
MM
HH
CC
A
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
KK
EE
C

TABLE 2-8 V.35 DTE CABLE PINOUTS
FlexWAN Connector V.35 DTE Connector

SD/RD- 17 Q SD- 1
SD/RD+ 18 P SD-
SCTE/SCT- 19 W SCTE- 2
SCTE/SCT+ 20 U SCTE+
TxC/RxC- 23 AA SCT- 3
TxC/RxC+ 24 Y SCT+
RxC/TxCE- 25 X SCR- 4
RxC/TxCE+ 26 V SCR+
RxD/TxD- 27 T RD- 5
RxD/TxD+ 28 R RD+
DCD/LL 33 F RLSD 6
DSR/DTR 34 E DSR 7
CTS/RTS 35 D CTS 8
RTS/CTS 42 C RTS 9
DTR/DSR 43 H DTR 10
LL/DCD 44 K LT 11
Circuit Ground 45 - B Ground 12
Shield Ground 46 Cable Shield A Shield Ground -
Shorting Group 2 50, 51, 52 - - - -
55, 56
2-42 O C T OBE R 2 8, 20 1 3
FLEXWAN V.35 DCE CABLE PINOUTS

The V.35 DCE cable connects the S2500 to a V.35 DTE device. Figure 2-39 illustrates the
connectors on either end of the V.35 DCE cable. Table 2-9 lists the cable pinouts.
FIGURE 2-39 FLEXWAN AND V.35 DCE CONNECTORS

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

AA
H
W
C
S
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
A
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
D
60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
B

TABLE 2-9 V.35 DCE CABLE PINOUTS
FlexWAN Connector V.35 DCE Connector

SD/RD- 17 T RD- 1
SD/RD+ 18 R RS-
SCTE/SCT- 19 AA SCT- 2
SCTE/SCT+ 20 Y SCT+
Nil/SCR- 21 X SCR- 3
Nil/SCR+ 22 V SCR+
RxC/TxCE- 25 W SCTE- 4
RxC/TxCE+ 26 U SCTE+
RxD/TxD- 27 S SD- 5
RxD/TxD+ 28 P SD+
DCD/LL 33 K LT 6
DSR/DTR 34 H DTR 7
CTS/RTS 35 D RTS 8
RTS/CTS 42 C CTS 9
DTR/DSR 43 E DSR 10
LL/DCD 44 F RLSD 11
Circuit Ground 45 - B Ground 12
Shield Ground 46 Cable Shield A Shield Ground -
55, 56
O CT OB ER 28 , 2 01 3 2-43
FLEXWAN X.21 DTE CABLE PINOUTS

The X.21 DTE cable connects the S2500 to an X.21 DCE device. Figure 2-40 illustrates
the connectors on either end of the X.21 DTE cable. Table 2-10 lists the cable pinouts.
FIGURE 2-40 FLEXWAN AND X.21 DTE CONNECTORS
To S2500
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
To DCE
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 1 2 3 4 5 6 7 8
60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
9 10 11 12 13 14 15
TABLE 2-10 X.21 DTE CABLE PINOUTS
FlexWAN Connector X.21 DTE Connector

CTS/RTS+ 1 5 Indicate+ 1
CTS/RTS- 2 12 Indicate-
RTS/CTS+ 9 3 Control+ 2
RTS/CTS- 10 10 Control-
TxD/RxD+ 11 2 Transmit+ 3
TxD/RxD- 12 9 Transmit-
Circuit Ground 15 - 8 Control GND 4
RxC/TxCE- 25 13 Timing- 5
RxC/TxCE+ 26 6 Timing+
RxD/TxD- 27 11 Receive- 6
RxD/TxD+ 28 4 Receive+
this cable this is one wire of twisted pair 4.
2-44 O C T OBE R 2 8, 20 1 3
FLEXWAN X.21 DCE CABLE PINOUTS

The X.21 DCE cable connects the S2500 to an X.21 DTE device. Figure 2-41 illustrates
the connectors on either end of the X.21 DCE cable. Table 2-11 lists the cable pinouts.
FIGURE 2-41 FLEXWAN AND X.21 DCE CONNECTORS
To S2500
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
To DTE
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 1 2 3 4 5 6 7 8
60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
9 10 11 12 13 14 15
60-pin Flex-WAN male connector 15-pin female connector
TABLE 2-11 X.21 DCE CABLE PINOUTS
FlexWAN Connector X.21 DCE Connector

CTS/RTS+ 1 3 Control+ 1
CTS/RTS- 2 10 Control-
RTS/CTS+ 9 5 Indicate+ 2
RTS/CTS- 10 12 Indicate-
TxD/RxD+ 11 4 Receive+ 3
TxD/RxD- 12 11 Receive-
Circuit Ground 15 - 8 Control GND 4
TxC/RxC- 23 13 Timing- 5
TxC/RxC+ 24 6 Timing+
RxD/TxD- 27 9 Transmit- 6
RxD/TxD+ 28 2 Transmit+
this cable this is one wire of twisted pair 4.
O CT OB ER 28 , 2 01 3 2-45
FLEXWAN RS-449 DTE CABLE PINOUTS

The RS-449 DTE cable connects the S2500 to an RS-449 DCE device. Figure 2-42
illustrates the connectors on either end of the RS-449 DTE cable. Table 2-12 lists the
cable pinouts.
FIGURE 2-42 FLEXWAN AND RS-449 DTE CONNECTORS

To S2500
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 To DCE
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

TABLE 2-12 RS-449 DTE CABLE PINOUTS
FlexWAN Connector RS-449 DTE Connector

Signal Pin Direction Pin Signal Twisted Pair
CTS/RTS+ 1 9 CS+ 1
CTS/RTS- 2 27 CS-
DSR/DTR+ 3 11 DM+ 2
DSR/DTR- 4 29 DM-
DCD/DCD+ 5 13 RR+ 3
DCD/DCD- 6 31 RR-
DTR/DSR+ 7 12 TR+ 4
DTR/DSR- 8 30 TR-
RTS/CTS+ 9 7 RS+ 5
RTS/CTS- 10 25 RS-
TxD/RxD+ 11 4 SD+ 6
TxD/RxD- 12 22 SD-
TxCE/TxC+ 13 17 TT+ 7
TxCE/TxC- 14 35 TT-
Circuit Ground 15 - 19 SGRC 8
Circuit Ground 16 - 20 SGRC
TxC/RxC- 23 23 ST- 9
TxC/RxC+ 24 5 ST+
RxC/TxCE- 25 26 RT- 10
RxC/TxCE+ 26 8 RT+
RxD/TxD- 27 24 RD- 11
RxD/TxD+ 28 6 RD+
LL/DCD 44 10 LLSC 12
Circuit Ground 45 37 Circuit Ground
Shorting Group 2 51, 52 -
2-46 O C T OBE R 2 8, 20 1 3
FLEXWAN RS-449 DCE CABLE PINOUTS

The RS-449 DCE cable connects the S2500 to an RS-449 DTE device. Figure 2-43
illustrates the connectors on either end of the RS-449 DCE cable. Table 2-13 lists the
cable pinouts.
FIGURE 2-43 FLEXWAN AND RS-449 DCE CONNECTORS
To S2500
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 To DTE
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45
60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37
60-pin Flex-WAN male connector 37-pin female connector
TABLE 2-13 RS-449 DCE CABLE PINOUTS
FlexWAN Connector RS-449 DCE Connector

Signal Pin Direction Pin Signal Twisted Pair
CTS/RTS+ 1 7 RS+ 1
CTS/RTS- 2 25 RS-
DSR/DTR+ 3 12 TR+ 2
DSR/DTR- 4 30 TR-
DCD/DCD+ 5 13 RR+ 3
DCD/DCD- 6 31 RR-
DTR/DSR+ 7 11 DM+ 4
DTR/DSR- 8 29 DM-
RTS/CTS+ 9 9 CS+ 5
RTS/CTS- 10 27 CS-
TxD/RxD+ 11 6 RD+ 6
TxD/RxD- 12 24 RD-
TxCE/TxC+ 13 5 ST+ 7
TxCE/TxC- 14 23 ST-
Circuit Ground 15 - 19 SGRC 8
Circuit Ground 16 - 20 SGRC
TxC/RxC- 23 26 RT- 9
TxC/RxC+ 24 8 RT+
RxC/TxCE- 25 35 TT- 10
RxC/TxCE+ 26 17 TT+
RxD/TxD- 27 22 SD- 11
RxD/TxD+ 28 4 SD+
Nil/LL 29 10 LLSC 12
Circuit Ground 30 - 37 Ground
O CT OB ER 28 , 2 01 3 2-47
FLEXWAN EIA-530 DTE CABLE PINOUTS

The EIA-530 DTE cable connects the S2500 to an EIA-530 DCE device. Figure 2-44
illustrates the connectors on either end of the EIA-530 DTE cable. Table 2-14 lists the
cable pinouts.
FIGURE 2-44 FLEXWAN AND EIA-530 DTE CONNECTORS
To S2500
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 To DCE
31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 1 2 3 4 5 6 7 8 9 10 11 12 13
60 59 58 57 56 55 54 53 52 51 50 49 48 47 46
14 15 16 17 18 19 20 21 22 23 24 25
TABLE 2-14 EIA-530 DTE CABLE PINOUTS
FlexWAN Connector EIA-530 DTE Connector

Signal Pin Direction Pin Signal
CTS/RTS+ 1 5 CTS+
CTS/RTS- 2 13 CTS-
DSR/DTR+ 3 6 DSR+
DSR/DTR- 4 22 DSR-
DCD/DCD+ 5 8 DCD+
DCD/DCD- 5 10 DCD-
DTR/DSR+ 7 20 DTR+
DTR/DSR- 8 23 DTR-
RTS/CTS+ 9 4 RTS+
RTS/CTS- 10 19 RTS-
TxD/RxD+ 11 2 TxD+
TxD/RxD- 12 14 TxD-
TxCE/TxC+ 13 24 TxCE+
TxCE/TxC- 14 11 TxCE-
TxC/RxC- 23 12 TxC-
TxC/RxC+ 24 15 TxC+
RxC/TxCE- 25 9 RxC-
RxC/TxCE+ 26 17 RxC+
RxD/TxD- 27 16 RxD-
RxD/TxD+ 28 3 RxD+
LL/DCD 44 18 LL
Circuit Ground 45 - 7 Circuit Ground
Shield Ground 46 Cable Shield 1 Shield Ground
Shorting Group 1 47, 48, 49 - - -
2-48 O C T OBE R 2 8, 20 1 3
CABLING THE WAN/TELCO (T1/E1 CSU/DSU)

CONNECTOR(S)
The S2500 supports up to two WAN/Telco (T1/E1 CSU/DSU) connectors (one per
optional I/O module). You cable the WAN/Telco (T1/E1 CSU/DSU) connectors
labeled 2 and/or 3 using RJ-48C cabling. Figure 2-45 shows the pinouts for the WAN/
Telco (T1/E1 CSU/DSU) connectors. The connector bodies connect the cable shield to
chassis ground (earth).
NOTE
WAN/Telco (T1/E1 CSU/DSU) connectors are supported only if the optional
T1/E1 CSU/DSU module is installed (one connector per I/O module).
FIGURE 2-45 S2500 WAN/TELCO (T1/E1 CSU/DSU) CONNECTOR PINOUTS

RX+ TX+
RX- TX-
1 2 34 5 67 8
RJ-48C female (shielded)
To cable the WAN/Telco (T1/E1 CSU/DSU) connectors, follow Procedure 2-12.
PROCEDURE 2-12 CABLING A WAN/TELCO (T1/E1 CSU/DSU) CONNECTOR
1 Attach one end of an RJ-45 cable to the S2500, as shown in Figure 2-46.
FIGURE 2-46 CABLING A WAN/TELCO (T1/E1 CSU/DSU) CONNECTOR
T1/E1 Link
CSU/
DSU Active
Fault
RJ-45 cable
2 Attach the other end of the RJ-45 cable to a CSU or DSU device.
O CT OB ER 28 , 2 01 3 2-49
CABLING THE V.24 CONNECTOR(S)

The S2500 V.24 module supports two V.24 serial ports. The ports on the V.24 module are
labeled Port 1 and Port 2. However the MNR S2500 software reserves ports 2 or 3 A
and B for digital conventional V.24 ports.
If the V.24 module is installed in port 2, the software uses port numbers 2A and
2B.
3B.
NOTE
How you cable the V.24 ports depends on whether you are Connecting the S2500 V.24
Interface Directly to a Base Station, Connecting the S2500 V.24 Interface to a Modem,
or Connecting the S2500 V.24 Interface to a Subrate Data (SRU) Card. In addition, you
must ensure that the clock source is set appropriately. For details, see Setting the
Clock Source in the Provisioning Manager on page 2-56.
Figure 2-47 illustrates the pin locations on the MNR 2500 V.24 connector. Table 2-15 lists
the pin functions.
FIGURE 2-47 MNR S2500 V.24 CONNECTOR (RJ-45)

1 2 34 5 67 8
RJ-45
2-50 O C T OBE R 2 8, 20 1 3
NOTE
The pin functions described in Table 2-15 apply to internal clock
applications (co-located links with direct connections to a base station).
When configuring the MNR 2500 for an external clock application (external
links connected via a modem or SRU), an external clock signal (TCLK-EXT)
must be brought in on pin 2 of the S2500 V.24 port interface. For details, see
Connecting the S2500 V.24 Interface to a Modem on page 2-53 or
Connecting the S2500 V.24 Interface to a Subrate Data (SRU) Card on
page 2-55.
TABLE 2-15 MNR S2500 V.24 CONNECTOR PIN FUNCTIONS
Pin # Name
1 RCLK Receive Clock (in)
2 CD Carrier Detect (in)
3 TCLK Transmit Clock (out)
4 GND (Signal Ground)
5 RxD Receive Data (in)
6 TxD Transmit Data (out)
7 CTS Clear to Send (in)
8 RTS Request to Send (out)
O CT OB ER 28 , 2 01 3 2-51
CONNECTING THE S2500 V.24 INTERFACE

DIRECTLY TO A BASE STATION
To connect the S2500 V.24 module directly to a base station, follow Procedure 2-13.
PROCEDURE 2-13 HOW TO CONNECT THE S2500 V.24 MODULE TO A BASE STATION
1 Attach one end of a port-to-port (V.24 null modem) cable with RJ-45 plugs at both ends, wired either
as illustrated in Figure 2-48 or as illustrated in Figure 2-49, to the S2500 V.24 port.
NOTE
The interface interconnection illustrated in Figure 2-48 can also be achieved by using the
pre-built cable designed for use with the V.24 module (part number DKN6143A-A).
FIGURE 2-48 SIGNAL DIAGRAM: MNR S2500 V.24 INTERFACE TO BASE STATION
%& '"

! "#$ ! "#$

FIGURE 2-49 ALTERNATIVE SIGNAL DIAGRAM: S2500 V.24 INTERFACE TO BASE STATION
%& '"

! "#$ ! "#$

2 Attach the other end of the V.24 null modem cable to the base station port.
2-52 O C T OBE R 2 8, 20 1 3
In addition to interconnecting the S2500 and the base station as illustrated in

Figure 2-48 or Figure 2-49, follow these best practice recommendations to ensure that
the port clock is configured appropriately:
CAUTION
Incorrect settings will cause data bit errors that damage the link
packets and result in packet loss with the data transfers to and from
the S2500.
Configure the V.24 port interface on the S2500 to synchronize the transmission of
its serial data (TXD) using an internally-generated reference clock.
Configure the V.24 port interface on the base station to synchronize the
transmission of its serial data (TXD) using an internally-generated reference
clock.
Connect the transmit clock output signal (TCLK) from the V.24 port of one device
to the receive clock input signal (RCLK) on the V.24 port of the other device.
Both of the V.24 ports will use the transmit clock signal supplied by the other device to
synchronize the reception of serial data.
CONNECTING THE S2500 V.24 INTERFACE TO A MODEM

To connect the S2500 V.24 module to a modem, follow Procedure 2-14.
PROCEDURE 2-14 HOW TO CONNECT THE S2500 V.24 MODULE TO A MODEM
1 Attach an RJ45-to-25-pin D cable adapter (CLN8488A) to the modem port. Figure 2-50 shows the
pin locations for the cable adapter.
FIGURE 2-50 RJ45-TO-25 D CABLE ADAPTER PIN LOCATIONS
(Continued)
O CT OB ER 28 , 2 01 3 2-53
PROCEDURE 2-14 HOW TO CONNECT THE S2500 V.24 MODULE TO A MODEM
2 Attach one end of an RJ45-toRJ45 straight-through cable, wired as illustrated in Figure 2-51, to the
S2500 V.24 port.
FIGURE 2-51 SIGNAL DIAGRAM: MNR S2500 V.24 INTERFACE TO MODEM
&' (
!"#$ )* +
!#% &' !"#$

!#*,--!&.,- #/%
0 & )*

./ 1 1 &' ( 2'#) !
3 Attach the other end of the RJ-45 cable to the cable adapter on the modem port.
In addition to interconnecting the S2500 and the modem as illustrated in

Figure 2-51, follow these best practice recommendations to ensure that the port clock is
configured appropriately:
CAUTION
the S2500.
Configure the DB-25 interface connection on the modem to supply both the
transmit and the receive clock signals to the V.24 port interface on the S2500.
Configure the V.24 port interface on the S2500 to use the externally-supplied clock
signal from the modem to synchronize the transmission of serial data.
Connect the TCLK-EXT input signal on the V.24 port interface on the S2500 to the
TCLK output signal on the DB-25 interface connection on the modem.
2-54 O C T OBE R 2 8, 20 1 3
CONNECTING THE S2500 V.24 INTERFACE

TO A SUBRATE DATA (SRU) CARD
To connect the S2500 V.24 module to an SRU card, follow Procedure 2-15.
PROCEDURE 2-15 HOW TO CONNECT THE MNR S2500 TO AN SRU CARD
1 Attach the appropriate end of an 8-conductor cable with standard RJ45 plugs at both ends, wired as
illustrated in Figure 2-52, to the S2500 V.24 port.
CAUTION
The two ends of the cable are not interchangeable and should be marked
accordingly.
FIGURE 2-52 SIGNAL DIAGRAM: S2500 V.24 INTERFACE TO SRU
( !"#$

!"#$ $&")*+! '
!#% &' #, # &+-+

2 Attach the other end of the 8-conductor cable to the SRU card port.
In addition to interconnecting the S2500 to the SRU as illustrated in Figure 2-52, follow
these best practice recommendations to ensure that the port clock is configured
appropriately:
CAUTION
the S2500.
Configure the V.24 port interface on the SRU to supply both the transmit and the
receive clock signals to the V.24 port interface on the S2500.
Configure the V.24 port interface on the S2500 to use the externally-supplied clock
signal from the SRU to synchronize the transmission of serial data.
Connect the TCLK-EXT input signal on the V.24 port interface on the S2500 to the
TCLK output signal on the V.24 port interface on the SRU.
O CT OB ER 28 , 2 01 3 2-55
SETTING THE CLOCK SOURCE IN THE PROVISIONING MANAGER

In addition to interconnecting the devices as described in the previous sections, follow
these best practice recommendations to configure the clock mode on the MNR S2500
V.24 ports:
If you are connecting the MNR S2500 directly to a base station, the clock source
for the V.24 communication link should be set to internal (the transmit clock is
generated internally in the MNR S2500).
If you are connecting the MNR S2500 to a modem, the clock source for the V.24
communications link should be set to external (the transmit clock is generated by
an external device; in this case, the modem).
If you are connecting the MNR S2500 to a subrate data (SRU) card, the clock
source for the V.24 communications link should be set to external (the transmit
clock is generated by an external device; in this case, the SRU card).
Beginning with the ASTRO 25 7.13 system release, you configure the clock source in
the Provisioning Manager. Clock Source is one of the fields included when you
configure a digital conventional channel. For details about how to use the Provisioning
Manager to configure digital conventional channels, see the Provisioning Manager
manual, available as part of the ASTRO 25 system release documentation, and the
Provisioning Manager online help.
NOTE
For releases prior to the ASTRO 25 7.13 system release, you configure the
clock source in the User Configuration Manager (UCM). The Clock Source
parameter is on the Digital Conventional Setup tab. For details, see the
User Configuration Manager manual, available as part of the ASTRO 25
system release documentation.
IMPORTANT
A reboot is required in order for changes made in the Provisioning Manager
or UCM to be adopted permanently by the MNR S2500.
2-56 O C T OBE R 2 8, 20 1 3
CABLING THE E&M (ANALOG) CONNECTOR(S)

When configured with the optional conventional-to-IP interface kit (E&M module and
DSP SIMM), the S2500 (referred to as the CCGW) supports four 4-wire E&M (analog)
connectors. You cable the E&M analog interface ports labeled 4, 5, 6, and 7 using
8-pin RJ-1CX connectors. Figure 2-53 illustrates the pin locations on the connector.
Table 2-16 lists the connector pinouts.
NOTE
E&M analog connectors are supported only if the optional conventional-to-
IP interface kit (E&M module and DSP SIMM) is installed.
FIGURE 2-53 S2500 E&M ANALOG CONNECTOR (RJ-1CX)
1 2 34 5 67 8
RJ-1CX
TABLE 2-16 S2500 E&M ANALOG R PINOUTS
Pin # Name
1 Tip-2
2 Ring-2
3 E-Lead
4 Ring-1
5 Tip-1
6 SG (Signal Ground)
7 M-Lead
8 SB (Signal Battery)
O CT OB ER 28 , 2 01 3 2-57
CONNECTING THE MNR S2500 E&M INTERFACE TO A BASE STATION
The MNR S2500 is physically connected to an analog base station through one or more
of the four 4-wire E&M interface ports.
The MNR S2500 E&M interface is configured to operate in E&M Type II mode. In E&M
Type II mode, the two line-control functions are implemented with two current loops.
Each side of an E&M Type II connection has a relay, a voltage source, and a current
detector.
The relay/switch function in the MNR S2500 E&M interface is provided on the E
and SG signals. The E and SG signals are connected to a voltage source and an
optically-isolated current detector on the base station to form a current loop
controlled by the MNR S2500. The base station detects MNR S2500 relay closure
with its current detector.
The contacts of the base-station-controlled relay are interconnected with the M
and SB signals on the MNR S2500 to form a current loop that is controlled by the
base station. The MNR S2500 SB signal provides the low voltage source for the
current loop and the current detector (on the MNR S2500 M-lead) detects base
station relay closure.
The audio connections on the E&M port consist of one signal pair for each direction
(4-wire audio). The control signal pairs are designed to interoperate with E&M signals
meeting the TIA/EIA-464 specification. According to this specification, the voltages on
the line control signals must adhere to the following limits:
The continuous working voltages on the E&M line control signals must not
exceed 60V in magnitude (nominal working voltage is -48VDC).
Transient peaks of up to 300V are permitted (for inductive or capacitive ringing).
A level of 80V is sustained for no more than 10 milliseconds.
NOTE
The audio signals on the S2500 E&M module are designed for 600
resistively-terminated interfaces, and we recommend that the terminators
on the base station be configured appropriately.
CAUTION
The analog interface of the CCGW is designed to connect directly to
analog stations that are physically located in the same room or
building, or via a connection provided by a microwave link. If analog
lines are used to connect the CCGW to an analog station at another
location, a primary surge suppression device must be installed.
2-58 O C T OBE R 2 8, 20 1 3
Connect the signals on the MNR S2500 E&M port(s) to a QUANTAR base station as
illustrated in Figure 2-54. For the specific port number on the base station that is used
to connect the 4-wire interface cable, refer to the documentation supplied with the base
station. For detailed information about the pin functions, see MNR S2500-to-Analog
Base Station Pin Functions on page 2-61.
NOTE
While QUANTAR base stations do not specifically implement a standard
E&M interface, they do include all the components (voltage supplies, relays,
and current detectors) necessary to interoperate with the E&M interface on
the MNR S2500.
NOTE
It may be necessary to connect additional circuitry to accommodate various
unique base station applications.
NOTE
The relay/switch closure detection function provided on pins 7 and 8 and
the relay/switch function provided on pins 3 and 6 is only possible if the
equipment connected is colocated on the same premises as the MNR S2500.
NOTE
Figure 2-54 shows a 5-Volt supply output on the base station as the voltage
source for the current detector on the base station. However the CCGW
safely accepts any voltage source between +/- 60 VDC, providing that the
voltage output of the source does not cause the optically-isolated current
detector on the base station to exceed its maximum current rating.
O CT OB ER 28 , 2 01 3 2-59
FIGURE 2-54 MNR S2500 E&M PORT-TO-QUANTAR BASE STATION INTERCONNECTIONS
2-60 O C T OBE R 2 8, 20 1 3
MNR S2500-TO-ANALOG BASE STATION PIN FUNCTIONS

Table 2-17 describes the pin functions for analog base station connections to the
MNR S2500.
NOTE
The relay/switch closure detection function provided on pins 7 and 8 and
the relay/switch function provided on pins 3 and 6 is only possible if the
equipment connected is colocated on the same premises as the MNR S2500.
TABLE 2-17 PIN FUNCTIONS FOR ANALOG BASE STATION CONNECTIONS
Pin Function Description
Relay/Switch Closure Detection Pins 7 and 8 are normally used as part of a current loop that is controlled
(pins 7 and 8) by the attached equipment. Pin 8 provides a current-limited -48VDC
supply to drive the current loops, while pin 7 detects when the relay/
switch on the attached equipment is closed.
The current detector on pin 7 detects currents of 2 m or greater and is
used in circuits with average signal levels ranging between +/ 60V. The
surge protection devices (not shown in Figure 2-54) that are included in
this circuit trigger when the signal significantly exceeds 60V in
magnitude and as a result contribute to the overall signal settling time for
signals exceeding 60V.
Relay/Switch Function Pins 3 and 6 are normally used to control (open and close) a current loop
(pins 3 and 6) that is monitored by the attached equipment. The MNR S2500 uses a
solid-state relay to control the current loop. The solid-state relay on the
MNR S2500 will switch as much a 1 A. However the current through pins
3 and 6 should not average more then 0.5 A, or significantly exceed 1 A
peak; otherwise, the self-healing polymer fuses (not shown Figure 2-54)
that are included in this circuit trigger. The average voltage level must not
exceed 60V in magnitude for much longer than 10 milliseconds to avoid
damaging the transient voltage suppressors in the circuit. The solid-state
relay has a worst-case off-state leaking current of 10 when open.
Pins 3 and 6 are not protected against high voltage. If your particular
application warrants it, however, you may add your own surge
protection devices.
(Continued)
O CT OB ER 28 , 2 01 3 2-61
TABLE 2-17 PIN FUNCTIONS FOR ANALOG BASE STATION CONNECTIONS (CONTINUED)
Pin Function Description
Outbound Audio The analog audio from the MNR S2500 is carried (differentially) on pins 4
(pins 4 and 5) and 5. The source impedance of the outbound audio circuit is 600 Ohms,
and the receiving end of the line is terminated with a load impedance of
600 Ohms (to maintain specified output gain levels). The terminators on
the receiving equipment should be configured appropriately, if multiple
termination options are available.
The outbound audio circuit is designed to drive an analog tone with
average levels as high as +11dBm (+/- 3.9V peak-to-peak) into a 600 Ohms
load without clipping. Transient voltage suppressors on the secondary
side of the isolation transformer will clip signals significantly exceeding
8V (differential) and surge protection devices on the primary side of the
transformer trigger when the differential voltage significantly exceeds
25V.
Inbound Audio The analog audio into the MNR S2500 is carried (differentially) on pins 1
(pins 1 and 2) and 2. Normally the MNR S2500 is configured to provide a termination
impedance of 600 Ohms across these pins. The MNR S2500 has a software
option (referred to as the high-impedance option, the non-terminated
option or, alternatively, the 10K-Ohms loading option) to disconnect the
terminating load on a port-by-port basis. This option is used in cases
where another piece of equipment (attached to the same signal pair) is
configured to provide the 600 Ohms termination.
NOTE
The resulting termination impedance is greater than
10K-Ohms.
The inbound audio circuit is designed to receive an analog audio tone
with average levels as high as +11 dBm (+/- 3.9V peak-to-peak) without
clipping. Transient voltage suppressors on the secondary side of the
isolation transformer will clip signals significantly exceeding 8V
(differential) and surge protection devices on the primary side of the
transformer trigger when the differential voltage significantly exceeds
25V.
2-62 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE CONNECTING A PC, TERMINAL, OR MODEM
CONNECTING A PC, TERMINAL, OR MODEM

...................................
..
Connect a PC running a terminal emulation program, a terminal, or a modem to the
console port on the S2500 to configure the router software and review startup and
system operation messages.
Figure 2-55 illustrates the location of the console connector on the front of the S2500.
The console port is a 9-pin male connector.
FIGURE 2-55 S2500 CONSOLE CONNECTOR
S2500
SYSTEM
Console Run
Fwd
Status Load Power
Test /Fault
Console
connector
Table 2-18 lists the console port configuration settings.
TABLE 2-18 CONSOLE PORT CONFIGURATION SETTINGS
Characteristic Setting
Baud rate 9600
Data bits 8
Parity None
Stop bits 1
DTR Ignored
Duplex Full
Echo Off
Flow control None
O CT OB ER 28 , 2 01 3 2-63
CONNECTING A PC, TERMINAL, OR MODEM CHAPTER 2: INSTALLING THE S2500 HARDWARE
To connect a PC, terminal, or modem to the S2500, follow Procedure 2-16.
PROCEDURE 2-16 CONNECTING A PC, TERMINAL, OR MODEM
1 Obtain a cable to connect the device to the console port on the S2500.
CAUTION
To eliminate cable noise emission in excess of FCC Part 15, Subpart3 and EN55022
B, this device cable should be shielded and have connectors with metallic
backshells.
For a PC, use a 9-pin female to 9-pin female null modem-type cable. The cable pinouts are
FIGURE 2-56 9-PIN-TO-9-PIN PC CABLE (NULL MODEM TYPE)
To Console port To PC serial port

5 4 3 2 1 5 4 3 2 1
9 8 7 6 9 8 7 6
9-pin female connector 9-pin female connector
Name Abbr Pin Pin Abbr Name

Receive Data RxD 2 3 TxD Transmit Data
Transmit Data TxD 3 2 RxD Receive Data
Carrier Detect CD 1 7 RTS Request to Send
Clear to Send CTS 8 8 CTS Clear to Send
Request to Send RTS 7 1 CD Carrier Detect
Signal Ground Gnd 5 5 GND Signal Ground
Data Terminal Ready DTR 4 6 DSR Data Set Ready
Data Set Ready DSR 6 4 DTR Data Terminal Ready
For a terminal, use a 9-pin female to 25-pin null modem-type cable. The cable pinouts are illustrated
in Figure 2-57.
FIGURE 2-57 9-PIN-TO-25-PIN TERMINAL CABLE (NULL MODEM TYPE)
To Console port To terminal

5 4 3 2 1 1 2 3 4 5 6 7 8 9 10 11 12 13
9 8 7 6 14 15 16 17 18 19 20 21 22 23 24 25
9-pin female connector 25-pin male or female connector

Receive Data RxD 2 2 TxD Transmit Data
Transmit Data TxD 3 3 RxD Receive Data
Carrier Detect CD 1 4 RTS Request to Send
Request to Send RTS 7 8 CD Carrier Detect
Signal Ground GND 5 7 GND Signal Ground
Data Terminal Ready DTR 4 6 DSR Data Set Ready
Data Set Ready DSR 6 20 DTR Data Terminal Ready
(Continued)
2-64 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE CONNECTING A PC, TERMINAL, OR MODEM
PROCEDURE 2-16 CONNECTING A PC, TERMINAL, OR MODEM (CONTINUED)
For a modem, use a 9-pin female to 25-pin male straight-through-type cable. The cable pinouts are
illustrated in .
FIGURE 2-58 9-PIN-TO-25-PIN MODEM CABLE (STRAIGHT-THROUGH TYPE)
To Console port To modem

5 4 3 2 1 1 2 3 4 5 6 7 8 9 10 11 12 13
9 8 7 6 14 15 16 17 18 19 20 21 22 23 24 25
9-pin female connector 25-pin male connector

Transmit Data TxD 3 2 TxD Transmit Data
Receive Data RxD 2 3 RxD Receive Data
Request to Send RTS 7 4 RTS Request to Send
Carrier Detect CD 1 8 CD Carrier Detect
Signal Ground GND 5 7 GND Signal Ground
Data Set Ready DSR 6 6 DSR Data Set Ready
Data Terminal Ready DTR 4 20 DTR Data Terminal Ready
2 Connect one end of the cable to the console port on the S2500 and the other end to the serial port on
the back of the PC, terminal, or modem.
3 Verify that configurable parameters of the PC, terminal, or modem match the configuration settings of
the console port, specified earlier in this section in Table 2-18.
4 Turn on the PC, terminal, or modem.
O CT OB ER 28 , 2 01 3 2-65
POWERING THE ROUTER ON AND OFF CHAPTER 2: INSTALLING THE S2500 HARDWARE
POWERING THE ROUTER ON AND OFF

...................................
..
To power the S2500 on, plug in the power cord. To power the S2500 off, unplug the
power cord.
Figure 2-59 illustrates the location of the power receptacle on the S2500 rear panel.
FIGURE 2-59 LOCATION OF POWER RECEPTACLE ON S2500 REAR PANEL
Power
receptacle
2-66 O C T OBE R 2 8, 20 1 3
CHAPTER
LOGGING ON AND PERFORMING

3
ADMINISTRATIVE TASKS 3
...................................
....
This chapter describes how to start up the S2500, log on, and perform basic
administrative tasks.
Starting the System on page 3-2
Logging on to the System on page 3-5
Using the Command-line Interface on page 3-6
Performing Basic Administrative Tasks on page 3-11
Configuring The MNR S2500 to Perform IP Routing Functions on page 3-18
Accessing the S2500 Remotely on page 3-19
O CT OB ER 28 , 2 01 3 3-1
STARTING THE SYSTEM CHAPTER 3: LOGGING ON AND PERFORMING ADMINISTRATIVE TASKS
STARTING THE SYSTEM

...................................
..
To start up the S2500, follow Procedure 3-1.
PROCEDURE 3-1 STARTING THE S2500
1 Plug one end of the power cord into the rear panel of the S2500.
2 Plug the other end of the power cord into your power outlet.
Figure 3-1 illustrates the location of the power receptacle on the rear of the S2500.
FIGURE 3-1 S2500 REAR PANEL
Power
receptacle
3 Connect your PC or terminal to the S2500, as described under Connecting a PC, Terminal, or
Modem on page 2-63.
3-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE STARTING THE SYSTEM
VERIFYING SUCCESSFUL STARTUP

The startup process takes a few seconds. When the startup process has successfully
completed, the LEDs on the front panel should be on or off as described in Table 3-1. If
the LEDs on your S2500 appear differently than indicated in Table 3-1, see Error LED
Meanings in Appendix C, Troubleshooting for more information.
TABLE 3-1 LED STATUS AT SUCCESSFUL STARTUP
LED Status
1
Ethernet LAN Link On
(on base system)
Active Off If no packets are detected on the LAN.
Blinking If packets are detected on the LAN
Fault Off
SYSTEM Status All off
Fwd Off or blinking
Power/Fault Green
Run On
Load Off
Test Off
FlexWAN Serial1 Link On
Active On
Fault Off
WAN/Telco (T1/E1 CSU/DSU) Link On
Active On
Fault Off
10BASE-T Link On
(on 10BASE-T module)
Transmit Off If no packets are being transmitted on the LAN.
Blinking If packets are being transmitted on the LAN.
Receive Off If no packets are being received on the LAN.
Blinking If packets are being received on the LAN.
Collision Off
(Continued)
O CT OB ER 28 , 2 01 3 3-3
STARTING THE SYSTEM CHAPTER 3: LOGGING ON AND PERFORMING ADMINISTRATIVE TASKS
TABLE 3-1 LED STATUS AT SUCCESSFUL STARTUP (CONTINUED)
LED Status
V.24 Port Status Green Steady if the digital channel is idle; blinking if
audio packets are flowing.
Off If the CCGW service is disabled or the
corresponding channel is not configured to use the V.24
port (it is an analog channel).
Yellow If the CCGW service is enabled and the
corresponding channel is configured to use the V.24 port
(it is a digital channel), but the V.24 port is not connected.
E&M (Analog) Port Status Green Steady if the analog channel is idle; blinking if
Yellow CCGW functionality is not enabled; the DSP is
out of service; or a fault has been detected on the analog
channel corresponding to this port.
NOTE
When the S2500 boots up, the E&M port LEDs
are yellow until the first analog channel is
configured. Once an analog channel is
configured, the E&M port LEDs are off and
turn yellow if an enabled/active channel fails.
Off CCGW functionality is enabled, but the channel
corresponding to this port is disabled or is not configured
to use an E&M port (for example, it is a V.24 digital
channel).
1. For Ethernet and FlexWAN serial LEDs to display properly, an appropriate device must be connected to
the S2500 via a cable of the appropriate type, and this device must be powered on.
3-4 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE LOGGING ON TO THE SYSTEM
LOGGING ON TO THE SYSTEM

...................................
..
When your S2500 starts up, it takes a few seconds to complete the initialization process.
While the S2500 is initializing, various messages will appear on your terminal. The
S2500 has finished booting when the following message is displayed:
System Initialized and Running
To log on, follow Procedure 3-2.
PROCEDURE 3-2 LOGGING ON TO THE S2500
1 Press any key on the keyboard.

The following prompt appears:
NetLogin:
2 Enter the default account name:

root
The following prompt appears:
Password:
3 Press the <Return> key to enter a null string; this is the default local password.
The Network Manager prompt appears:
EnterpriseOS #
O CT OB ER 28 , 2 01 3 3-5
USING THE COMMAND-LINE INTERFACE CHAPTER 3: LOGGING ON AND PERFORMING ADMINISTRATIVE TASKS
USING THE COMMAND-LINE INTERFACE

...................................
..
Figure 3-2 illustrates the basic elements of the Enterprise OS command-line interface
syntax:
FIGURE 3-2 ENTERPRISE OS COMMAND-LINE INTERFACE SYNTAX
Values
Port or Path Identifier
Command Parameter
Service
ADD !<port> -IP NETAddr <IP address> [<network mask> [Ones Zeros [MTU]]] UnNumbered
You must enter an

exclamation point before Angle brackets enclose Square brackets enclose
a port, virtual port, variable parameters or values optional values or a list
or path number. Do not enter the angle brackets. of optional arguments.
Do not enter the square brackets.
A hyphen always precedes
the service name; if you enter A vertical bar separates
the service name, you must mutually exclusive values in a list
also enter the hyphen. Enter one of the values;
do not enter the bar itself.
Command Specifies the action to be taken. For a complete list of commands,

enter a question mark (?). For descriptions of the available commands, see the
Commands chapter in the Enterprise OS Software Reference Guide.
Port or Path Identifier Focuses the action of the command on the specified port
or path. If you do not include a port or path number, the command applies to all
ports or paths.
Service Focuses the action of the command on a particular service of the
system. In some casesif a parameter is unique to a particular service, for
exampleyou may not need to enter the service name.
Parameter Indicates the object of the action of the command. If two or more
services have parameters of the same name, you must include the service name in
the syntax so the command can be executed successfully. For information about
global parameters that affect the S2500 as a whole, see the Global Parameters
chapter in the Enterprise OS Software Reference Guide. For information about non-
global parameters, see the appropriate service chapter in the Enterprise OS
Software Reference Guide.
Values Specify how you want the parameter to be set. Values include numerics,
strings, or addresses depending on the parameter. For information about the
values associated with a particular parameter, see the appropriate service chapter
in the Enterprise OS Software Reference Guide.
3-6 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE USING THE COMMAND-LINE INTERFACE
Table 3-2 describes the symbols used in the Enterprise OS command-line interface.
TABLE 3-2 COMMAND-LINE INTERFACE SYNTAX SYMBOLS
Symbol Description
angle brackets < > Enclose a variable or value. You must specify the variable or value. For example,
in the syntax:
DELete -IP ADDRess <IP address>
you must supply a value for <IP address> when you enter the command. Do
not type the angle brackets.
If the angle brackets are enclosed in quotation marks, enclose the value you enter
in quotation marks. For example, in the syntax:
GetLdapConf [!port] <user name> <service name>
you must enclose the values you supply for <user name> and <service name>
with quotation marks.
square brackets [ ] Enclose an optional value or a list of optional arguments. You can specify one or
more values or arguments. For example, in the syntax:
SET PRIvilege = [User | NetMgr]
you can specify either User or NetMgr when you enter the command. Do not
type the square brackets.
parentheses ( ) Enclose a list of values that can be assigned to a single parameter. You must enter
at least one of the values. If you enter more than one value, you must type the
parentheses and separate the values with commas. For example, in the syntax:
SET CurrentPorts = ALL | (<port>, <port>)
you can specify two port numbers by enclosing them in parentheses and
separating them with a comma when you enter the command.
vertical bar | Separates mutually exclusive values; you must enter one of the values. For
example, in the syntax:
SETDefault -PIM BSRPeriod = <secs> | Default
you can enter a value for <secs> or you can enter the word Default. Do not
type the vertical bar.
hyphen - Precedes service names. When you enter a service name as part of a command,
you must precede the service name with a hyphen. For example, in the syntax:
SHow [!<port> |!*] -IP CONFiguration
you must include the hyphen with the service name when you enter the
command.
braces { } Enclose a list of required values. You must enter one of the values. For example,
in the syntax:
SETDefault -PIM BSFragLimit = {(100-1480) | Default}
you must enter either a value (between 100 and 1480) or the word Default.
(Continued)
O CT OB ER 28 , 2 01 3 3-7
TABLE 3-2 COMMAND-LINE INTERFACE SYNTAX SYMBOLS (CONTINUED)
Symbol Description
exclamation point ! Precedes a number that represents a port, virtual port, or path number. For
example, in the syntax:
SETDefault !<port> -IP RtphcHdrExtComp = Enable | Disable
you must include the exclamation point before the port number when you enter
the command.
ellipsis... Indicate that you may specify one or more additional arguments on the same
command line. For example, in the syntax:
ADD!<filterid> -IP FIlters <condition> [,<condition>...]
<condition> = <%offset>: [<operator>] <%pattern>
you may specify multiple conditions when you enter the command. Do not type
the ellipsis.
To use the command-line interface, follow Procedure 3-3.
PROCEDURE 3-3 USING THE COMMAND-LINE INTERFACE
1 Log on as root or as a user with Network Manager privilege.

For details about the root account, privileges, and passwords see Changing the root and
admin Passwords on page 3-11.
2 Type the command name.

You can also enter commands using an abbreviated version of the syntax style; the capitalized letters
in the syntax indicate the minimum letters you must enter for the command to be recognized. For
example, you can use SETD instead of the full form of the SETDefault command.
If the command has additional options, such as a port or path number, include it after the command
name.
If the command is modified by a parameter, type the service name (if necessary), the parameter
name, and values.
You can also abbreviate parameters, using only the letters that are capitalized in the syntax. For
example, in the command illustrated in Figure 3-2, you could use ADD -IP NET instead of the full
ADD -IP NETaddr.
3 Press <Return> after typing the complete command.
The software includes online help for commands, services, parameters, and syntax. The
syntax style that appears in the online help is the full form syntax; it contains full
names and visual cues for entering commands.
3-8 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE USING THE COMMAND-LINE INTERFACE
USING THE MENU-DRIVEN INTERFACE

If you are unsure of the command syntax, you can use the menu-driven interface,
which you access by entering the MEnu command. To use the menu-driven interface,
you must log on with Network Manager privilege.
NOTE
You cannot access all parameters from the menu-driven interface; for
example, you cannot change privilege level.
The MEnu command allows you to:
Display a list of available services.
Choose a service and display the list of parameters available for that service.
Display a list of parameters in the current service.
Choose a parameter and display the commands used with it.
Check the active and default values of a parameter.
Display the online help syntax of a parameter.
Enter the new value of a parameter.
For more information about the MEnu command, see the Commands chapter in the
Enterprise OS Software Reference Guide.
O CT OB ER 28 , 2 01 3 3-9
To use the menu-driven interface, follow Procedure 3-4.
PROCEDURE 3-4 USING THE MENU-DRIVEN INTERFACE
1 Log on as root or as a user with Network Manager privilege.
2 Access the menu-driven interface using:

MEnu [-<service>] [<param-name>]
If the CurrentServices parameter is set to ALL, the Main menu appears after you enter the MEnu
command. If the CurrentServices parameter is set to a particular service, the Main menu displays
only that service. For example, if the current service is POrt, only the POrt Service entry appears in
the Main menu. For details about the CurrentServices parameter, see Chapter 2, Global Parameters
in the Enterprise OS Software Reference Guide.
If you specify the service in the MEnu command, the parameters in the specified service are
displayed, not the ones in the current service. For example, if the current service is POrt, and you
enter MEnu -PAth, the PAth Service menu is displayed.
If you include the parameter to be modified or displayed when you enter the MEnu command, the
first two levels of the service menu are skipped.
For example, if you enter MEnu -PAth NAme, the following menu appears:
==================== SHow -PAth NAme ==================
Path !1 NAme = Path1
Path !2 NAme = Path2
========= -PAth NAme parameter menu (Level 3)==========
1 - SetD
Select (1-1) ... <CR> to Exit ====>
3 Select the desired service by entering the number corresponding to that service.
In the service menu, the parameters are numbered. The commands that you can use to modify the
parameters are enclosed in parentheses. If no commands follow a parameter, as in the case of the
CONFiguration parameter in the POrt Service menu, you can only display the parameteryou
cannot modify it using a command.
4 Select the parameter you want to configure by entering the number corresponding to that parameter.
If you select a configurable parameter from the service menu, another menu displays information on
that parameter and prompts you for the port number (if appropriate) and command.
5 To escape out of a menu to the previous menu level, press the <Return> key.
For example, if you are at the SYS Service menu and you press the <Return> key, you will return to
the Main menu; if you are at the Main menu and you press the <Return> key, you will return to the
command-line interface.
3-10 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE PERFORMING BASIC ADMINISTRATIVE TASKS
PERFORMING BASIC ADMINISTRATIVE TASKS

...................................
..
Table 3-3 summarizes basic administrative tasks associated with managing an S2500
router and indicates whether performing each task is required, recommended, or
optional.
TABLE 3-3 ADMINISTRATIVE TASK SUMMARY
Task Status of Task
Changing the root and admin Required

Passwords
Changing the Default Console Do only if you want to attach a

Port Baud Rate terminal with a baud rate other
than 9600.
Managing User Accounts Optional
Setting the Time and Date Recommended
Setting System Information Required
Setting Up Security Access Recommended
The following subsections describe these tasks in greater detail. For information on the
commands and parameters used in this chapter, see the Enterprise OS Software Reference
Guide.
CHANGING THE ROOT AND ADMIN PASSWORDS

EOS supports the following privileged user accounts:
root associated with the Network Manager privilege level, which enables all
software commands. In order to log in as root you must enter the Network
Manager password.
admin associated with the User privilege level, which enables only a subset
of the software commands. In order to log in as admin you must enter the User
password.
O CT OB ER 28 , 2 01 3 3-11
PERFORMING BASIC ADMINISTRATIVE TASKS CHAPTER 3: LOGGING ON AND PERFORMING ADMINISTRATIVE TASKS
NOTE
To change the privilege level without logging off, use:
SET PRIvilege = User | NetMgr
If you are logged on at the User privilege level and you issue the
SET PRIvilege = NetMgr command to change the privilege level to
Network Manager, you are prompted to enter the Network Manager
password. You must enter the Network Manager password in order to raise
your privilege level.
The default password for both the Network Manager (root) and the User (admin)
privilege is a null string, which you generate by pressing the <Return> key. For
security purposes, you should specify a new passwords for both privilege levels
immediately after you log on for the first time. To set the passwords the first time,
execute the SETDefault command with an empty string for the old password, using:
SETDefault -SYS NMPassWord = <new password>
<new password>
SETDefault -SYS UMPassWord = <new password>
<new password>
The new password you specify is case-sensitive and must be at least 7 characters. Valid
characters are limited to ASCII codes 32 through 126. In addition, the string of six
asterisks (******) is not allowed as a Network Manager or User password. This string is
reserved for use as a non-operational value when passwords are captured using the
ASCII capture feature.
The maximum password length varies, depending on whether or not the account is
configured for RADIUS authentication.
If the account is configured for RADIUS authentication (the AC service
RESolutionOrder parameter is set to Radius or Radius Local), the maximum
password length is 31 characters.
If the account is configured for local authentication (the AC service
RESolutionOrder parameter is set to Local or None), the maximum password
length is 15 characters.
NOTE
If you configure a RADIUS account with a 16-31 character password, you
should also configure at least one local account on the device with a
password that is 15 characters or less. This allows the local account to still be
able to log on to the device in the event of a RADIUS server failure.
3-12 O C T OBE R 2 8, 20 1 3
NOTE
The default minimum length for the Network Manager (root) and User
(admin) passwords is 7 characters. You can configure the minimum length
using the PwMinLength parameter. For details, see the description of the
PwMinLength parameter in the SYS Service Parameters chapter of the
Enterprise OS Software Reference Guide. If the Network Manager (root) or
User (admin) password set to NULL, it is allowed to remain at that value
until the password is changed. Once the Network Manager (root)
password is changed from NULL, however, it must comply with the
password minimum length requirement and cannot be set back to NULL
except from the boot monitor.
Follow these guidelines when you change a password:
Log on as root.
Clear the User password before you clear the Network Manager password.
Define the Network Manager password before you define the User password.
To change both the Network Manager and User passwords, enter:
SysPassWord
A menu is displayed.
Follow the menu to set the Network Manager password and then the User password.
CAUTION
You should set both the Network Manager and the User password. If
you do not set the Network Manager password, any unauthorized user
can log on with Network Manager privilege. If you do not set the User
password, any unauthorized user can log on with User privilege.
O CT OB ER 28 , 2 01 3 3-13
CHANGING THE DEFAULT CONSOLE PORT BAUD

RATE
Changing the default console port baud rate is necessary only if you want to attach a
terminal with a baud rate other than 9600.
To change the default console port baud rate, follow Procedure 3-5.
PROCEDURE 3-5 CHANGING THE DEFAULT CONSOLE PORT BAUD RATE
1 At the Network Manager prompt (EnterpriseOS #), enter:

SysconF
The System Configuration menu appears.
2 Select the Console Port option.

A submenu appears, displaying the console port baud rate options.
3 Select the baud rate you want to use.
4 Set the terminal baud rate to match the baud rate configured for the console port.
CAUTION
Be sure to change the terminal baud rate before you reset the S2500. Once the S2500
resets, it uses the new baud rate. If you have not changed the terminal baud rate to
match this new rate, you will not be able to access the system software to enter any
commands at the default 9600 baud rate.
5 After you change the terminal baud rate, reset the S2500.
The new console port baud rate does not become effective until you reset the router.
3-14 O C T OBE R 2 8, 20 1 3
MANAGING USER ACCOUNTS

You can add user accounts when logged in as root with Network Manager privileges.
To add a user account, log on as root and use:
AddUser [<username>]
If you do not specify a username, you will be prompted for one. Specify the
privilege and password at the prompts.
To delete an account use:
DELeteUser [<username>]
To force a user password to expire, use:
EXPire [<username>]
To manage multiple users and see all user accounts, enter:
UserManage
Any user can change his or her password by entering:
PassWord
O CT OB ER 28 , 2 01 3 3-15
SETTING THE TIME AND DATE

Motorola recommends that you set the time and date. Use:
SET -SYS DATE = <YYYY/MM/DD HH:MM[:ss]>
Enter the time in 24-hour-clock format. For example, to set the date and time to
February 10, 2001, 2:40 p.m., enter:
SET -SYS DATE = 2001/2/10 14:40
NOTE
You can use the Network Time Protocol (NTP) service to synchronize the
computer clock in a distributed network. For details, see the NTP Service
Parameters chapter in the Enterprise OS Software Reference Guide.
USING THE DAYLIGHT SAVING TIME FEATURE

The EOS Daylight Saving Time feature automatically adjusts the system time to reflect
the local Daylight Saving Time worldwide. Using the SYS service DSTime parameter,
you configure Daylight Saving Time only onceusing either a definite date
(in mm/dd/yyyy format) or a conventional date (such as the first Sunday in April or the
last Sunday in October).
After you configure the DSTime initially, EOS uses your configuration to automatically
adjust Daylight Saving Time as appropriate for the country and region in which the
router is installed and in the future will compute the local system time without user
intervention.
To configure Daylight Saving Time, use:
SETDefault -SYS DSTime = None |
({<startZone>, <startWeeK>, <startDay>, <startMonth>,
<startTime>, <startOffset>, | <startZone>, <startDate>,
<startTime>, <startOffset>,}
{<endZone>, <endWeeK>, <endDay>, <endMonth>, <endTime>,
<endOffset> | <endZone>, <endDate>, <endTime>,
<endOffset>})
For details see the description of the DSTime parameter in the SYS Service Parameters
chapter in the Enterprise OS Software Reference Guide.
3-16 O C T OBE R 2 8, 20 1 3
SETTING SYSTEM INFORMATION

You should set the system name to identify the router to SNMP management stations.
You can also set the location and contact so that other system administrators can
contact you for information.
(Required) To assign a name to the S2500 use:
SETDefault -SYS SysNAMe = <string>
For example, to set the system name to Engineering1.Sunnyvale, enter:
SETDefault -SYS SysNAMe = Engineering1.Sunnyvale
(Optional) To specify the system location use:
SETDefault -SYS SysLOCation = <string>
For example, to set the system location to SecondFloor.Lab, enter:
SETDefault -SYS SysLOCation = SecondFloor.Lab
(Optional) To identify the contact person managing the S2500 use:
SETDefault -SYS SysCONtact = <string>
For example, to identify Mary Smith as the system contact and (408) 555-1111 as
the phone number at which to reach her, enter:
SETDefault -SYS SysContact = Mary Smith (408) 555-1111
If you specify the system contact, users can obtain this information using the
SHow -SYS SysCONtact command.
SETTING UP SECURITY ACCESS

To allow read/write access to files only to a system administrator, use these commands
and parameters:
The SNMP Service COMmunity parameter modifies the list of communities and
managers with read/write access to the device. By default, any application can
read the SNMP MIBs. To provide write access for a particular management
application, you must configure a community and manager(s). For further
information on the COMmunity parameter, see the SNMP Service Parameters in
the Enterprise OS Software Reference Guide.
The SysLog feature generates a log message on a network management
workstation that captures configuration changes and events for monitoring
routers. For more information on this feature, see the Syslog Messages appendix
in the Enterprise OS Software User Guide.
The -SYS TelnetManager SshManager parameters allow you to set up a list of
allowed Telnet and SSH managers. Both Telnet and SSH shared this list of allowed
managers. Adding or changing a member of this list using the TelnetManager
parameter changes the list of allowed managers for SSH as well; adding or
changing a member of this list using the SshManager parameter changes the list
of allowed managers for Telnet as well.
O CT OB ER 28 , 2 01 3 3-17
CONFIGURING THE MNR S2500 TO PERFORM IP ROUTING FUNCTIONS CHAPTER 3: LOGGING ON AND PERFORMING ADMINISTRATIVE TASKS
CONFIGURING THE MNR S2500 TO PERFORM

IP ROUTING FUNCTIONS
...................................
..
This section outlines the basic steps you must perform before you can access the router
over its 10/100 Ethernet interface and use the S2500 to perform IP routing functions.
To configure a basic IP router, follow Procedure 3-6.
PROCEDURE 3-6 CONFIGURING THE MNR S2500 TO PERFORM IP ROUTING FUNCTIONS
1 Assign IP addresses to the routers Ethernet (LAN) port using:

SETDefault !<portnumber> -IP NETaddr = <IPaddress> <subnet mask>
For example, to assign IP addresses 10.79.132.28 using subnet mask 255.255.255.0, enter:
SETDefault !1 -IP NETaddr = 10.79.132.28 255.255.255.0
2 If necessary, add static routes to the router.

If the router will be participating in a dynamic routing protocol such as RIP or OSPF, static routes
are not required. To enable these protocols on the router use:
SETDefault !<port> -RIPIP CONTrol = (TAlk, Listen)
and/or
SETDefault !<port> -OSPF CONTrol = Enable
NOTE
See the Configuring IP Routing chapter in the Enterprise OS Software User Guide for details
about configuring the router for dynamic routing protocols.
If the router requires static routes, add them using:
ADD -IP ROUte <IP net address> [<mask>] {<gateway | !<port>} <metric>
[Override]
For example, assuming the default gateway is on network 10.79.139.2, you could add a default
route for the IP addresses you entered in step 1 with the following command:
ADD -IP ROUte 0.0.0.0 10.79.139.2 5
NOTE
As shown in the example above, when you add a default route, you are not required to
enter a subnet mask.
3 To enable the router to perform IP routing (forward packets that are not destined for it), enter:
SETDefault -IP CONTrol = Route
3-18 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE ACCESSING THE S2500 REMOTELY
ACCESSING THE S2500 REMOTELY

...................................
..
After you have configured the IP address of the S2500 using a direct console
connection, you can access the user interface remotely using one of the following
methods:
Telnet Use Telnet to access the MNR S2500 from a device (for example, a
workstation) on the same extended network or internetwork, using the IP address
you configured for the S2500 as described under Configuring The MNR S2500
to Perform IP Routing Functions on page 3-18.
SSH Use SSH (secure shell) to access the MNR S2500 securely. SSH provides
secure encrypted communications between two untrusted hosts over an insecure
network. Secure copy (SCP) copies files between hosts on a network, using SSH
for data transfer. It provides the same security as SSH. The MNR S2500 can be
used within the SSH architecture in the following ways:
As an SCP file transfer server, supporting one secure file transfer operation
at a time.
As an SSH client/server, supporting four concurrent sessions.
For details, see the Secure Shell (SSH) Support section in the Configuring
Security Features chapter of the Enterprise OS Software User Guide.
SNMP Use Simple Network Management Protocol (SNMP) to view and
configure a subset of the parameters from a remote host. For information on
preparing the MNR S2500 to run SNMP, see Configuring the SNMP Service in
the Configuring Network Management chapter of the Enterprise OS Software User
Guide.
SNMPv3 Use SNMPv3 to incorporate security into the SNMP model. SNMPv3
supports provides authentication and encryption functions and allows you to
determine whether or not given USM users are allowed to access particular MIB
objects to perform specific functions. For details, see the SNMPv3 Support
section in the Configuring Network Management chapter of the Enterprise OS
Software User Guide.
O CT OB ER 28 , 2 01 3 3-19
CHAPTER
CONFIGURING PATHS, PORTS, AND

4
CONNECTORS 4
...................................
....
This chapter provides conceptual information about ports, paths, and connectors and
basic configuration procedures for each of the interfaces on the MNR S2500 router.
Understanding Connectors, Paths and Ports on page 4-2
Path and Port Numbering on page 4-3
Path, Port, and Connector Services and Syntax on page 4-6
Configuring the Ethernet Interface(s) on page 4-7
Configuring the FlexWAN Serial Interface(s) on page 4-9
Configuring the WAN/Telco (T1/E1 CSU/DSU) Interfaces on page 4-12
Configuring the V.24 (CCGW Digital Conventional) Interfaces on page 4-15
Configuring the E&M (CCGW Analog Conventional) Interfaces on page 4-16
Where To Go From Here on page 4-17
O CT OB ER 28 , 2 01 3 4-1
UNDERSTANDING CONNECTORS, PATHS AND PORTS CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS
UNDERSTANDING CONNECTORS, PATHS AND

PORTS
...................................
..
The terms connector, path and port represent the fundamental interface syntax on the
S2500.
A connector is the physical interface itself; for example, a FlexWAN connector or
a WAN/Telco (T1/E1 CSU/DSU) connector. All connectors, by default, carry one
path each.
A path is the connection on the physical interface that connects the S2500 to a
physical network medium such as Ethernet, a T1/E1 line, or serial line. Each path
is associated with a connector.
A port is the logical interface used by the software to represent a connection to a
network.
Figure 4-1 illustrates the relationship between connectors, paths and ports.
FIGURE 4-1 RELATIONSHIP BETWEEN CONNECTORS, PATHS, AND PORTS
Physical connectors
S2500 chassis
Physical path Logical port

!<path> !<port>
Physical path Logical port

!<path> !<port>
4-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE PATH AND PORT NUMBERING
PATH AND PORT NUMBERING

...................................
..
For software purposes, paths are numbered 1, 2, 3, and so on. The path number may be
followed by a letter or a decimal and a channel number. By default, each path is
assigned to one port. For example, all network traffic received on physical path 1 is
treated by the software as arriving on logical port 1, and all traffic that the software
transmits through logical port 1 passes through physical path 1. This default
configuration is called a static port and path binding. A static path is a path that is mapped
to a port. All paths are static by default.
You can redefine the default mapping using software commands. For example, you can
redirect network traffic that is being routed through a particular logical port to a
different physical path without manually switching cables on the connector.
MAPPING MULTIPLE PATHS TO A SINGLE PORT

Each logical port is usually associated with only one physical path. For Ethernet and
Frame Relay, for example, the path-to-port ratio is always one-to-one. But for paths
connected to serial lines, multiple paths can be associated with and statically bound to
a single port if the Point-to-Point Protocol (PPP) is running over the port.
You can use multiple static paths on the same port for disaster recovery, dial-on-
demand, failover, or bandwidth-on-demand, and you can also create dynamic paths,
that are not assigned to any one port but are available in a dial pool.
DYNAMIC PATHS
You can unbind paths from their ports and place them in a dial path pool to be shared
by more than one port using:
SETDefault !<path> -PATH DialCONTrol = DYNamic
A dial pool enables you to dial multiple destinations, use bandwidth-on- demand, and
failover to another line without having to reserve specific paths for a port. The paths in
the dial pool are called dynamic paths. For more information about the use of the dial
path pool, see the Configuring Port Bandwidth Management chapter in the Enterprise OS
Software User Guide.
O CT OB ER 28 , 2 01 3 4-3
PATH AND PORT NUMBERING CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS
MAPPING MULTIPLE PORTS TO A SINGLE PATH

(VIRTUAL PORTS)
To configure multiple ports over one path, you create virtual ports. A virtual port
functions the same way as a nonvirtual port doesas a logical interface that represents
a connection to a network.
You can assign a virtual port to a static path or to the SysCallerID of a remote site.
SysCallerID virtual ports are available when you are using PPP in a virtual private
network (VPN); these virtual ports use paths in a dial pool and are not associated to
any one path.
S2500 PORT AND PATH NUMBERING

Figure 4-2 shows the path/connector to port number mappings for MNR S2500 routers
with an E&M module installed in the analog I/O slot. As illustrated in Figure 4-2, the
MNR S2500 software reserves physical ports 4 through 7 for the analog conventional
E&M ports.
FIGURE 4-2 S2500 PATH-TO-PORT MAPPINGS
LAN/WAN 3 maps
path 3 to port 3
E&M analog paths 4-7 map to ports 4-7
Port 4 maps to channel 1
LAN/WAN 2 maps Port 5 maps to channel 2
path 2 to port 2
LAN 1 maps
path 1 to port 1

SYSTEM
LAN
T1/E1 "
CSU/

Console
DSU 10BaseT Status

#
!
4 5 6 7
1 I/O Module A 2 I/O Module B 3 Analog Module
4-4 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE PATH AND PORT NUMBERING
The S2500 V.24 module can be installed in I/O slot A (port 2) or B (port 3). The MNR
S2500 software reserves ports 2 or 3 A and B for digital conventional V.24 ports.
If the V.24 module is installed in port 2, as illustrated in Figure 4-3, the software
uses port numbers 2A and 2B.
3B.
NOTE
FIGURE 4-3 S2500 PATH-TO-PORT MAPPINGS (V.24 MODULE IN I/O SLOT A)
LAN/WAN 2 maps
path 2 to ports 2A and 2B
LAN 1 maps
path 1 to port 1

V.24 SYSTEM
LAN
Console

Status

1 I/O Module A 2 3
O CT OB ER 28 , 2 01 3 4-5
PATH, PORT, AND CONNECTOR SERVICES AND SYNTAX CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS
PATH, PORT, AND CONNECTOR SERVICES

AND SYNTAX
...................................
..
Path and port parameters have their own dedicated service type, but connector
parameters do not have a dedicated service type:
Use the PAth service to configure paths and connectors.
Use the POrt service to configure ports.
Table 4-1 lists the path and port numbering syntax rules used for default naming for the
S2500.
TABLE 4-1 S2500 PATH/PORT SYNTAX RULES
Path/Port Syntax
Interface
Syntax Description
Ethernet (LAN) connectors (10BASE-T/100BASE-TX) <n> n=1

provided on base system
Ethernet (LAN) connectors (10BASE-T) <n> n = 2 or 3

require optional 10BASE-T module
FlexWAN Serial connectors <n> n = 2 or 3

require optional FlexWAN module
WAN/Telco (T1/E1 CSU/DSU) connectors <n> n = 2 or 3

require optional WAN/Telco (T1/E1 CSU/DSU) module
V.24 connectors <nA> and <nB> n = 2 or 31

require optional V.24 module
E&M Analog connectors <n> n = 4, 5, 6, 72

require optional conventional-to-IP interface kit (E&M
module and DSP SIMM)
1. V.24 paths/ports 2A and 2B or 3A and 3B map to digital conventional channels 1 and

2 with the following mapping:
Port 2A -> Channel 1 Port 3A-> Channel 1
Port 2B -> Channel 2 Port 3B -> Channel 2
2. E&M paths/ports 4-7 map to analog conventional channels 1-4
as follows:
Path/Port 4 maps to channel 1
4-6 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE CONFIGURING THE ETHERNET INTERFACE(S)
CONFIGURING THE ETHERNET INTERFACE(S)

...................................
..
This section tells you how to configure the Ethernet interfaces on your S2500. One
Ethernet interface is provided on the S2500 base system. If the optional 10BASE-T
module is installed, the router supports additional Ethernet interfaces.
NOTE
NOTE
The 10BASE-T module does not support tagged VLAN ports with certain
versions of EOS software certified for system releases prior to the
ASTRO 25 7.8 system release. If you attempt to configure a tagged VLAN
port on the 10BASE-T module interface of an S2500 router running a version
of EOS software that does not support tagged VLAN ports, the system
returns an error message similar to the following:
VLANs are currently supported only on Ethernet.
By default, the S2500 Ethernet paths and ports are enabled.
The software automatically detects the following settings:
Baud 10 Mbps or 100 Mbps
NOTE
The Ethernet interface on the optional 10BASE-T module supports a baud
rate of 10 Mbps only.
Duplex full or half
To set up ports and paths for local area network (LAN) Ethernet interfaces, follow
Procedure 4-1.
O CT OB ER 28 , 2 01 3 4-7
CONFIGURING THE ETHERNET INTERFACE(S) CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS
PROCEDURE 4-1 CONFIGURING PORTS AND PATHS FOR LAN (ETHERNET) INTERFACES
1 (optional) Assign a name to the path using:

SETDefault !<path> -PAth NAme = string
For example, to name path 1, enter:
SETDefault !1 -PAth NAme = "FLOOR_1"
Some restrictions apply to the name you assign using the -PAth NAme parameter. For more
information, see the PAth Service Parameters chapter in the Enterprise OS Software Reference Guide.
2 Disable all local area ports that you are not using by entering for each port:
SETDefault !<port> -POrt CONTrol = Disabled
NOTE
Motorola recommends that you disable all ports you do not use. Disabling unused ports
improves performance.
All ports are enabled by default. If the port has been disabled, you must re-enable the port to use it.
3 Repeat steps 1 and 2 for each local area port and local area path on the S2500.
4-8 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE CONFIGURING THE FLEXWAN SERIAL INTERFACE(S)
CONFIGURING THE FLEXWAN SERIAL

INTERFACE(S)
...................................
..
FlexWAN interfaces provide connection to industry-standard V.35, RS-232, RS-449,
EIA-530, or X.21 Data Communications Equipment (DCE) or Data Terminal Equipment
(DTE) serial devices.
NOTE
The S2500 supports FlexWAN serial interfaces (one per I/O module) only if
the hardware configuration includes an optional FlexWAN module.
CONFIGURING FLEXWAN INTERFACES WITH DCE

DEVICES
This section describes how to configure the FlexWAN serial interfaces when connected
to DCE devices (external modems or CSUs/DSUs).
When connected to a DCE device, the FlexWAN serial interface automatically detects
the following settings:
Clock internal or external
Connector type RS-232, V.35, X.21, RS-449, or EIA-530
O CT OB ER 28 , 2 01 3 4-9
CONFIGURING THE FLEXWAN SERIAL INTERFACE(S) CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS
FLEXWAN INTERFACE CONFIGURATION PREREQUISITES

(DCE DEVICES)
Before you configure FlexWAN interfaces connected to DCE devices, complete the
following tasks:
Cable the FlexWAN serial interface and connect it to the telephone network.
Log on to the system with Network Manager privilege.
FLEXWAN INTERFACE CONFIGURATION PROCEDURE

(DCE DEVICES)
To configure the FlexWAN serial interface with a DCE device, follow Procedure 4-2.
PROCEDURE 4-2 CONFIGURING FLEXWAN INTERFACES WITH DCE DEVICES
1 The default baud rate for the FlexWAN serial interface is 64 Kbps. If you need to change the baud rate,
use:
SETDefault !<path> -PATH Baud = <kbps> (1.2-2048)
2 The default device type is Modem. If you need to change the device type, specify the external device
type attached to the FlexWAN cable using:
SETDefault !<path> -PATH ExDevType = [Modem | Bri | Sw56 | Async]
3 If you have changed any of the default settings, re-enable the path to make sure all settings on the
path take effect using:
SETDefault !<path> -PATH CONTrol = Enabled
4-10 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE CONFIGURING THE FLEXWAN SERIAL INTERFACE(S)
CONFIGURING FLEXWAN SERIAL INTERFACES WITH

DTE DEVICES
This section describes how to configure the FlexWAN serial interfaces when connecting
directly to DTE devices.
When connected to a DTE device, the FlexWAN serial interface automatically detects
the following settings:
Line type leased
Clock internal or external
Connector type RS-232, V.35, X.21, or RS-449
FLEXWAN INTERFACE CONFIGURATION PREREQUISITES (DTE

DEVICES)
Before you configure FlexWAN interfaces connected to DTE devices, complete the
following tasks:
Attach the FlexWAN cable to the FlexWAN serial interfaces and the line
equipment (either DCE or DTE).
Log on to the system with Network Manager privilege.
FLEXWAN INTERFACE CONFIGURATION PROCEDURE (DTE DEVICES)

To configure the FlexWAN serial interface with a DTE device, follow Procedure 4-3.
PROCEDURE 4-3 CONFIGURING FLEXWAN INTERFACES WITH DTE DEVICES
1 The default baud rate for the serial FlexWAN interface is 64 Kbps. If you need to change the baud rate,
use:
SETDefault !<path> -PAth Baud = <kbps> (1.2-2048)
2 Set the owner of the port using:

SETDefault !<port> -POrt OWNer = PPP
3 If you have changed any of the default path settings, re-enable the path to ensure that the new settings
take effect using:
SETDefault !<path> -PAth CONTrol = Enabled
O CT OB ER 28 , 2 01 3 4-11
CONFIGURING THE WAN/TELCO (T1/E1 CSU/DSU) INTERFACES CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS
CONFIGURING THE WAN/TELCO

(T1/E1 CSU/DSU) INTERFACES
...................................
..
You can configure the WAN/Telco (T1/E1 CSU/DSU) interfaces in a variety of ways;
there is no default configuration for these interfaces. For example, you can configure
the WAN/Telco (T1/E1 CSU/DSU) interfaces to:
Connect to T1 or E1 lines.
Run single-path leased services.
NOTE
The S2500 supports WAN/Telco (T1/E1 CSU/DSU) interfaces (one per I/O
module) only if the hardware configuration includes an optional T1/E1 CSU/
DSU module.
WAN/TELCO (T1/E1 CSU/DSU) INTERFACE

CONFIGURATION PREREQUISITES
Before you configure a WAN/Telco (T1/E1 CSU/DSU) interface, complete the following
tasks:
Attach a RJ-45 cable between the WAN/Telco (T1/E1 CSU/DSU) interface and an
appropriate Telco switch or external CSU.
Log on to the system with Network Manager privileges.
4-12 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE CONFIGURING THE WAN/TELCO (T1/E1 CSU/DSU) INTERFACES
WAN/TELCO (T1/E1 CSU/DSU) INTERFACE

CONFIGURATION PROCEDURE
To configure a WAN/Telco (T1/E1 CSU/DSU) interface, follow Procedure 4-4.
PROCEDURE 4-4 CONFIGURING WAN/TELCO (T1/E1 CSU/DSU) INTERFACES
1 Set the FrameMode as appropriate for your setup using:

SETDefault !<path> -PAth FrameMode = T1_SF|T1_ESF|E1_CRC4|E1_NOCRC
where <path> = 2 or 3.
You can specify any of the following FrameMode values:
T1_SF Superframe format T1
T1_ESF Extended Superframe format T1
E1_CRC4 CRC-active E1.
E1_NOCRC E1 without an active CRC
2 Set the connector type as appropriate for your setup using

SETDefault !<path> -PAth CONNector = E1_Unstructured| T1_Unstructured
3 Set the LineCoding as appropriate for your setup using:

SETDefault !<path> -PAth LineCoding = B8ZS | AMI | HDB3
The LineCoding parameter specifies the transmission encoding method for a serial line. The coding
method you specify for the serial line must match the attached communication device. Use AMI or
B8ZS for T1 connectors and HDB3 for E1 connectors.
(Continued)
O CT OB ER 28 , 2 01 3 4-13
CONFIGURING THE WAN/TELCO (T1/E1 CSU/DSU) INTERFACES CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS
PROCEDURE 4-4 CONFIGURING WAN/TELCO (T1/E1 CSU/DSU) INTERFACES
4 Set the LineDistance as appropriate for your setup using:

SETDefault !<path> -PAth LineDistance = LH1 | LH2 | LH3 | LH4 | SH1 |
SH2 | SH3 | SH4 | SH5 | SH7
The LineDistance parameter determines the long haul (LH) or short haul (SH) line distance. Enter one
of the following options:
LH1 (T1, 0 dB)
LH2 (T1, 7.5 dB)
LH3 (T1, 15 dB)
LH4 (T1, 22.5 dB)
SH1 (T1, 0-133 feet)
SH2 (T1, 133-266 feet)
SH3 (T1, 266-399 feet
SH4 (T1, 399-533 feet)
SH5 (T1, 533-655 feet)
SH7 (E1, G.703 120 Ohm)
T1 lines support long haul and short haul settings, in units of dB for long haul, and in units of feet for
short haul. E1 lines support only short haul. Set LineDistance to SH7 for E1 lines.
NOTE
The default setting for ASTRO 25 systems is SH1. This setting is included in the boot.cfg
files generated by the TNCT configuration tool. It minimizes cross talk issues and works
for implementations where the T1 interface and the MNR S2500 are collocated in the same
room (within 133 cable feet of each other).
5 Enable the connector using:

SETDefault !<path> -PAth ConnControl = Enabled
NOTE
Connector parameter settings are not applied until the connector is enabled.
4-14 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE CONFIGURING THE V.24 (CCGW DIGITAL CONVENTIONAL) INTERFACES
CONFIGURING THE V.24 (CCGW DIGITAL

CONVENTIONAL) INTERFACES
...................................
..
An MNR S2500 router augmented with a V.24 module supports digital conventional
CCGW operation. No configuration is required for the V.24 interfaces. However, if you
use the network management application to configure digital conventional parameters
(the V.24 clocking source, for example) while the CCGW is running, you must issue the
following commands to direct the CCGW to apply the changes:
setd -ccgw cont=d
setd -ccgw cont=e
If you configure the digital conventional parameters prior to initial bootup, the CCGW
configures with the values in the LDAP database.
For information about how to configure CCGW functionality on an S2500 router, see
the Configuring CCGW Functionality on MNR S2500 Routers chapter in the
Enterprise OS Software User Guide.
O CT OB ER 28 , 2 01 3 4-15
CONFIGURING THE E&M (CCGW ANALOG CONVENTIONAL) INTERFACES CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS
CONFIGURING THE E&M (CCGW ANALOG

CONVENTIONAL) INTERFACES
...................................
..
An MNR S2500 router augmented with the conventional-to-IP interface kit (E&M
module and DSP SIMM) provides 4 four-wire with E&M relay interfaces to
conventional base stations. No configuration is required for the S2500 E&M (analog)
interfaces. For information about how to configure CCGW functionality on an S2500
router, see the Configuring CCGW Functionality on MNR S2500 Routers chapter in
the Enterprise OS Software User Guide.
4-16 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE WHERE TO GO FROM HERE
WHERE TO GO FROM HERE

...................................
..
After you have configured the interfaces on your S2500, you can configure the services
and protocols you want to use.
Table 4-2 provides a list of services and protocols supported by the S2500 and directs
you to the appropriate chapters in the Enterprise OS Software User Guide and the
Enterprise OS Software Reference Guide for further configuration instructions.
TABLE 4-2 S2500-SUPPORTED SERVICES
Enterprise OS Enterprise OS
Service or Protocol
Software User Guide Software Reference Guide
IP Routing Protocols and Services
IP Routing Configuring IP Routing IP Service Parameters
IP Quality of Service Configuring Quality of Service (IPQoS) IPQoS Service Parameters
System IP Configuring System IP (SYSIP) IP Service Parameters
OSPF Configuring IP Routing OSPF Service Parameters
BGP Configuring IP Routing BGP Service Parameters
IPv6 Configuring IPv6 Routing IPv6 Service Parameters
RSVP Configuring the Resource Reservation RSVP Service Parameters
Protocol (RSVP)
DHCP Configuring the Dynamic Host DHCP Service Parameters
Configuration Protocol (DHCP)
NAT Configuring Network Address NAT Service Parameters
Translation (NAT)
RIP-IP Configuring IP Routing RIPIP Service Parameters
Multicast IP Routing Configuring IP Multicast Routing MIP Service Parameters
PIM-SM Configuring Protocol Independent PIM Service Parameters
Multicast-Sparse Mode (PIM)
RDP Configuring the Router Discovery RDP Service Parameters
Protocol
(Continued)
O CT OB ER 28 , 2 01 3 4-17
WHERE TO GO FROM HERE CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS
TABLE 4-2 S2500-SUPPORTED SERVICES (CONTINUED)
Service or Protocol
WAN Protocols and Services
Frame Relay Configuring Wide Area Networking FR Service Parameters
Using Frame Relay
PPP Configuring Wide Area Networking PPP Service Parameters
Using PPP
Port Bandwidth Chapter 19, Configuring Port Bandwidth Chapter 28, PAth Service Parameters
Management Management Chapter 30, POrt Service Parameters
Protocol Reservation Configuring Protocol Reservation FIlter Service Parameters
IP Service Parameters
POrt Service Parameters
Data Compression Configuring Data Compression PAth Service Parameters
Prioritization Configuring Prioritization of FIlter Service Parameters
Multiprotocol Data IP Service Parameters
LAN Protocols and Services
Bridging Configuring Bridging BRidge Service Parameters
STP Service Parameters
Mnemonic Filtering Configuring Bridging FIlter Service Parameters
UDP Broadcast Helper Configuring the User Datagram Protocol UDPHELP Service Parameters
(UDP) Broadcast Helper
(Continued)
4-18 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE WHERE TO GO FROM HERE
TABLE 4-2 S2500-SUPPORTED SERVICES (CONTINUED)
Service or Protocol
VPN Tunnels and Security
VPNs (overview) Configuring Virtual Private Networks
(VPNs)An Overview
Protocol Authentication Configuring Security Features CRYPTO Service Parameters
Dynamic Security Policies Configuring Security Features CRYPTO Service Parameters
MD5 Authentication for Configuring Security Features OSPF Service Parameters
OSPF and BGP BGP Service Parameters
SSH Configuring Security Features Commands
CRYPTO Service Parameters
SYStem Service Parameters
SNMPv3 Configuring Network Management Commands (UserManage Command)
L2 Tunnel Connections Configuring L2Tunnel Connections L2T Service Parameters
Tunnel Route Shortcuts Configuring Tunnel Route Shortcut TRSC Service Parameters
(TRSC) Endpoints
Firewalls Configuring Internet Firewalls FireWall Service Parameters
LDAP Configuring the Lightweight Directory LDAP Service Parameters
Access Protocol (LDAP)
Other Protocols and Services
Network Management Configuring Network Management SNMP Service Parameters
Remote Polling (REMP) Configuring the Remote Polling Protocol REMPolling Service Parameters
VRRP Configuring the Virtual Router VRRP Service Parameters
Redundancy Protocol (VRRP)
Scheduling and Event- Configuring Scheduling and Event-Based SCH Service Parameters
Based Macro Execution Macro Execution
CCGW Functionality Configuring CCGW Functionality on CCGW Service Parameters
MNR S2500 Routers
O CT OB ER 28 , 2 01 3 4-19
APPENDIX
COMPLIANCE
A A
...................................
....
This appendix provides information about agency approvals and regulatory
compliance for MNR S2500 routers.
The information in this appendix is organized as follows:
EMC/EMI Requirements on page A-2
Product Safety Requirements on page A-4
FCC Part 15 Statement on page A-5
Telephony Requirements on page A-6
Canadian Notice on page A-8
Japanese Notice on page A-9
CE Notice on page A-10
EU WEEE Directive Compliance on page A-11
CMM Labeling and Disclosure on page A-12
O CT OB ER 28 , 2 01 3 A-1
EMC/EMI REQUIREMENTS APPENDIX A: COMPLIANCE
EMC/EMI REQUIREMENTS
...................................
..
The MNR S2500 meets the following EMI/EMC requirements:
North America
FCC Part 15 Class B
Industry Canada ICES-003 Class B
Europe (EU)
EN 55022: 2003 - Emissions
Radiated Emissions Class B
Conducted Emissions Class B
EN61000-3-2 Harmonics
EN 61000-3-3 Flicker
EN 55024: 2003 - Immunity
EN 61000-4-2 ESD Immunity
EN 61000-4-3 Radiated Immunity
EN 61000-4-4 EFT/B Immunity
EN 61000-4-5 Surge
EN 61000-4-6 Conducted Immunity
EN 61000-6-11 Voltage Interruption / Dips
Japan
VCCI Class B
Australia / New Zealand
AS/NZS CISPR 22 Class B
A-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE EMC/EMI REQUIREMENTS
CLASSES
Various national agencies (in the United States, The Federal Communications
Commission (FCC)) govern the levels of electromagnetic emissions from digital
devices. Electromagnetic emissions can interfere with radio and television
transmission. To reduce the risk of harmful interference, these agencies have
established requirements for manufacturers of digital devices.
The manufacturer of a digital device must test and label a product to inform end users
of the maximum emission level from the product when used in accordance with its
instructions. The emission levels encountered are classified as Class A or Class B. A
system that meets the Class A requirement can be marketed for use in an industrial or a
commercial area. A system that meets the more stringent Class B requirement can be
marketed for use in a residential area in addition to an industrial or a commercial area.
End users are generally held responsible for ensuring that their systems are suitable for
their environments as stated in the above paragraph and bear the financial
responsibility for correcting any harmful interference.
MODIFICATIONS
Modifications or changes made to this device, and not approved by Motorola, may
void the authority granted by the FCC, or other such agency, to operate this equipment.
SHIELDED CABLES
Connections between Motorola equipment and other equipment and peripherals must
be made using shielded cables in order to maintain compliance with FCC, and other
agency, electromagnetic frequency emissions limits.
O CT OB ER 28 , 2 01 3 A-3
PRODUCT SAFETY REQUIREMENTS APPENDIX A: COMPLIANCE
PRODUCT SAFETY REQUIREMENTS

...................................
..
The MNR S2500 meets the following product safety requirements:
North America
UL60950-1, 2002; Information Technology Equipment
CSA C22.2 No. 60950-1, Information Technology Equipment
Europe (EU)
EN 60950-1, 2002, Information Technology Equipment, General
Requirement
AS/NZS 60950-1, 2002; Information Technology Equipment
International Electrotechnical Commission
IEC 60950-1, 2002, Information Technology Equipment, General
Requirement
A-4 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE FCC PART 15 STATEMENT
FCC PART 15 STATEMENT

...................................
..
This equipment has been tested and found to comply with the limits for a Class B
digital device, pursuant to Part 15 of the FCC rules. These limits are designed to
provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment. This equipment generates, uses and can create
radio frequency energy and, if not installed and used in accordance with the instruction
manual, may cause harmful interference to radio communications. If this equipment
does cause harmful interference to radio or television reception, which can be
determined by turning the equipment off and on, the user is encouraged to try and
correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and the receiver.
Connect the equipment into an outlet on a circuit different from that to which the
receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
In order to meet FCC Class B limits, this equipment must be used only with cables
which comply with IEEE 802.3.
You may find the following booklet prepared by the Federal Communication
Commission to be helpful:
How to Identify and Resolve Radio-TV Interference Problems
This booklet is available from the U.S. Government Printing Office, Washington, DC
20402, Stock No. 004-000-00345-4.
O CT OB ER 28 , 2 01 3 A-5
TELEPHONY REQUIREMENTS APPENDIX A: COMPLIANCE
TELEPHONY REQUIREMENTS
...................................
..
The MNR S2500 meets the latest versions of the following telephony requirements:
North America
FCC Part 68
IC CS-03
Europe (EU)
ETSI/TBR1
TBR2
TBR12
TBR13
TBR 17
AS/ACIF S003
ACA TS016
TNA 117
FCC PART 68 STATEMENT

This equipment complies with 47 CFR, Part 68 of the Federal Communications
Commission (FCC) rules. On the bottom of the equipment is a label that contains,
among other information, the FCC registration number and ringer equivalence number
(REN) for this equipment. If requested, this information must be provided to the
telephone company.
This equipment is designed to be connected to the telephone network or premises
wiring using a telephone cord and a compatible modular jack that meet Part 68
requirements. For details about connecting the S2500 router, see the installation
instructions in Chapter 2.
If the MNR S2500 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 is not 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.
The telephone company may make changes in its facilities, equipment, operations or
procedures that could affect the operation of this equipment. If this happens the
telephone company will provide advance notice in order for you to make necessary
modifications to maintain uninterrupted service.
A-6 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE TELEPHONY REQUIREMENTS
If you experience trouble with the MNR S2500, for repairs or warranty information,
please contact the Solution Support Center (SSC), 1311 East Algonquin Road,
Schaumburg IL 60196 or call (800) 221-7144. Call SCC to confirm troubleshooting
results and analysis prior to repairing your system through FRU (field-replaceable
unit) removal/replacement. 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.
The MNR S2500 cannot be used on public coin phone service provided by the
telephone company. Connection to party line service is subject to state tariffs. (Contact
the state public utility commission, public service commission or corporation
commission for information.)
FCC Registration Number: See label on product
T1 ports:
Required Connector (USOC): RJ48C
Service Order Code (SOC): 6.0N
Facility Interface Codes (FIC): 04DU9-BN, 04DU9-DN, 04DU9-1KN, 04DU9-1SN
E&M (analog) ports:
Required Connector (USOC): RJ1CX
Service Order Code (SOC): 9.0F
Facility Interface Codes (FIC): 04LS2, 04GS2
CAUTION
The analog interface of the S2500 router used as a conventional
channel gateway (CCGW) is designed to connect directly to analog
stations that are physically located in the same room or building, or via
a connection provided by a microwave link. If analog lines are used to
connect the CCGW to an analog station at another location, a primary
surge suppression device must be installed.
O CT OB ER 28 , 2 01 3 A-7
CANADIAN NOTICE APPENDIX A: COMPLIANCE
CANADIAN NOTICE
...................................
..
The Industry Canada label identifies certified equipment. This certification means that
the equipment meets certain telecommunications network protective, operational, and
safety requirements. Industry Canada does not guarantee the equipment will operate
to the users satisfaction.
Before installing this equipment, users should ensure that it is permissible to be
connected to the facilities of the local telecommunications company. The equipment
must also be installed using an acceptable method of connection. In some cases, the
inside wiring associated with a single line individual service may be extended by
means of a certified connector assembly. 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 made by an authorized Canadian
maintenance facility designated by the supplier. Any repairs or alterations 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.
WARNING
Users should not attempt to make electrical ground connections by
themselves, but should contact the appropriate inspection authority or
an electrician, as appropriate.
A-8 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE JAPANESE NOTICE
JAPANESE NOTICE
...................................
..
The following label indicates that the MNR S2500 router is a Class B ITE device:
Translation: This is a Class B product. In a domestic environment this product may

cause radio interference, in which case the user may be required to take corrective
actions.
O CT OB ER 28 , 2 01 3 A-9
CE NOTICE APPENDIX A: COMPLIANCE
CE NOTICE
...................................
..
Marking by the following symbol indicates compliance of this equipment to applicable
essential requirements of the following Directives of the Council of the European
Communities on the approximation of the laws of the Member States:
1999/5/EC on Radio Equipment and Telecommunications Terminal Equipment
and the mutual recognition of their conformity.
56
Such marking is indicative that this equipment meets or exceeds the most recent
version of the following technical standards:
EN 55022 - Limits and Methods of Measurement of Radio Interference
Characteristics of Information Technology Equipment.
EN 55024 - Limits and Methods of Measurement of Immunity Characteristics of
Information Technology Equipment.
EN60950 - Safety of information technology equipment, including electrical
business equipment.
CTR 1 - Attachment requirements for terminal equipment to be connected to
circuit switched data networks and leased circuits using a CCITT
Recommendation X.21 interface, or at an interface physically, functionally and
electrically compatible with CCITT Recommendation X.21 but operating at any
data signalling rate up to, and including, 1 984 kbit/s
CTR 2 - Attachment requirements for Data Terminal Equipment (DTE) to connect
to Packet Switched Public Data Networks (PSPDNs) for CCITT Recommendation
X.25 interfaces at data signalling rates up to 1 920 kbit/s utilizing interfaces
derived from CCITT Recommendations X.21 and X.21 bis
CTR 12 - Open Network Provision (ONP) technical requirements; 2 048 kbit/s
digital unstructured leased line (D2048U) Attachment requirements for terminal
equipment
CTR 13 - 2048 kbit/s digital structured leased lines (D2048S); Attachment
requirements for terminal equipment interface
A Declaration of Conformity in accordance with the above standards has been
made and is on file at Motorola Inc.
A-10 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE EU WEEE DIRECTIVE COMPLIANCE
EU WEEE DIRECTIVE COMPLIANCE

...................................
..
The MNR S2500 router is compliant with the EU WEEE marking requirements
specified in the following document:
EN 50419:2005 (Marking of electrical and electronic equipment in accordance
with Article 11(2) of Directive 2002/96/EC (European Directive on Waste of
Electrical and Electronic Equipment (WEEE).
CARING FOR THE ENVIRONMENT BY RECYCLING

Marking by the following symbol indicates that the MNR S2500 router should not be
disposed of with household waste:
DISPOSAL OF YOUR ELECTRICAL ACCESSORIES

Please do not dispose of electrical accessories with your household waste. In some
countries or regions, collection systems have been set up to handle waste electrical and
electronic items. Please contact your regional authorities for more details. If no suitable
scheme exists, you may return unwanted electrical accessories to any Motorola
Approved Service Center in your region.
O CT OB ER 28 , 2 01 3 A-11
CMM LABELING AND DISCLOSURE APPENDIX A: COMPLIANCE
CMM LABELING AND DISCLOSURE

...................................
..
Marking by the following symbol indicates compliance of this electronic information
product (EIP) with China Management Methods (CMM) environmental regulations.
(China Management Methods refers to the regulation Management Methods for
Controlling Pollution by Electronic Information Products.)
Such marking is indicative that this equipment contains hazardous substances with an
Environmental Friendly Use Period of 50 (fifty) years. The EFUP is the period (in years)
during which the Toxic and Hazardous Substances (T&HS) contained in the EIP will
not leak or mutate, thereby causing environmental pollution or bodily injury from the
use of the EIP. The EFUP indicated by the marking shown above applies to the MNR
S2500 router and all its parts.
The following disclosure table is intended only to communicate compliance with China
requirements; it is not intended to communicate compliance with EU RoHS or any
other environmental requirements.
A-12 O C T OBE R 2 8, 20 1 3
APPENDIX
TECHNICAL SUPPORT
B B
...................................
....
The Solution Support Center (SSC) is your primary Motorola contact. Call SSC prior to
any software reload and to confirm troubleshooting results and analysis prior to
repairing your system through FRU (field-replaceable unit) removal/replacement.
For return authorization numbers and technical support, contact:
Motorola Solutions System Support Center
1311 East Algonquin Road
Schaumburg, IL 60196
800-221-7144 (Domestic)
302-444-9800 (International)
847-725-4073 (Fax)
O CT OB ER 28 , 2 01 3 B-1
APPENDIX
TROUBLESHOOTING
C C
...................................
....
This appendix provides troubleshooting procedures for MNR S2500 routers.
Using the S2500 Firmware Boot Monitor on page C-2
Normal LED Meanings on page C-9
Error LED Meanings on page C-15
Performing Loopback Tests on page C-21
Performing a Memory Dump on page C-27
O CT OB ER 28 , 2 01 3 C-1
USING THE S2500 FIRMWARE BOOT MONITOR APPENDIX C: TROUBLESHOOTING
USING THE S2500 FIRMWARE BOOT MONITOR

...................................
..
To enter the S2500 firmware boot monitor, follow Procedure C-1.
PROCEDURE C-1 ENTERING THE S2500 FIRMWARE BOOT MONITOR
1 Start up or reboot the S2500, and wait for a message similar to the following to appear:
Motorola Incorporated S2500
FW/S2500-BOOT2,2.0.0.01|
24 MB instruction/data memory, 6 MB shared memory
16 MB installed for drive A, Drive B not installed
Booting for bank A
Station Address is 0800024858D7 - 128 addresses allocated
POST ... passed
Would you like to enter the boot monitor (y/n):
2 Enter Y within five seconds to display the firmware boot monitor prompt (>).
CAUTION
The firmware boot monitor stops the software from running. To return to the EOS
software user interface you must reboot the router.
The following subsections describe the user mode commands available from the S2500
firmware boot monitor.
C-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE USING THE S2500 FIRMWARE BOOT MONITOR
BOOT MODE (BM)

SYNTAX
BM
DESCRIPTION
Use the BM command to specify the boot sequence after a boot failure occurs. The
following options are available:
1. Reboot
2. Scope loop/enter monitor
EXAMPLE
>bm
Boot mode - on self test/boot failure: Reboot
1. Reboot
2. Scope loop/enter monitor
Choose boot mode or press Q to quit (CR=Reboot):
BOOT (BT)
SYNTAX
BT
DESCRIPTION
Use the BT command to reboot or to override the default boot and configuration file
paths configured in the firmware by the boot monitor or by the SysconF command in
the software. This command is useful if the boot path has a typing error or if you have a
malfunctioning flash memory drive.
EXAMPLE
> bt
Enter the boot filename (CR=a:/primary/boot.ppc):
Enter the configuration path (CR=a:/primary):
O CT OB ER 28 , 2 01 3 C-3
CONFIGURE LOAD (CL)

SYNTAX
CL
DESCRIPTION
Use the CL command to configure the following settings to identify a TFTP server for
downloading or dumping memory:
1. Client IP Address
2. Server IP Address
3. Gateway IP Address
4. Subnet Mask
5. Image Filename
6. Number of Retries
7. Port Selection
8. Baud Rate
9. Duplex Mode
EXAMPLE
> cl
1. Client IP Address 10.79.139.21
2. Server IP Address 10.79.130.83
3. Gateway IP Address 10.79.139.1
4. Subnet Mask 255.255.255.0
5. Image Filename boot.ppc
6. Number of Retries 4
7. Port Selection LAN 1
8. Baud Rate Auto Baud
9. Duplex Mode Auto Duplex
C-4 O C T OBE R 2 8, 20 1 3
DISPLAY FILES (DF)

SYNTAX
DF [<subdir>]
DESCRIPTION
Use the DF command to display information about files on a file system or in a
specified directory. This command also displays the available free space in the file
system.
EXAMPLE
> df
Directory of a:/
PRIMARY<dir>07-15-200115:05
AUDLOG<dir>07-15-200112:35
TEST <dir>08-10-200114:51
3 file(s)
9105408 bytes free
FLASH LOAD (FL)

SYNTAX
FL <path/><filename>
DESCRIPTION
Use the FL command to format the flash memory and copy the boot image and SYS
files from the location identified by the CL command to the flash drive via TFTP.
CAUTION
The FL command will reformat the a: drive. Back up all configuration
files before issuing the FL command, or the contents of these files will
be lost during the reformatting operation.
O CT OB ER 28 , 2 01 3 C-5
Use Procedure C-2 to restore the router to factory defaults.
PROCEDURE C-2 RESTORING THE S2500 TO FACTORY DEFAULTS
1 Use the CL command to configure the parameters necessary to load an image file from a TFTP server.
2 Use the FL <image filename> command to retrieve a bootable EOS image.
3 Reboot the router using the image you obtained in step 2.
When you use the FL command to recover a system, the image is always written to
A:/primary/boot.ppc. If the system primary boot source config directory
parameters were set to boot from another area, the BT command will fail because it will
try to boot from the other area. In this case, use the following command to boot the
system:
bt a:/primary/boot.ppc
Then reset the boot pointers using the SysconF command menu Boot Sources option.
See Boot Sources in Appendix E, SysconF Command Menus for more information.
RECOVERY ACTION (RA)

SYNTAX
RA
DESCRIPTION
Use the RA command to configure the recovery action and memory dump parameters
that the system should use in the event of a crash. The following options are available:
1. Reboot with partial dump only
Automatically reboot and save the partial dump information.
2. Perform full dump and reboot
Upload the full dump contents to the server and reboot.
3. Halt system to monitor
Halt operation and enter the debug monitor.
EXAMPLE
> ra
C-6 O C T OBE R 2 8, 20 1 3
REBOOT (RB)
SYNTAX
RB
DESCRIPTION
Use the RB command to reboot the system.
SHOW SYSTEM INFORMATION (SI)

SYNTAX
SI
DESCRIPTION
Use the SI command to display information about the system, including processor
version and MCPU processor type, firmware and software versions, installed memory,
and installed I/O modules.
O CT OB ER 28 , 2 01 3 C-7
SET SELF TEST ACTION (ST)

SYNTAX
ST
DESCRIPTION
Use the ST command to specify the self-test action that is performed on startup. The
following options are available:
1. Quick
Perform a subset of the self-tests on startup.
2. Full
Perform a full set of self-tests on startup.
NOTE
If you select the Full option, startup takes significantly longer than if you
select the Quick option.
EXAMPLE
> st
Self-Test: Quick
1. Quick
2. Full
Choose a Self-Test Action on boot
or press Q to quit (CR=Quick): 2
HELP (H, ?)
SYNTAX
H or ?
DESCRIPTION
Use the H (or ?) command to list all available commands in the user mode of the
firmware boot monitor.
C-8 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE NORMAL LED MEANINGS
NORMAL LED MEANINGS

...................................
..
This section describes the normal operation of the S2500 LEDs.
SYSTEM LEDS
Figure C-1 describes the system LEDs.
FIGURE C-1 S2500 SYSTEM LEDS
Normal operation
SYSTEM Lights green when unit has power. Lights amber if there is
Run Power a problem with power. When unlit, power to unit is off.
Status Fwd /Fault
Load
Power
Test /Fault
Flashes green each time a packet is forwarded between
Fwd two ports.
Run Lights green when the software has successfully loaded and is running.
Load Unlit in normal operation. Flashes green during startup to indicate system is loading software. Lights
amber when there is a load problem.
Test Unlit in normal operation. Lights amber during startup to indicate system is running self-tests.
Status Provides additional status for the Run, Load, and Test LEDs.
O CT OB ER 28 , 2 01 3 C-9
NORMAL LED MEANINGS APPENDIX C: TROUBLESHOOTING
LAN (ETHERNET) LEDS

Figure C-2 describes the LAN LEDs for the Ethernet port on the S2500 base unit
(labeled LAN 1).
FIGURE C-2 S2500 LAN (ETHERNET) LEDS (LAN PORT 1 ON S2500 BASE UNIT)
100Mb Lights green when 100BASE-TX Ethernet is in use.

100Mb
LAN Link
Link Lights green when the path is up.
Active Active Flashes green when a packet is detected on the LAN.
Fault
1 Fault Lights amber when an error is detected or the self-test
has failed.
Normal operation
Figure C-2 describes the LAN LEDs for the Ethernet port on the optional 10BASE-T
module (labeled 3).
FIGURE C-3 S2500 LAN (ETHERNET) LEDS (OPTIONAL 10BASE-T MODULE)
Link Link Lights green when the path is up.

Transmit Transmit Flashes green when a packet is being transmitted on the LAN.
Receive
Collision Receive Flashes green when a packet is being received on the LAN.
I/O Module B 3 Collision Lights amber during system startup and initialization
or when a collision occurs in half duplex mode.
Normal operation
C-10 O C T OBE R 2 8, 20 1 3
FLEXWAN SERIAL LEDS

Figure C-4 describes the FlexWAN serial module LEDs.
FIGURE C-4 S2500 FLEXWAN SERIAL LEDS

Link
Lights green when there is a physical connection to a serial
Active Active
device such as a CSU/DSU or modem.
Fault
Unlit in normal operation. Lights amber if an error in the
Fault
frames is detected or if no cable is connected to the serial port.
Normal operation
O CT OB ER 28 , 2 01 3 C-11
WAN/TELCO (T1/E1 CSU/DSU) LEDS

Figure C-5 describes the WAN/Telco (T1/E1 CSU/DSU) module LEDs.
FIGURE C-5 S2500 WAN/TELCO (T1/E1 CSU/DSU) LEDS

Link
Active
Lights green when an end-to-end connection
Active exists or is in progress.
Fault
Fault Lights amber when an error in the frames is
detected.
Normal operation
WAN/TELCO (T1/E1 CSU/DSU) MODULE LED DEFINITIONS

Table C-1 lists the WAN/Telco (T1/E1 CSU/DSU) module LED definitions for MNR
S2500 routers.
TABLE C-1 S2500 WAN/TELCO (T1/E1 CSU/DSU) MODULE LED DEFINITIONS
Operational
Link Active Fault
State
Normal ON ON OFF
Operation
Loss of Signal OFF OFF ON
Link Failure OFF ON OFF

(no LOS)
Remote No Blinking No
Initiated Change Change
Loopback
Path or Port OFF OFF OFF

Disabled
C-12 O C T OBE R 2 8, 20 1 3
V.24 MODULE LEDS

The V.24 module features four port status LEDs, as illustrated in Figure C-6.
FIGURE C-6 S2500 V.24 MODULE LEDS
V.24
Port status L
Each LED indicates the status of one of the two V.24 (CCGW digital conventional) ports
as follows:
Steady Green The V.24 port is connected, the HDLC link is up, and the digital
channel corresponding to this port is enabled and idle.
Blinking Green The V.24 port is connected, the HDLC link is up, the digital
channel corresponding to this port is enabled, and audio packets are flowing.
NOTE
In order for the V.24 module port status LED to light green, the CCGW
service must be enabled and the site type must be configured as digital
from the LDAP server.
Yellow The CCGW service is enabled and the corresponding channel is
configured to use the V.24 port (it is a digital channel), but the V.24 port is not
connected.
Off The CCGW service is disabled or the corresponding channel is not
configured to use the V.24 port (it is an analog channel).
O CT OB ER 28 , 2 01 3 C-13
E&M MODULE LEDS

The E&M module features four port status LEDs, as illustrated in Figure C-7.
FIGURE C-7 S2500 E&M MODULE LEDS
S2500
Port SYSTEM
Status
Run
4 Console Fwd
5 Status Load
Power
6 Test /Fault
5 6 7 7
Analog
E&M Port Status LEDs
Each LED indicates the status of one of the four E&M ports as follows:
Steady Green The analog channel corresponding to this port is enabled and
idle.
Blinking Green The analog channel corresponding to this port is enabled, and
Yellow CCGW functionality is not enabled; the DSP is out of service; or a fault
has been detected on the analog channel corresponding to this port.
NOTE
When the S2500 boots up, the E&M port LEDs are yellow until the first
analog channel is configured. Once an analog channel is configured, the
E&M port LEDs are off and turn yellow if an enabled/active channel fails.
Off CCGW functionality is enabled, but the channel corresponding to this port
is disabled or is not configured to use an E&M port (for example, it is a V.24
digital channel).
C-14 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE ERROR LED MEANINGS
ERROR LED MEANINGS

...................................
..
This section describes the error modes of the S2500 LEDs.
TROUBLESHOOTING DURING THE LOAD PHASE

If the Load and Power/Fault LEDs in the System area light amber, a problem occurred
during the system software load phase. Compare your System LEDs with the following
examples and follow the instructions for troubleshooting.
FILE SYSTEM EMPTY
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: The file system is empty.

ACTION: Reload the software. For details, see Appendix E, SysconF Command
Menus.
READ-ONLY MEMORY CORRUPTION
Run
Status
Amber Load Fwd
Amber
Test
Power
/Fault
SYSTEM
MEANING: Possible read-only memory corruption; cannot seek file.

Menus.
O CT OB ER 28 , 2 01 3 C-15
ERROR LED MEANINGS APPENDIX C: TROUBLESHOOTING
SOFTWARE IMAGE FILE DELETED / BOOT SOURCE AND

IMAGE NAME MISMATCH
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: The software image file has been deleted or the boot source and image
names do not match.
ACTION: Follow these steps:
1. At the monitor prompt, enter:

DF <path>
The default path is:
DF /primary
The image is called boot.ppc.
2. If the image has been deleted, reload the software, as described in Appendix E,
SysconF Command Menus.
3. If the image has a different name or is in a different directory, boot from the image
using:
BT [<path>]<filename>
IMAGE FILE TOO LARGE
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: The image file is too large.
C-16 O C T OBE R 2 8, 20 1 3
ACTION: Check to see if the image file is larger than available memory. Turn the
power off and then on again to retry the system software load. If the load is
unsuccessful, contact your network supplier.
FILE READ OR DECOMPRESSION ERROR
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: There was an error either reading the image file or decompressing it.
Menus.
FILE CHECKSUM ERROR
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: File checksum error.

Menus.
O CT OB ER 28 , 2 01 3 C-17
UNSPECIFIED FATAL ERROR
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: Unspecified fatal error.

Menus.
UNABLE TO TRANSMIT BOOTP REQUEST
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: Unable to transmit BOOTP request.

ACTION: Check cable connections. The S2500 may not be connected correctly to the
Ethernet network.
C-18 O C T OBE R 2 8, 20 1 3
NO RESPONSE TO BOOTP REQUEST
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: No response to BOOTP request. The BOOTP server may not be present or
is incorrectly configured.
ACTION: Check Trivial File Transfer Protocol (TFTP)/BOOTP server configuration and
verify the media access control (MAC) address of the S2500. Turn the power off and
then on again to retry the system software load. If the load is unsuccessful, see
Appendix E, SysconF Command Menus. for information about how to reload the
system software.
NO RESPONSE TO ARP REQUEST
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: No response from the TFTP server to Address Resolution Protocol (ARP)
request. The TFTP server is not present or may be incorrectly configured.
ACTION: Check the TFTP server configuration and verify the MAC address of the
S2500. Power the router off and then on again to retry the system software load. If the
load is unsuccessful, contact the Solution Support Center (SSC) for assistance.
O CT OB ER 28 , 2 01 3 C-19
NO RESPONSE TO TFTP REQUEST
Run
Amber Load Fwd
Status
Amber
Test
Power
/Fault
SYSTEM
MEANING: No response to TFTP request. The TFTP server is not present, the incorrect
file was downloaded, or the file is incorrectly configured.
ACTION: Make sure the MAC address is initialized correctly. Power the router off and
then on again to retry the system software load. If the load is unsuccessful, contact the
Solution Support Center (SSC) for assistance.
TROUBLESHOOTING DURING THE TEST PHASE

When the software load is complete, the system begins the test phase. If the Test LED
lights amber, as illustrated below, a problem occurred during the system test phase.
Run
Green Load Fwd
Status
Amber
Amber Test
Power
/Fault
SYSTEM
MEANING: EEPROM checksum test failed.

ACTION: Contact the Solution Support Center (SSC).
C-20 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE PERFORMING LOOPBACK TESTS
ERRORS INDICATED BY THE SERIAL LEDS

If the Fault LED in the serial LED section of your S2500 lights amber, as illustrated
below, it means an error has been detected in a received frame.
Link
Active
Amber Fault
PERFORMING LOOPBACK TESTS

...................................
..
This section describes how to perform loopback diagnostic tests on MNR S2500 routers.
CONFIGURING A SERIAL LINE LOOPBACK

This section describes how to configure a serial interface for a loopback test. Figure C-8
shows the data flow in this test. A modem or CSU/DSU is required in this
configuration.
FIGURE C-8 SERIAL LOOPBACK TESTING
Link partner
S2500
Before running the serial loopback test, complete the following tasks:
Attach a console or Telnet to your S2500.
Place the modem or CSU/DSU in local loopback test mode. For information, see
the documentation that accompanies your modem or CSU/DSU.
Verify the path and port number of the serial port you are testing.
O CT OB ER 28 , 2 01 3 C-21
PERFORMING LOOPBACK TESTS APPENDIX C: TROUBLESHOOTING
To perform a loopback test on the serial port, follow Procedure C-3
PROCEDURE C-3 PERFORMING A LOOPBACK TEST ON THE SERIAL PORT
1 Set the line type to Leased using:

SETDefault !<path> -PATH LineType = Leased
2 If necessary, delete any virtual ports on the interface.
NOTE
You must delete all virtual ports on the interface before you set the POrt OWner to
LoopBack.
3 Set the owner of the serial port you are testing to LoopBack using:
SETDefault !<port> -PORT OWNer = LoopBack
4 Select the loopback test mode by entering:

DLTest TestMode LoopBack
5 Specify the number of seconds that the test should run using:
DLTest TestDuration <seconds>
If you do not enter a value, the test will run indefinitely. However, use caution when running the test
for a specified duration. The test ends abruptly as soon as the time duration expires, and a
discrepancy between the number of packets transmitted and the number received may result.
6 Start the serial loopback test by entering:

DLTest START
If the number of received packets equals or approximately equals the number of transmitted packets,
your serial line has passed the serial loopback test. If your serial line does not pass the test, verify that
your S2500 is cabled correctly and that the software is configured correctly.
You can also check the number of packets transmitted and the number of errors by entering:
DLTest STATistics
7 Stop the serial loopback test by entering:

DLTest Abort
8 Restore the owner of the wide area port you are testing from loopback to your protocol using:
SETDefault !<port> -PORT OWNer = PPP | FrameRelay | Auto
CAUTION
Failure to perform this step causes the port to remain in loopback mode, preventing
connectivity through the port. Performing diagnostics on the port will reveal only
that the port is down.
C-22 O C T OBE R 2 8, 20 1 3
CONFIGURING AN RX-TO-TX LOOPBACK

This section describes how to configure a receive-to-transmit (Rx-to-Tx) loopback test
on an MNR S2500 router. Figure C-9 illustrates the data flow in this test.
FIGURE C-9 RX-TO-TX LOOPBACK TESTING DATA FLOW
S2500 Link partner
Before running the Rx-to-Tx loopback test, attach a console or Telnet to the S2500.
To configure the Rx-to-Tx loopback test, follow Procedure C-4.
PROCEDURE C-4 PERFORMING AN RX-TO-TX LOOPBACK TEST
1 Disable all the paths on the interface using:

SETDefault !<path> -PAth ConnControl = Disable
2 Start a loopback test by entering one of the following commands:

To receive data from the network and loop back data to the network without performing any
framing or deframing, configure a remote line loopback using:
LPBCK !<path> -PAth RMLnLpbck
To receive data from the network, extract the payload from the frames, and then reframe the
payload and loop the data back to the network, configure a remote payload loopback using:
LPBCK !<path> -PAth RmPyldLpbck
The loopback is now enabled and will remain enabled until you explicitly end it.
3 To end a loopback in progress, use:

LPBCK !<path> -PAth STOP
4 Enable the path using:

SETDefault !<path> -PAth ConnControl = Enable
O CT OB ER 28 , 2 01 3 C-23
CONFIGURING A LOCAL LOOPBACK

This section describes how to configure a T1 link for a local line or payload loopback.
Figure C-10 illustrates the data flow in this test.
FIGURE C-10 LOCAL LOOPBACK TESTING DATA FLOW
S2500 Link partner
Before running the local loopback test, attach a console or Telnet to the S2500.
To configure the T1 interface for local loopback, follow Procedure C-5.
PROCEDURE C-5 PERFORMING A LOCAL LOOPBACK TEST


To start a local line loopback test, use:
LPBCK !<path> -PAth LclLnLpbck
To start a local payload loopback test, use:
LPBCK !<path> -PAth LclPyldLpbck


C-24 O C T OBE R 2 8, 20 1 3
CONFIGURING A RX-TO-TX LOOPBACK ON THE LINK

PARTNER
This section describes how to configure a T1 link to start a remote line or payload
loopback on the link partner. Figure C-11 illustrates the data flow in this test.
FIGURE C-11 LINE PARTNER REMOTE LOOPBACK TESTING DATA FLOW
S2500 Link partner
Before running the remote loopback test on the link partner, attach a console or Telnet
to the S2500.
To configure the T1 interface for a remote loopback test on the link partner, follow
Procedure C-6.
PROCEDURE C-6 PERFORMING A RX-TO-TX LOOPBACK TEST ON THE LINK PARTNER


To make the link partner receive data from the network and loop the data back to the network
without performing any framing or deframing, configure a remote line loopback on the link partner
using:
LPBCK !<path> -PAth RmANsiLn
To make the link partner receive data from the network, extract the payload from the frames, and
then reframe the payload and loop the data back to the network, configure a remote payload
loopback on the link partner using:
LPBCK !<path> -PAth RmANsiPyld


O CT OB ER 28 , 2 01 3 C-25
RESPONSES TO LOOPBACK ASSERTIONS

This section describes how the S2500 responds to various link partner loopback
assertions on the FlexWAN and WAN/Telco (T1/E1 CSU/DSU) interfaces.
RESPONSE TO LOCAL LOOPBACK ASSERTION

If the S2500 is connected to a DTE that asserts a local loopback signal on a FlexWAN
serial interface, the router displays:
Path x Detected DTE Loopback ON, switching to echo mode
The S2500 in echo mode transmits the received data back to the DTE.
When the signal is removed, the S2500 displays:
Path x Detected DTE Loopback OFF, switching to normal mode
RESPONSE TO LOOPBACK ASSERTIONS VIA INBOUND BOP AND MOP

MESSAGES
If the S2500 is connected to the T1 central office switch that supports BoP (bit-oriented
protocol) or MoP (message-oriented protocol) messaging, the central office switch can
send a loopback request via these messages to the S2500.
Upon receipt of such a loopback request message, the S2500 displays one of the
following messages, depending on the loopback requested:
Connector X - Engaging remote initiated line loopback
or
Connector X - Engaging remote initiated payload loopback
The S2500 then loops the received T1 data stream back to the transmit side, out to the
central office switch.
Upon receipt of a loopback terminate request message, the S2500 displays:
Connector X - Line Loopback Terminated
or
Connector X - Payload Loopback Terminated
The S2500 then terminates the loopback.
C-26 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE PERFORMING A MEMORY DUMP
PERFORMING A MEMORY DUMP

...................................
..
If a S2500 unexpectedly stops functioning, it performs a partial memory dump, unless
it is configured to perform a full dump. A memory dump provides a view of the
internal state of the system, which can help technical support personnel determine the
cause of the failure.
PERFORMING A FULL MEMORY DUMP

If you want the S2500 to perform a full dump to a TFTP server on the local Ethernet
network, you must have the following items available:
A TFTP server on the local Ethernet network
IP addresses and subnet masks of the S2500, the TFTP server and, possibly,
the gateway leading to the network segment where the TFTP server is
located
Authorization to write to the TFTP server
96 MB of available disk space on the TFTP server
The S2500 configured to dump to the TFTP server
The procedure for obtaining a memory dump involves setting up destination IP
addresses and files to hold the memory dump information. The S2500 uses the IP
addresses to transmit the memory dump in files across the network to a TFTP server.
NOTE
Notice to users with UNIX TFTP servers: Some UNIX TFTP servers do not
have the capability to create files if they do not exist, but can overwrite
existing files. Therefore, you must first create files with the expected dump
filenames on the UNIX TFTP server. The procedure for creating these files is
described in Creating Files for the Full Memory Dump on page C-30.
O CT OB ER 28 , 2 01 3 C-27
PERFORMING A MEMORY DUMP APPENDIX C: TROUBLESHOOTING
CONFIGURING THE DUMP DESTINATION

The Dump Destination parameter selects where the contents of S2500 memory are
stored in case of a crash.
To configure the dump destination, follow Procedure C-7.
PROCEDURE C-7 CONFIGURING THE DUMP DESTINATION
1 Connect to the S2500 through the Console port or through Telnet.
2 At the EnterpriseOS # prompt, enter:

SysconF
3 Select the Recovery Action Menu from the System Configuration menu.
4 From the Recovery Action menu, do one of the following:

Select Reboot with partial dump only to direct the system to perform a partial dump to the
FPROM. You do not have to complete the rest of this procedure.
Select Perform full dump and reboot to perform a full dump to the network. The Full Dump
Network Configuration menu appears:
4. Subnet Mask
5. Dump Destination
6. Port Selection
7. Baud Rate
8. Duplex Mode
5 Set the IP addresses for the client, server, gateway, and subnet mask.
5.1 Select Client IP Address and enter the IP address associated with the Ethernet port of the S2500.
5.2 Return to the Full Dump Network Configuration menu, select Server IP Address and enter the
IP address associated with the TFTP server.
5.3 Return to the Full Dump Network Configuration menu and, if necessary, select Gateway IP
Address and enter the IP address of the default gateway leading to the network on which the
TFTP server resides.
5.4 Return to the Full Dump Network Configuration menu, select Subnet Mask, and enter the
subnet mask associated with the IP network attached to the Ethernet port.
(Continued)
C-28 O C T OBE R 2 8, 20 1 3
PROCEDURE C-7 CONFIGURING THE DUMP DESTINATION (CONTINUED)
6 Configure the location on the TFTP server to which the dump file will go.
6.1 From the Full Dump Network Configuration menu, select Dump Destination.
The default destination is /dump.
6.2 Enter the target directory on the TFTP server.
Usually, the target directory is the default TFTP directory. For example, if the TFTP directory is
/home/TFTPdir, and the target directory configured on the S2500 is /dump, then the actual target
directory is /home/TFTPdir/dump. Make sure this directory exists on the TFTP server, as it will
not be created by the S2500 or the TFTP process when a TFTP transfer is initiated.
7 Type Q repeatedly to exit the System Configuration menus and return to the EnterpriseOS #
prompt.
OBTAINING THE MAC ADDRESS

Because the system creates several dump files named dmXXXXXX.<EXT> on the TFTP
server, where XXXXXX are the last six characters of the MAC address of the
motherboard of the S2500, you need to obtain the media access control (MAC) address
of the S2500. <EXT> can be .o0x, .d0x, or .pdm, depending on the type of file.
To display the MAC address of the S2500 motherboard:
At the Enterprise OS # prompt, enter:
SysInfo
Record the MAC address in the Host MAC Address entry. You will use this number in
the next procedure.
O CT OB ER 28 , 2 01 3 C-29
CREATING FILES FOR THE FULL MEMORY DUMP

Some UNIX TFTP servers do not have the capability to create files if they do not exist.
They can, however, overwrite an existing file. Therefore, if you are using a UNIX TFTP
server, you must first create a set of files with the expected full dump filenames on the
UNIX TFTP server.
Before beginning this procedure, make sure the TFTP server is running. On a UNIX
system, the ps command with appropriate arguments provides a listing of the current
processes. See the documentation pertaining to the IP stack on the TFTP server if you
have any problems.
To create the files for an S2500 motherboard full dump, follow Procedure C-8. If you
have any problems, see the UNIX system documentation.
PROCEDURE C-8 CREATING FULL DUMP FILES
1 On a UNIX TFTP server, create files with the names dmXXXXXX.o01 through dmXXXXXX.o06 and
dmXXXXXX.d01 through dmXXXXXX.d06, where XXXXXX are the last six characters of the MAC
address of the S2500 motherboard. The dmXXXXXX.o01 through dmXXXXXX.o06 files contain the
onboard memory contents, while the dmXXXXXX.d01 through dmXXXXXXd06 files contain the
DIMM memory contents.
For example, if the last six characters of the MAC address of the S2500 motherboard are 06BA6A,
enter:
touch dm06BA6A.o01
touch dm06BA6A.o02
touch dm06BA6A.o03
touch dm06BA6A.o04
touch dm06BA6A.o05
touch dm06BA6A.o06
touch dm06BA6A.d01
touch dm06BA6A.d02
touch dm06BA6A.d03
touch dm06BA6A.d04
touch dm06BA6A.d05
touch dm06BA6A.d06
The 06BA6A portions of these commands are for example purposes only. When you enter the commands,
substitute the last six characters of the MAC address of your S2500 motherboard.
2 Ensure that all users have permission to write to the target directory and filename. To determine this
on a UNIX system, enter:
ls -la
(Continued)
C-30 O C T OBE R 2 8, 20 1 3
PROCEDURE C-8 CREATING FULL DUMP FILES
3 To change write access permissions on a file or directory, enter:

chmod 666 dm06BA6A.o01
chmod 666 dm06BA6A.d01
NOTE
The 06BA6A portions of these commands are for example purposes only. When you enter
the commands, substitute the last six characters of the MAC address of your S2500
motherboard.
If a system crash occurs, the system performs a dump and outputs S2500 motherboard information to
these files.
VERIFYING THE TFTP PROCESS

To verify that a TFTP transfer can occur from the S2500 to the TFTP server, follow
Procedure C-9.
PROCEDURE C-9 VERIFYING THE TFTP PROCESS
1 From the S2500 console, obtain a listing of the files on the router to select one to transfer using:
df <directory>
2 If you are using a UNIX TFTP server, from the UNIX console create a zero byte file with the name of
the file you selected, and with the proper permissions, using:
touch <filename>
chmod 666 <filename>
3 From the S2500 console, transfer the selected file from the router to the TFTP server using:
COpy [<device>:]<src_filename> [<device>:][<dest_filename>]
For example, to copy a source file named system to destination /dump/ using the TFTP server at IP
address 139.88.132.192, enter:
COpy a:/primary/system 139.88.132.192:/dump/system
4 Verify that the file was transferred to the correct location on the TFTP server.
O CT OB ER 28 , 2 01 3 C-31
PERFORMING A PARTIAL MEMORY DUMP

By default, if the S2500 fails, the system performs a partial dump to available flash
memory. The partial dump information is written to a specific place in flash memory
and is then copied out of this place to one of three files when the system boots up the
next time. The following filenames are used to hold the partial dumps:
partial1.dmp
partial2.dmp
partial3.dmp
You can transfer these files from the router to some other storage location. If you do not
remove the files, they are overwritten with new partial dump files if an additional
system failure occurs.
If you select the Perform full dump and reboot option in the Recovery Action menu,
the information in the partial dump that is created as part of the full dump processing
is recorded in two places:
Before the system restarts, the partial dump information is transferred to the
TFTP server with the name dmXXXXXX.pdm, where XXXXXX are the last six
characters of the MAC address of the S2500 motherboard.
After the system restarts, the partial dump information is recorded on the local
flash in one of the three partial dump files: partial1.dmp, partial2.dmp, or
partial3.dmp.
C-32 O C T OBE R 2 8, 20 1 3
CREATING A FILE FOR THE PARTIAL MEMORY DUMP

Some UNIX TFTP servers do not have the capability to create files if they do not exist.
They can, however, overwrite an existing file. Therefore, if you are using a UNIX TFTP
server, you must first create a file with the expected partial dump filename on the
UNIX TFTP server.
Before beginning this procedure, make sure the TFTP server is running. On a UNIX
system, the ps command with appropriate arguments provides a listing of the current
processes. See the documentation pertaining to the IP stack on the TFTP server if you
have any problems.
To create the partial dump file, follow Procedure C-10. If you have any problems, see
the UNIX system documentation.
PROCEDURE C-10 CREATING A PARTIAL DUMP FILE
1 On a UNIX TFTP server, create a file with the name dmXXXXXX.pdm, where XXXXXX are the last six
characters of the MAC address of the motherboard of the S2500.
For example, if the last six characters of the MAC address of the S2500 are 06BA6A, enter:
touch dm06BA6A.pdm
2 Ensure that all users have permission to write to the target directory and filename. To determine this
on a UNIX system, enter:
ls -la
3 To change write access permissions on a file or directory, enter:

chmod 666 dm06BA6A.pdm
NOTE
The 06BA6A portion of this command is for example purposes only. When you enter the
command substitute the last six characters of the MAC address of your S2500.
If a system crash occurs, the system performs a partial dump and outputs an ASCII text file to the file
named dm06BA6A.pdm.
O CT OB ER 28 , 2 01 3 C-33
VERIFYING THE MEMORY DUMP PROCEDURE

To verify that the memory dump process works, simulate a failure of the S2500.
CAUTION
This process will interrupt normal system operation and thus should
be performed only at a time when an outage can be tolerated.
At the EnterpriseOS # prompt, enter:

su dm BBBBBBBB
The system responds with a display similar to the following:
PANIC Trap 18 (DATA TLB MISS)
pc=FE3DE2A0 lr=FE3DE288 srrl=00009072 dar=BBBBBBBB dsisr=000004BF
Stack traceback:
FE47E38C FE3DE2A0 FE3C6BC8 FE3B7A7C FE3B7A0C 00000000
Dumping memory to network ... Dumping to file - </dump/dm06BA6A.pdm>
Station Address - 0800022ACC97
Trying LAN L2 ... 100BaseTX connection detected.
tftp write of file </dump/dm06BA6A.pdm> to server 139.88.132.192
Beginning transfer148 ... done
Dumping to file - </dump/dm06BA6A.o01>
Trying LAN L2 ... 100BaseTX connection detected.
tftp write of file </dump/dm06BA6A.o01> to server 139.88.132.192
Beginning transfer23224 ... done
If you receive a similar display, your S2500 series router is configured correctly to
obtain a memory dump.
The display your system returns may be slightly different depending on the number
and names of the files required to dump the router information. The number of files
can vary because the system compresses the memory image as it writes the full dump
files. If you receive a totally different display, or if the TFTP dump fails, try these
procedures again.
C-34 O C T OBE R 2 8, 20 1 3
APPENDIX
RELOADING THE SYSTEM

D
SOFTWARE D
...................................
....
This appendix describes how to reload EOS system software if the boot image has been
accidentally deleted or corrupted or if the S2500 router is unable to boot.
System Software Reload Overview on page D-1
Reloading the Software on page D-2
Load Errors on page D-3
SYSTEM SOFTWARE RELOAD OVERVIEW

................................... ..
To reload the software, you must have the software installed on a TFTP server on the
LAN. You can optionally use a TFTP/(BootP) server with the TFTP server.
The loading procedure in this chapter:
Looks up the IP address of the server.
Transfers the boot.ppc and SYS files from the server.
Creates the a:/primary directory.
Places the image in the /primary directory.
O CT OB ER 28 , 2 01 3 D-1
RELOADING THE SOFTWARE APPENDIX D: RELOADING THE SYSTEM SOFTWARE
RELOADING THE SOFTWARE

...................................
..
You must have a console attached to your S2500 to reload the system software from the
backup CD-ROM. To reload the system software, follow Procedure D-1.
PROCEDURE D-1 RELOADING THE SYSTEM SOFTWARE
1 Reset the S2500 by powering the router off and on again.

If the boot image has been accidently deleted or corrupted, the S2500 should go into monitor mode,
which is indicated by an angle bracket prompt (>). Go on to the next step.
If the S2500 does not go into monitor mode, contact the Solution Support Center (SSC). You do not
need to complete the remaining steps.
2 If you are using a TFTP server, enter:

CL
The CL command allows you to configure the following settings:
1. Client
2. Server
3. Gateway
4. Subnet Mask
5. Boot Filename
6. Port Selection
7. Baud Rate
8. Duplex Mode
When you configure addressing using the CL command, you do not need to use a BootP server to
acquire addresses. If you do not use the CL command, a BootP server must be available on the local
LAN with an entry in its database for this device.
NOTE
If you are flash loading from a backup, add the names of any configuration files into the
SYS file.
3 If you are using a TFTP server with BootP, enter:

FL <path on the TFTP server/>SYS
If you are using a BootP server in addition to the TFTP server, enter:
FL
The FL uses TFTP to copy the image from the identified server to the flash memory.
NOTE
If you are using BootP instead of locally configured addressing in the CL command, you
must not include the filename.
(Continued)
D-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE LOAD ERRORS
PROCEDURE D-1 RELOADING THE SYSTEM SOFTWARE
4 When the flash load is complete, confirm that boot.ppc was copied onto the S2500 by entering:
DF /primary
If you do not see boot.ppc, or if there is no /primary directory, contact the Solution Support Center
(SSC).
5 To reboot the S2500, enter:

BT A:/primary/boot.ppc
LOAD ERRORS
...................................
..
During the software loading process, some hardware or software conditions can cause
the process to fail. For more information about load errors, see Error LED Meanings in
Appendix C, Troubleshooting.
O CT OB ER 28 , 2 01 3 D-3
APPENDIX
SYSCONF COMMAND MENUS

E E
...................................
....
The SysconF command displays a menu of configurable firmware parameters. This
appendix describes how to configure these parameters to customize the operation of
the S2500.
Using the SysconF Command on page E-1
S2500 SysconF Command Menus on page E-2
USING THE SYSCONF COMMAND

...................................
..
The basic operation of the SysconF command is as follows:
SYNTAX
SysconF [<number>]
MINIMUM PRIVILEGE
Root user with Network Manager privilege
DESCRIPTION
If you enter only SysconF, a menu of options similar to the following is displayed:
1. Upgrade Menu
2. Console Port
3. Self-Test
4. Primary Boot Source
5. Secondary Boot Source
6. Test Boot Source
7. Boot Sources
8. Recovery Action
9. Boot Statistics
O CT OB ER 28 , 2 01 3 E-1
S2500 SYSCONF COMMAND MENUS APPENDIX E: SYSCONF COMMAND MENUS
If you enter SysconF with the number of a menu option, only that specific menu item is
displayed. For example, if you enter SysconF 2, the Console Port menu item is
displayed.
You can also configure firmware parameters using the firmware boot monitor. The
advantage of using SysconF menu options is that you can configure the firmware while
the software is running. Using the firmware boot monitor halts the router software. For
details about using the firmware boot monitor, see Using the S2500 Firmware Boot
Monitor in Appendix C, Troubleshooting.
NOTE
You cannot use the SysconF command when you access the router using the
REMote command.
The following section describes the SysconF menu options.
S2500 SYSCONF COMMAND MENUS

...................................
..
This section describes the options available on the S2500 SysconF command menus.
NOTE
The Upgrade Menu option is obsolete. Management of firmware upgrades
is no longer necessary since firmware upgrades are performed
automatically when a device boots with an image (boot.ppc file) that
contains new firmware.
CONSOLE PORT
The Console Port option displays a menu that allows you to set the baud rate for the
console port:
1. 110 bps
2. 300 bps
3. 1200 bps
4. 2400 bps
5. 4800 bps
6. 9600 bps
7. 19200 bps
8. 38400 bps
Enter the number corresponding to the baud rate that you want to set. The default baud
rate is 9600 bps. Data bits are always set at 8 and parity at none.
E-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE S2500 SYSCONF COMMAND MENUS
SELF-TEST
The Self-Test option displays a menu that allows you to specify whether your system
runs all self-tests or a subset of the self tests when you turn the power on or reset:
1. Quick
The system runs a subset of self-tests when it reboots.
2. Full
The system runs all self-tests when it reboots.
Enter the number corresponding to the self-test action you want to specify. The default
is Full.
PRIMARY BOOT SOURCE AND SECONDARY BOOT

SOURCE
Both the Primary Boot Source and the Secondary Boot Source options display a menu
that allows you to specify paths to boot and configuration files and to configure the IP
address and FTP information necessary to retrieve these files. The Primary Boot Source
option configures this information for your primary boot source. The Secondary Boot
Source option configures this information for your secondary boot sourced alternative
boot source to be used if the primary boot source fails. Both of these options work in
conjunction with the Boot Sources option. For more information, see Boot Sources
on page E-6.
The following options are available from the Primary/Secondary Boot Source menu:
1. Boot Filename
Use the Boot Filename option to specify the boot filename. Enter the full
path:
/<directory>/<filename>
The default boot file is /primary/boot.ppc for Primary Boot Source and
/secondar/boot.ppc for Secondary Boot Source.
NOTE
Do not include a drive letter in the boot path.
2. Config File Source
Use the Config File Source option to specify the configuration file directory.
The default directory is /primary for Primary Boot Source and /secondar for
Secondary Boot Source.
O CT OB ER 28 , 2 01 3 E-3
3. IP Addresses
The IP Addresses option displays a menu that allows you to specify IP
addresses for the following:
1. Client
2. Server
3. Gateway
4. Remote File Server (not applicable)
5. Subnet Mask
The default setting for all IP addresses is none (no IP address configured).
To specify an IP address, enter the appropriate menu option (3 for Gateway,
for example), then enter an IP address, in dotted decimal notation, and press
<Return>.
To delete an IP address, enter the appropriate menu option (3 for Gateway,
for example), then enter 0.0.0.0 or press the space bar once and press
<Return>.
4. FTP login parameters
The FTP Login Parameters option displays a menu that allows you to set the
following FTP login options:
1. Username
2. Password
3. Account
Enter the number corresponding to the FTP parameter that you want to
configure (1 to configure the username, for example), then enter the
appropriate information. Each username, password, or account can be up to
20 characters long.
TEST BOOT SOURCE

The Test Boot Source option displays a menu that allows you to:
Specify the test boot source filename and default configuration file.
Initiate the system reboot directly from the test boot source menu.
Clear the test boot timer when the test boot succeeds.
E-4 O C T OBE R 2 8, 20 1 3
The Test Boot Source option provides the following options:

1. Boot Source
Use the Boot Source option to specify the test boot source filename. Enter
the full path:
/<directory>/<filename>
The default boot file is /primary/boot.ppc for Primary Boot Source and
/secondar/boot.ppc for Secondary Boot Source.
2. Config File Source
Use the Config File Source option to specify the configuration file directory.
The default directory is /primary for Primary Boot Source and /secondar for
Secondary Boot Source.
3. IP Addresses
The IP Addresses option displays a menu that allows you to specify IP
addresses for the following:
1. Client
2. Server
3. Gateway
4. Remote File Server (not applicable)
5. Subnet Mask
The default setting for all IP addresses is 0.0.0.0 (no IP address configured).
To specify an IP address, enter the appropriate menu option (3 for Gateway,
for example), then enter an IP address, in dotted decimal notation, and press
<Return>.
To delete an IP address, enter the appropriate menu option (3 for Gateway,
for example), then enter 0.0.0.0 or press the space bar once and press
<Return>.
4. FTP login parameters
The FTP Login Parameters option displays a menu that allows you to set the
following FTP login options:
1. Username
2. Password
3. Account
Enter the number corresponding to the FTP parameter that you want to
configure (1 to configure the username, for example), then enter the
appropriate information. Each username, password, or account can be up to
20 characters long.
O CT OB ER 28 , 2 01 3 E-5
5. Perform Test Boot

If you are upgrading software from a remote device, you must perform a
test boot of the new software to determine its reliability.
When you select the Perform Test Boot option, the following prompt is
displayed:
Enter number of seconds until automatic reboot after
test boot (CR = 0):
Enter the desired number of seconds. Motorola recommends entering 300
seconds, which should allow the system enough time to initialize.
After you enter the desired number of seconds, the following prompt is
displayed:
Press Y to test boot now (any other key to cancel):
Type Y to initiate the test boot.
If the test boot is successful, you can access the new software. If the test boot
fails, the router waits the number of seconds specified earlier, and then
attempts to reboot using the boot source specified by the Boot Sources
option.
6. Clear Test Boot Timer
Use the Clear Test Boot Timer option to clear the test boot timer if your test
boot succeeds and you do not want to reboot the system when the timer
runs down to 0. The system will continue to run the new software. If the
system reboots, however, it will go back to running the software specified by
the Boot Sources option.
BOOT SOURCES
The Boot Sources option displays a menu that allows you to select which boot source
you want the system to use:
1. Primary
The system will boot from the primary boot source only.
2. Primary and Secondary
The system will boot from the primary boot source first. If this fails, it will
boot from the secondary boot source
3. Secondary
The system will boot from the secondary boot source only.
The default is Primary. For more information on primary and secondary boot source
options, see Primary Boot Source and Secondary Boot Source on page E-3.
E-6 O C T OBE R 2 8, 20 1 3
RECOVERY ACTION
The Recovery Action option displays a menu that allows you to specify the action you
want the system to take upon crash recovery:
1. Reboot with partial dump only
Before rebooting, the system performs a partial memory dump.
2. Perform full dump and reboot
Before rebooting, the system performs a full memory dump to the location
and directory you specify , over the port and at the baud rate and duplex
mode you specify using the following options:
4. Subnet Mask
5. Dump Destination
6. Port Selection
7. Baud Rate
8. Duplex Mode
3. Halt system to debug monitor
The system takes you to the firmware boot monitor. For details about this
utility, see Using the S2500 Firmware Boot Monitor in Appendix C,
Troubleshooting.
BOOT STATISTICS
The Boot Statistics option displays the following information:
Boots Number of boots, including the date and time of last successful boot
Exceptions Number of exceptions (unsuccessful boots), including date and
time of last exception.
Boot source used for last successful boot
Last error during boot attempt
To clear the boot statistics, enter Y.
NOTE
The counters reported in the Boot Statistics (SysconF 9) output wrap at
about 32000. On systems where boot statistics are not tracked for extended
periods of time or circumstances cause the device to reboot rapidly, the boot
counters can wrap and report negative values. These circumstances are not
expected to be seen in deployed systems; however, if precise boot counts are
critical for your system, Motorola suggests that you:
Monitor the boot counts at an interval that allows you to detect when the
counts reach about 1000.
Record the boot counts in an external tracking system.
Clear the boot statistics after you have recorded them.
O CT OB ER 28 , 2 01 3 E-7
APPENDIX
INSTALLING TAMPER EVIDENCE

F
LABELS F
...................................
....
When the MNR S2500 is configured for use in a secure environment, the device must be
equipped with tamper evidence labels (part number TYN4008A). This appendix
describes how to apply tamper evidence labels on the MNR S2500 to meet Common
Criteria requirements, and how to remove tamper evidence labels from the power
receptacle prior to connecting power to the unit.
Securing the MNR S2500 with Tamper Evidence Labels on page F-2
Removing the Tamper Evidence Labels from the Power Receptacle on page
F-4
O CT OB ER 28 , 2 01 3 F-1
SECURING THE MNR S2500 WITH TAMPER EVIDENCE LABELS APPENDIX F: INSTALLING TAMPER EVIDENCE LABELS
SECURING THE MNR S2500 WITH

TAMPER EVIDENCE LABELS
...................................
..
Follow Procedure F-1 to install tamper evidence labels on the MNR S2500.
IMPORTANT
The surface to which the labels will be attached must be at a temperature of
at least +10C (+50F), and the surface must be clean and dry. Clean any
grease, dirt, oil, or adhesive residue from the areas to which the labels are to
be attached before applying the tamper evidence labels.
(Con
PROCEDURE F-1 HOW TO SECURE THE MNR S2500 WITH TAMPER EVIDENCE LABELS
1 Wipe the surface clean with isopropyl alcohol (99% concentration) to remove surface contaminants.
Please note that using a solution with an isopropyl alcohol concentration less than 99% is not
acceptable.
2 Do not allow excess alcohol to air dry. Use a clean paper towel or cotton cloth to completely remove
any excess alcohol, thereby removing any residual contaminants.
3 Apply tamper evidence labels 1 and 2 to secure the front of the MNR S2500 chassis.
3.1 Remove the Kraft liners from the backs of the labels and attach the labels positioned as
illustrated in Figure F-1:
Starting from the short edge of the label that is positioned towards the front of the unit, affix
each label by applying pressure while pushing the label across the top cover.
3.2 Rub the labels on the top of the chassis for 2 seconds to ensure that the labels have adhered.
FIGURE F-1 APPLYING TAMPER EVIDENCE LABELS 1 AND 2 TO SECURE THE FRONT OF THE MNR S2500
Label 2 Locate labels 1 and 2 approximately

where shown; apply labels on top of cover
Label 1
(Continued)
F-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE SECURING THE MNR S2500 WITH TAMPER EVIDENCE LABELS
PROCEDURE F-1 HOW TO SECURE THE MNR S2500 WITH TAMPER EVIDENCE LABELS (CONTINUED)
4 Apply tamper evidence labels 3 and4 to secure the rear of the MNR S2500 chassis.
4.1 Remove the Kraft liners from the backs of the labels and position the labels as illustrated in
Figure F-2.
Position the label with the perforation between the T and the O aligned with the edge of the
top cover. Starting from the short edge of the label that is positioned on the rear panel, affix each
label by applying pressure while pushing the label up the rear panel and onto the top cover.
4.2 Rub the labels on the top and rear of the chassis for 2 seconds to ensure that the labels have
adhered.
FIGURE F-2 APPLYING TAMPER EVIDENCE LABELS 3 AND 4 TO SECURE THE REAR OF THE MNR S2500
Locate labels 3 and 4 approximately where shown.

If the labels are applied correctly, the perforation
of each label between the "T" and the "O" aligns
with the edge of the top cover
Label 4
Label 3
5 Secure the unit in a restricted area. Allow the applied labels to cure for at least 4 hours; do not touch
the labels during this time.
6 If you need to re-apply the tamper evidence labels to the MNR S2500, repeat steps 1-5.
O CT OB ER 28 , 2 01 3 F-3
REMOVING THE TAMPER EVIDENCE LABELS FROM THE POWER RECEPTACLE APPENDIX F: INSTALLING TAMPER EVIDENCE LABELS
REMOVING THE TAMPER EVIDENCE LABELS

FROM THE POWER RECEPTACLE
...................................
..
IMPORTANT
You must follow the instructions below to remove the tamper evidence
labels from the power receptacle on the rear of the MNR S2500 router prior
to connecting power to the unit.
Follow this step to remove the tamper evidence labels from the AC power receptacle on the rear of
the MNR S2500 prior to connecting power to the unit.
1. Remove the tamper evidence labels covering the AC power receptacle on the rear
of the MNR S2500.
IMPORTANT
Do not remove the tamper evidence label securing the power supply module itself
(wrapped over the top cover of the chassis on the rear of the MNR S2500.
F-4 O C T OBE R 2 8, 20 1 3
APPENDIX
COPYING FILES TO AND FROM A

G
TFTP OR FTP SERVER G
...................................
....
This appendix describes how to copy files between the MNR S2500 and a TFTP or FTP
server.
Copying Files between an MNR S2500 and a TFTP Server on page G-2
Copying Files between an MNR S2500 and an FTP Server on page G-3
Troubleshooting TFTP/FTP File Transfer Issues on page G-5
O CT OB ER 28 , 2 01 3 G-1
COPYING FILES BETWEEN AN MNR S2500 AND A TFTP SERVER APPENDIX G: COPYING FILES TO AND FROM A TFTP OR FTP SERVER
COPYING FILES BETWEEN AN MNR S2500

AND A TFTP SERVER
...................................
..
To copy files between an MNR S2500 and a TFTP server, follow Procedure G-1.
PROCEDURE G-1 HOW TO COPY FILES BETWEEN AN MNR S2500 AND A TFTP SERVER
1 Connect a straight-through Ethernet cable between port 1 of the MNR S2500 and a hub or switch port
that is in the same subnet as the TFTP server.
2 From the MNR S2500 command line, enter the following commands to configure the MNR S2500 to
access the TFTP server:
SETDefault !1 -IP NETaddr = <IP address> [<network mask>]
where <IP address> is the IP address you want to assign to port 1 and <network mask> is the
subnet mask.
SETDefault !1 -PAth CONTrol = Enable
SETDefault !1 -POrt CONTrol = Enable
ADD -IP ROUte <IP address> <mask> <gateway> <metric>
where <IP address> is the subnet address for the TFTP server, <mask> is the subnet mask,
<gateway> is the gateway IP address, and <metric> represents the number of hops required for a
packet to reach its destination.
For example:
ADD -IP ROUte 10.79.0.0 255.255.0.0 10.79.130.1 0
3 Copy the desired files between the MNR S2500 and the TFTP server.
NOTE
For the purposes of this procedure, assume that the TFTP server is configured to access
files on a Windows PC from the location c:\data\tftp
To copy a file from the TFTP server to the MNR S2500, use the following syntax:
copy <TFTP server IP address>:<filename> <MNR S2500 directory>/<filename>
For example, to copy the file c:\data\tftp\boot.txt from TFTP server with IP address 10.79.130.4 to
the a:/primary directory on the MNR S2500, enter:
copy 10.79.130.4:boot.txt a:/primary/boot.txt
To copy a file from the MNR S2500 to the TFTP server, use the following syntax:
copy <MNR S2500 directory>/<filename> <TFTP server IP address>:<filename>
For example, to copy the file boot.txt from the a:/primary directory on the MNR S2500 to the TFTP
server with IP address 10.79.130.4, enter:
copy a:/primary/boot.txt 10.79.130.4:boot.txt
G-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE COPYING FILES BETWEEN AN MNR S2500 AND AN FTP SERVER
COPYING FILES BETWEEN AN MNR S2500

AND AN FTP SERVER
...................................
..
To copy files between an MNR S2500 and an FTP server, follow Procedure G-2.
PROCEDURE G-2 HOW TO COPY FILES BETWEEN AN MNR S2500 AND AN FTP SERVER
1 If you have not already done so, use the SysconF menus to configure the MNR S2500 with a user
name and password for logging in to the FTP server. See Configuring FTP Login Parameters on
page G-4 for step-by-step instructions.
2 Connect a straight-through Ethernet cable between port 1 of the MNR S2500 router and a hub or
switch port that is in the same subnet as the FTP server.
3 From the MNR S2500 command line, enter the following commands to configure the
MNR S2500 to access the FTP server:
SETDefault !1 -IP NETaddr = <IP address> [<network mask>]
where <IP address> is the IP address you want to assign to port 1 and <network mask> is the
subnet mask.
ADD -IP ROUte <IP address> <mask> <gateway> <metric>
where <IP address> is the subnet address for the FTP server, <mask> is the subnet mask,
<gateway> is the gateway IP address, and <metric> represents the number of hops required for a
packet to reach its destination.
For example:
ADD -IP ROUte 10.79.0.0 255.255.0.0 10.79.130.1 0
4 Copy the desired files between the MNR S2500 and the FTP server.
NOTE
For the purposes of this procedure, assume that the FTP server is configured to access files
on a Windows PC from the location c:\data\ftp
To copy a file from the FTP server to the MNR S2500, use the following syntax:
get <FTP server IP address>:<filename> <MNR S2500 directory>/<filename>
For example, to copy the file c:\data\ftp\boot.txt from FTP server with IP address 10.79.130.3 to the
a:/primary directory on the MNR S2500, enter:
get 10.79.130.3:boot.txt a:/primary/boot.txt
To copy a file from the MNR S2500 to the FTP server, use the following syntax:
put <MNR S2500 directory>/<filename> <FTP server IP address>:<filename>
For example, to copy the file boot.txt from the a:/primary directory on the MNR S2500 to the FTP
server with IP address 10.79.130.3, enter:
put a:/primary/boot.txt 10.79.130.3:boot.txt
O CT OB ER 28 , 2 01 3 G-3
COPYING FILES BETWEEN AN MNR S2500 AND AN FTP SERVER APPENDIX G: COPYING FILES TO AND FROM A TFTP OR FTP SERVER
CONFIGURING FTP LOGIN PARAMETERS

Follow Procedure G-3 to set up a user name and password on the MNR S2500 so you
can log in from the MNR S2500 to an FTP server.
PROCEDURE G-3 HOW TO CONFIGURE FTP LOGIN PARAMETERS ON AN MNRS2500
1 From the MNR S2500 command line, enter the following command:
SysconF 4
Result: The Primary Boot Source: menu is displayed.
2 Enter 4 to select the FTP login parameters option:

Result: The File access protocol: FTP login parameters menu is displayed.
3 Enter 1 to select the Username option:

Result: The system displays the currently-configured user name (if any) and prompts you to:
Enter Username for FTP login parameter (CR=no change):
4 Enter the user name you want to use to log in to the FTP server.
5 Enter 2 to select the Password option:

Result: The system displays hash marks representing the currently-configured password and
prompts you to:
Enter Password for FTP login parameter (CR=no change):
6 Enter the password you want to use to log in to the FTP server.
7 Press <Enter> twice to exit from the SysconF menus.
G-4 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE TROUBLESHOOTING TFTP/FTP FILE TRANSFER ISSUES
TROUBLESHOOTING TFTP/FTP FILE

TRANSFER ISSUES
...................................
..
Refer to Table G-1 for troubleshooting strategies in the event that a file transfer to or
from an MNR S2500 and a TFTP or FTP server fails.
TABLE G-1 TROUBLESHOOTING MNR S2500 TO TFTP/FTP SERVER FILE TRANSFERS
Possible Causes for File Transfer Failure Solutions
Some TFTP or FTP servers do not allow files that Check to see if a file by the same name already exists
already exist on the server to be overwritten. on the TFTP or FTP server. If so, back up the existing
file (if necessary), then delete the existing file before
attempting the file transfer.
Firewalls on TFTP or FTP servers may block file Disable any firewalls running on the TFTP or FTP
transfers to the server. server and attempt the file transfer again.
O CT OB ER 28 , 2 01 3 G-5
INDEX
. . . . . . . . . . . . . . . . . . . . . . .N.UMERICS
...........................
100BASE-TX interfaces . . . . . . . . . . . . . . . . . . . . . .1-7 10BASE-T module
10BASE-T interfaces . . . . . . . . . . . . . . . . . . . . . . . .1-7 installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5
. . . . . . . . . . . . . . . . . . . . . . . . . A. . . . . . . . . . . . . . . . . . . . . . . . . .
access, restricting. . . . . . . . . . . . . . . . . . . . . . . . . .3-17 analog interfaces
administrative tasks . . . . . . . . . . . . . . . . . . . . . . . 3-11 connector pinouts . . . . . . . . . . . . . . . . . . . . . .2-57
agency approvals. . . . . . . . . . . . . . . . . . . . . . . . . . A-1 angle brackets, meaning in CLI . . . . . . . . . . . . . . . .3-7
analog connectors
pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-57
. . . . . . . . . . . . . . . . . . . . . . . . . B. . . . . . . . . . . . . . . . . . . . . . . . . .
bar, meaning in CLI. . . . . . . . . . . . . . . . . . . . . . . . .3-7 Boot (BT) command, firmware boot monitor . . . . C-3
baud rate Boot Mode (BM) command, firmware boot monitorC-3
changing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14 boot path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
console port boot sources, specifying primary and secondary . E-3
configuring . . . . . . . . . . . . . . . . . . . . . . . .3-14 Boot Sources, SysconF menu option . . . . . . . . . . . E-6
default . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14 Boot Statistics, SysconF menu option . . . . . . . . . . E-7
Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7 braces, meaning in CLI . . . . . . . . . . . . . . . . . . . . . .3-7
FlexWAN serial. . . . . . . . . . . . . . . . . . . . . . . .4-10
. . . . . . . . . . . . . . . . . . . . . . . . . C. . . . . . . . . . . . . . . . . . . . . . . . . .
cables X.21 DCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-45
100BASE-TX X.21 DTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-44
emissions classes . . . . . . . . . . . . . . . . . . .2-31 cabling
types . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-31 E&M (analog) connectors . . . . . . . . . . . . . . . .2-57
10BASE-T Ethernet (LAN) connectors . . . . . . . . . . . . . . .2-29
emissions classes . . . . . . . . . . . . . . . . . . .2-30 FlexWAN serial connectors. . . . . . . . . . . . . . .2-36
standards . . . . . . . . . . . . . . . . . . . . . . . . .2-31 power connector . . . . . . . . . . . . . . . . . . . . . . .2-27
types . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-30 V.24 connectors . . . . . . . . . . . . . . . . . . . . . . . .2-50
EIA-530 DTE . . . . . . . . . . . . . . . . . . . . . . . . . .2-48 WAN/Telco connectors . . . . . . . . . . . . . . . . . .2-49
Fast Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . .2-35 CCGW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
FlexWAN serial. . . . . . . . . . . . . . . . . . . . . . . .2-39 requirements . . . . . . . . . . . . . . . . . . . . . . . . . .1-11
required for installation . . . . . . . . . . . . . . . . . .2-3 supported channel types. . . . . . . . . . . . . . . . .1-11
RS-232 DCE. . . . . . . . . . . . . . . . . . . . . . . . . . .2-41 supported features
RS-232 DTE . . . . . . . . . . . . . . . . . . . . . . . . . . .2-40 IV&D . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-13
RS-449 DCE. . . . . . . . . . . . . . . . . . . . . . . . . . .2-47 theory of operation . . . . . . . . . . . . . . . . . . . . .1-12
RS-449 DTE . . . . . . . . . . . . . . . . . . . . . . . . . . .2-46 CE notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10
V.35 DCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-43 channel types, supported for CCGW. . . . . . . . . . .1-11
V.35 DTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-42 China Management Methods (CMM) . . . . . . . . . A-12
O CT OB ER 28 , 2 01 3 IX-1
INDEX MNR S2500 HARDWARE USER GUIDE
clock source electromagnetic compatibility information . . . A-2

setting for V.24 ports . . . . . . . . . . . . . . . . . . . 2-56 EU WEEE Directive . . . . . . . . . . . . . . . . . . . . A-11
CMM labeling and disclosure . . . . . . . . . . . . . . . A-12 FCC notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
collision domain diameter (Fast Ethernet) . . . . . . 2-32 FCC Part 68 statement . . . . . . . . . . . . . . . . . . . A-6
command line interface (CLI) Japanese notice. . . . . . . . . . . . . . . . . . . . . . . . . A-9
basic elements . . . . . . . . . . . . . . . . . . . . . . . . . 3-6 components, system . . . . . . . . . . . . . . . . . . . . . . . . 1-3
commands Configure Load (CL) command,
entering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-8 firmware boot monitor . . . . . . . . . . . . . . . . . . . . . . C-4
firmware boot monitor connectors
Boot (BT) . . . . . . . . . . . . . . . . . . . . . . . . . . C-3 Ethernet (LAN) . . . . . . . . . . . . . . . . . . . . . . . 2-29
Boot Mode (BM) . . . . . . . . . . . . . . . . . . . . C-3 FlexWAN serial . . . . . . . . . . . . . . . . . . . . . . . 2-39
Configure Load (CL) . . . . . . . . . . . . . . . . . C-4 serial port types . . . . . . . . . . . . . . . . . . . . . . . 4-11
Display Files (DF) . . . . . . . . . . . . . . . . . . . C-5 console port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Flash Load (FL) . . . . . . . . . . . . . . . . . . . . . C-5 baud rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Help (H, ?) . . . . . . . . . . . . . . . . . . . . . . . . . C-8 configuration settings . . . . . . . . . . . . . . . . . . 2-63
Reboot (RB) . . . . . . . . . . . . . . . . . . . . . . . . C-7 connecting . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-63
Recovery Action (RA) . . . . . . . . . . . . . . . . C-6 Console Port, SysconF menu option . . . . . . . . . . . . E-2
Set Self Test Action (ST). . . . . . . . . . . . . . . C-8 contact person, assigning for system . . . . . . . . . . 3-17
Show System Information (SI). . . . . . . . . . C-7 conventional-to-IP (E&M) interfaces . . . . . . . . . . . 1-8
MEnu . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9, 3-10 conventional-to-IP interface kit
SysconF . . . . . . . . . . . . . . . . . . . . . . . . . 3-14, C-3 connecting . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
SysPassWord . . . . . . . . . . . . . . . . . . . . . . . . . 3-13 connector pinouts . . . . . . . . . . . . . . . . . . . . . 2-57
compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XXII
Canadian notice . . . . . . . . . . . . . . . . . . . . . . . . A-8 notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . XXII
CE notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10 text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .XXIII
CMM logo . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12 crash recovery, specifying router action upon . . . . E-7
. . . . . . . . . . . . . . . . . . . . . . . . . D. . . . . . . . . . . . . . . . . . . . . . . . . .
data link connection identifiers. See DLCIs dial-up services, supported . . . . . . . . . . . . . . . . . . 1-9
data transfer rates, supported . . . . . . . . . . . . . . . . 1-9 Display Files (DF) command,
date, setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16 firmware boot monitor . . . . . . . . . . . . . . . . . . . . . . C-5
Daylight Saving Time, configuring for . . . . . . . . . 3-16 DLCIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
dial pool, dynamic paths . . . . . . . . . . . . . . . . . . . . 4-3 duplex, Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
dial-up lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9 dynamic paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
with PPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
. . . . . . . . . . . . . . . . . . . . . . . . . E. . . . . . . . . . . . . . . . . . . . . . . . . .
E&M (analog) connectors E&M cabling
cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57 to base station . . . . . . . . . . . . . . . . . . . . . . . . 2-58
E&M (analog) interfaces E&M connectors
configuring . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16 pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-57
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14 E&M interfaces
E&M (analog) LEDS . . . . . . . . . . . . . . . . . . . . . . . . 3-4 connector pinouts . . . . . . . . . . . . . . . . . . . . . 2-57
IX-2 O C T OBE R 2 8, 20 1 3
MNR S2500 HARDWARE USER GUIDE INDEX
E1/FE1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9 equipment, required for installation . . . . . . . . . . . .2-3

configuring WAN/Telco interface. . . . . . . . . .4-12 Ethernet (LAN) interfaces . . . . . . . . . . . . . . . . . . . .1-7
EIA-530 DTE cable pinouts . . . . . . . . . . . . . . . . . .2-48 baud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7
electromagnetic compatibility information . . . . . . A-2 configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7
ellipsis, meaning in CLI. . . . . . . . . . . . . . . . . . . . . .3-8 duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7
encryption module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3, C-10
installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-16 path/port syntax . . . . . . . . . . . . . . . . . . . . . . . .4-6
replacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-20 Ethernet connectors . . . . . . . . . . . . . . . . . . . . . . . .2-29
Enterprise OS Software Reference Guide . . . . . . . . . . . XXI cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-29
Enterprise OS Software User Guide . . . . . . . . . . . . . . XXI EU WEEE Directive compliance . . . . . . . . . . . . . A-11
environmental requirements . . . . . . . . . . . . . . . . . .2-2 exclamation point, meaning in CLI . . . . . . . . . . . . .3-8
. . . . . . . . . . . . . . . . . . . . . . . . . F. . . . . . . . . . . . . . . . . . . . . . . . . .
Fast Ethernet FlexWAN serial interfaces . . . . . . . . . . . . . . . . . . . .1-7
collision domain diameter . . . . . . . . . . . . . . .2-32 baud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10
creating network . . . . . . . . . . . . . . . . . . . . . . .2-32 cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-39
interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-31 configuring with DCEs . . . . . . . . . . . . . . . . . . .4-9
maximum cable lengths . . . . . . . . . . . . . . . . .2-35 configuring with DTEs . . . . . . . . . . . . . . . . . .4-11
FCC notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 connector types . . . . . . . . . . . . . . . . . . . . . . . .4-11
FCC Part 68 statement . . . . . . . . . . . . . . . . . . . . . . A-6 connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-39
firmware boot monitor . . . . . . . . .C-16, D-2, E-2, E-7 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3, C-11
accessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2 path/port syntax . . . . . . . . . . . . . . . . . . . . . . . .4-6
how to use. . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2 fractional E1. See E1/FE1
Flash Load (FL) command, firmware boot monitorC-5 fractional T1. See T1/FT1
FlexWAN module FRF.17 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-13
installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5 front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
FlexWAN serial connectors . . . . . . . . . . . . . . . . . .2-39 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-36
. . . . . . . . . . . . . . . . . . . . . . . . . G. . . . . . . . . . . . . . . . . . . . . . . . . .
grounding (earthing) . . . . . . . . . . . . . . . . . . . . . . .2-28 grounding (earthing) screw . . . . . . . . . . . . . . . . . . .1-6
. . . . . . . . . . . . . . . . . . . . . . . . . H. . . . . . . . . . . . . . . . . . . . . . . . . .
hardware interrupt button . . . . . . . . . . . . . . . . . . .1-3 Help (H, ?) command, firmware boot monitor . . . C-8
hardware overview . . . . . . . . . . . . . . . . . . . . . . . . .1-1 hyphen, meaning in CLI . . . . . . . . . . . . . . . . . . . . .3-7
. . . . . . . . . . . . . . . . . . . . . . . . . .I . . . . . . . . . . . . . . . . . . . . . . . . .
I/O slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6 site requirements. . . . . . . . . . . . . . . . . . . . . . . .2-2
installation stacking with brackets. . . . . . . . . . . . . . . . . . .2-25
in a rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26
on tabletop . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24
optional I/O modules . . . . . . . . . . . . . . . . . . . .2-5
O CT OB ER 28 , 2 01 3 IX-3
interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2, 1-3 supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

100BASE-TX. . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 V.24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8
10BASE-T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
conventional-to-IP (E&M) . . . . . . . . . . . . . . . . 1-8 path/port syntax . . . . . . . . . . . . . . . . . . . . 4-6
E&M (analog) WAN/Telco . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12
Ethernet (LAN) . . . . . . . . . . . . . . . . . . . . . . . . 1-7 path/port syntax . . . . . . . . . . . . . . . . . . . . 4-6
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10 Internet Key Exchange (IKE)
path/port syntax . . . . . . . . . . . . . . . . . . . . 4-6 negotiation with FRF.17 . . . . . . . . . . . . . . . . . 1-13
FlexWAN serial . . . . . . . . . . . . . . . . . . . . . . . . 1-7 IP address, configuring. . . . . . . . . . . . . . . . . . . . . 3-18
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-11 ISDN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
path/port syntax . . . . . . . . . . . . . . . . . . . . 4-6
. . . . . . . . . . . . . . . . . . . . . . . . . L. . . . . . . . . . . . . . . . . . . . . . . . . .
LAN connectors . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29 Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-29 normal operation . . . . . . . . . . . . . . . . . . . 3-3, C-9
LAN interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 system . . . . . . . . . . . . . . . . . . . . . . 3-3, C-9, C-15
baud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 V.24 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4, C-13
configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 WAN/Telco . . . . . . . . . . . . . . . . . . . . . . 3-3, C-12
duplex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7 LMI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3 load errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3
path/port syntax. . . . . . . . . . . . . . . . . . . . . . . . 4-6 Local Management Interface. See LMI
leased line services, supported . . . . . . . . . . . . . . . . 1-9 location, assigning system . . . . . . . . . . . . . . . . . . 3-17
leased lines logging on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
with PPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10 loopback tests
LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3 local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-24
E&M (analog). . . . . . . . . . . . . . . . . . . . . 3-4, C-14 responses to assertions. . . . . . . . . . . . . . . . . . C-26
error meanings. . . . . . . . . . . . . . . . . . . . . . . . C-15 Rx-to-Tx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Ethernet (LAN) . . . . . . . . . . . . . . . . . . . 3-3, C-10 Rx-to-Tx on link partner. . . . . . . . . . . . . . . . . C-25
FlexWAN serial . . . . . . . . . . . . . . . . . . . 3-3, C-11 serial line . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-21
. . . . . . . . . . . . . . . . . . . . . . . . . M. . . . . . . . . . . . . . . . . . . . . . . . . .
MAC addresses, for memory dump . . . . . . . . . . . C-29 menu-driven interface
memory dump accessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
configuring destination . . . . . . . . . . . . . . . . . C-28 exiting from . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
creating files for . . . . . . . . . . . . . . . . . . C-30, C-33 functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
obtaining MAC addresses . . . . . . . . . . . . . . . C-29 modules, optional (encryption)
performing . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27 installing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16
specifying options . . . . . . . . . . . . . . . . . . . . . . E-7 replacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
verifying procedure . . . . . . . . . . . . . . . . . . . . C-34 modules, optional (I/O)
verifying TFTP process . . . . . . . . . . . . . . . . . C-31 installing . . . . . . . . . . . . . . . . . . . . . 2-6, 2-7, 2-13
MEnu command. . . . . . . . . . . . . . . . . . . . . . 3-9, 3-10 replacing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10
monitor mode. See firmware boot monitor
IX-4 O C T OBE R 2 8, 20 1 3
mounting multiple ports per path . . . . . . . . . . . . . . . . . . . . . .4-4

in a rack. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-26
on a tabletop . . . . . . . . . . . . . . . . . . . . . . . . . .2-24
stacking units . . . . . . . . . . . . . . . . . . . . . . . . .2-25
. . . . . . . . . . . . . . . . . . . . . . . . . N. . . . . . . . . . . . . . . . . . . . . . . . . .
name, assigning system . . . . . . . . . . . . . . . . . . . . .3-17 notice conventions . . . . . . . . . . . . . . . . . . . . . . . . . XXII
Network Manager password. . . . . . . . . . . . . . . . . 3-11 numbering, paths and ports . . . . . . . . . . . . . . . . . .4-4
. . . . . . . . . . . . . . . . . . . . . . . . . P. . . . . . . . . . . . . . . . . . . . . . . . . .
packet-switched services . . . . . . . . . . . . . . . . . . . . .1-9 ports
supported . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10 analog
using . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-10 connector pinouts . . . . . . . . . . . . . . . . . . .2-57
parameters console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3
selecting on menu-driven interface. . . . . . . . .3-10 configuration settings . . . . . . . . . . . . . . . .2-63
parentheses, meaning in CLI . . . . . . . . . . . . . . . . . .3-7 connecting . . . . . . . . . . . . . . . . . . . . . . . .2-63
PassWord command . . . . . . . . . . . . . . . . . . . . . . .3-15 definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3
passwords E&M
"root" and "admin" . . . . . . . . . . . . . . . . . . . . . 3-11 connecting . . . . . . . . . . . . . . . . . . . . . . . .2-57
changing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13 connector pinouts . . . . . . . . . . . . . . . . . . .2-57
changing "root" and "admin" . . . . . . . . . . . . . 3-11 E&M (analog)
character and length restrictions . . . . . . . . . . .3-12 configuring . . . . . . . . . . . . . . . . . . . . . . . .4-16
default. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12 Ethernet (LAN)
paths baud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7
dynamic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3 configuring . . . . . . . . . . . . . . . . . . . . . . . . .4-7
dynamic dial pool . . . . . . . . . . . . . . . . . . . . . . .4-3 connecting . . . . . . . . . . . . . . . . . . . . . . . .2-29
multiple ports per path . . . . . . . . . . . . . . . . . . .4-4 connector pinouts . . . . . . . . . . . . . . . . . . .2-30
numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4 connectors. . . . . . . . . . . . . . . . . . . . . . . . .2-29
static . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3 duplex. . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7
pinouts FlexWAN serial
analog connectors . . . . . . . . . . . . . . . . . . . . . .2-57 baud . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-10
E&M connectors . . . . . . . . . . . . . . . . . . . . . . .2-57 configuring with DCEs . . . . . . . . . . . . . . . .4-9
EIA-530 DTE . . . . . . . . . . . . . . . . . . . . . . . . . .2-48 configuring with DTEs . . . . . . . . . . . . . . .4-11
Ethernet (LAN) connector. . . . . . . . . . . . . . . .2-30 connecting . . . . . . . . . . . . . . . . . . . . . . . .2-36
RS-232 DCE. . . . . . . . . . . . . . . . . . . . . . . . . . .2-41 connector types. . . . . . . . . . . . . . . . . . . . .4-11
RS-232 DTE . . . . . . . . . . . . . . . . . . . . . . . . . . .2-40 connectors. . . . . . . . . . . . . . . . . . . . . . . . .2-39
RS-449 DCE. . . . . . . . . . . . . . . . . . . . . . . . . . .2-47 multiple ports per path . . . . . . . . . . . . . . . . . . .4-4
RS-449 DTE . . . . . . . . . . . . . . . . . . . . . . . . . . .2-46 numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4
V.24 connectors . . . . . . . . . . . . . . . . . . . . . . . .2-50 V.24
V.35 DCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-43 configuring . . . . . . . . . . . . . . . . . . . . . . . .4-15
V.35 DTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-42 connecting . . . . . . . . . . . . . . . . . . . . . . . .2-50
WAN/Telco connectors . . . . . . . . . . . . . . . . . .2-49 connector pinouts . . . . . . . . . . . . . . . . . . .2-50
X.21 DCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-45 virtual, definition . . . . . . . . . . . . . . . . . . . . . . .4-4
X.21 DTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-44
O CT OB ER 28 , 2 01 3 IX-5
WAN/Telco powering router on and off . . . . . . . . . . 1-6, 2-66, 3-2

configuring . . . . . . . . . . . . . . . . . . . . . . . 4-12 PPP
connecting . . . . . . . . . . . . . . . . . . . . . . . . 2-49 using with dial-up and leased lines . . . . . . . . 1-10
connector pinouts . . . . . . . . . . . . . . . . . . 2-49 Primary Boot Source, SysconF menu option . . . . . E-3
power receptacle . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 protocols, supported . . . . . . . . . . . . . . . . . . . . . . 4-17
. . . . . . . . . . . . . . . . . . . . . . . . . R. . . . . . . . . . . . . . . . . . . . . . . . . .
rack-mount remote access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-26 resetting the router . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24 restricting access. . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
rear panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6 return authorization numbers . . . . . . . . . . . . . . . . B-1
Reboot (RB) command, firmware boot monitor . . . C-7 RS-232 DCE cable pinouts . . . . . . . . . . . . . . . . . . 2-41
recovering the system software . . . . . . . . . . . . . . . D-2 RS-232 DTE cable pinouts. . . . . . . . . . . . . . . . . . . 2-40
Recovery Action (RA) command, RS-449 DCE cable pinouts . . . . . . . . . . . . . . . . . . 2-47
firmware boot monitor . . . . . . . . . . . . . . . . . . . . . . C-6 RS-449 DTE cable pinouts. . . . . . . . . . . . . . . . . . . 2-46
Recovery Action, SysconF menu option . . . . . . . . . E-7
. . . . . . . . . . . . . . . . . . . . . . . . . S. . . . . . . . . . . . . . . . . . . . . . . . . .
SCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4 SSH
Secondary Boot Source, SysconF menu option. . . . E-3 accessing GGM 8000 via. . . . . . . . . . . . . . . . . 3-19
security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17 using for remote access . . . . . . . . . . . . . . . . . 3-19
Self-test, SysconF menu option. . . . . . . . . . . . . . . . E-3 stacking units with mounting brackets. . . . . . . . . 2-25
serial connectors . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39 starting up
cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-36 applying power . . . . . . . . . . . . . . . . . . . . . . . . 3-2
serial interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7 logging on . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
baud . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10 static paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39 statistics,boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-7
configuring with DCEs . . . . . . . . . . . . . . . . . . 4-9 SysCallerID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
configuring with DTEs. . . . . . . . . . . . . . . . . . 4-11 SysconF command . . . . . . . . . . . . . . . . . . . . . C-3, E-1
connector types . . . . . . . . . . . . . . . . . . . . . . . 4-11 SysconF menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39 Boot Sources option . . . . . . . . . . . . . . . . . . . . . E-6
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3, C-11 Boot Statistics option . . . . . . . . . . . . . . . . . . . . E-7
path/port syntax. . . . . . . . . . . . . . . . . . . . . . . . 4-6 Console Port option . . . . . . . . . . . . . . . . . . . . . E-2
services, supported. . . . . . . . . . . . . . . . . . . . . . . . 4-17 Primary Boot Source option . . . . . . . . . . . . . . . E-3
Set Self Test Action (ST) command, Recovery Action option . . . . . . . . . . . . . . . . . . E-7
firmware boot monitor . . . . . . . . . . . . . . . . . . . . . . C-8 Secondary Boot Source option . . . . . . . . . . . . . E-3
Show System Information (SI) command, Self-Test option . . . . . . . . . . . . . . . . . . . . . . . . E-3
firmware boot monitor . . . . . . . . . . . . . . . . . . . . . . C-7
Test Boot Source option . . . . . . . . . . . . . . . . . . E-4
shutting down . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
SysLog feature . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
SysPassWord command . . . . . . . . . . . . . . . . . . . . 3-13
using for remote access . . . . . . . . . . . . . . . . . 3-19
system components . . . . . . . . . . . . . . . . . . . . . . . . 1-3
SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
system information. . . . . . . . . . . . . . . . . . . 3-17, C-29
Solution Support Center (SSC) . . . . . . . . . . . . . . . . B-1
system LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
software recovery . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
system software recovery . . . . . . . . . . . . . . . . . . . . D-2
square brackets, meaning in CLI . . . . . . . . . . . . . . 3-7
IX-6 O C T OBE R 2 8, 20 1 3
. . . . . . . . . . . . . . . . . . . . . . . . . T. . . . . . . . . . . . . . . . . . . . . . . . . .
T1/E1 modules. See WAN/Telco modules Test Boot Source, SynsconF menu option . . . . . . . E-4
T1/FT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9 Test LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
configuring WAN/Telco interface. . . . . . . . . .4-12 text conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . XXIII
tabletop installation . . . . . . . . . . . . . . . . . . . . . . . .2-24 time, setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16
tamper evidence labels . . . . . . . . . . . . . . . . . . . . . F-1 torque specification, for I/O module
removing from power receptacle(s) . . . . 2-27, F-4 installation. . . . . . . . . . . . . . . . 2-10, 2-12, 2-18, 2-22
to secure front and rear of chassis. . . . . . . . . . F-2 troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
technical support . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 deleted image files . . . . . . . . . . . . . . . . . . . . C-15
Telco modules. See WAN/Telco modules . . . . . . . .2-6 during test phase. . . . . . . . . . . . . . . . . . . . . . C-20
Telco services, supported . . . . . . . . . . . . . . . . . . . .1-9 load errors. . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
Telnet, accessing GGM 8000 via . . . . . . . . . . . . . .3-19 Load LED . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
terminal load phase . . . . . . . . . . . . . . . . . . . . . . . . . . . C-15
baud rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14 Test LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
connecting. . . . . . . . . . . . . . . . . . . . . . . . . . . .2-63
. . . . . . . . . . . . . . . . . . . . . . . . . U. . . . . . . . . . . . . . . . . . . . . . . . . .
user accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15 user interface
managing . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-15 command-line . . . . . . . . . . . . . . . . . . . . . . . . . .3-6
privileged . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11 menu-driven . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9
User password. . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11
. . . . . . . . . . . . . . . . . . . . . . . . . V. . . . . . . . . . . . . . . . . . . . . . . . . .
V.24 cabling V.24 interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8
to base station . . . . . . . . . . . . . . . . . . . . . . . . .2-52 configuring . . . . . . . . . . . . . . . . . . . . . . . . . . .4-15
to modem . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-53 connector pinouts . . . . . . . . . . . . . . . . . . . . . .2-50
to SRU card . . . . . . . . . . . . . . . . . . . . . . . . . . .2-55 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4, C-13
V.24 connectors path/port syntax . . . . . . . . . . . . . . . . . . . . . . . .4-6
cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-50 V.24 module
pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-50 connector pinouts . . . . . . . . . . . . . . . . . . . . . .2-51
V.35 DCE cable pinouts . . . . . . . . . . . . . . . . . . . . .2-43
V.35 DTE cable pinouts . . . . . . . . . . . . . . . . . . . . .2-42
virtual ports, definition . . . . . . . . . . . . . . . . . . . . . .4-4
. . . . . . . . . . . . . . . . . . . . . . . . .W
..........................
WAN/Telco connectors LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3, C-12
cabling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-49 path/port syntax . . . . . . . . . . . . . . . . . . . . . . . .4-6
pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-49 WAN/Telco module
WAN/Telco interfaces . . . . . . . . . . . . . . . . . . . . . . .1-7 installing . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5, 2-6
configuring . . . . . . . . . . . . . . . . . . . . . . . . . . .4-12
connector pinouts . . . . . . . . . . . . . . . . . . . . . .2-49
O CT OB ER 28 , 2 01 3 IX-7
. . . . . . . . . . . . . . . . . . . . . . . . . X. . . . . . . . . . . . . . . . . . . . . . . . . .
X.21 DCE cable pinouts . . . . . . . . . . . . . . . . . . . . 2-45
X.21 DTE cable pinouts . . . . . . . . . . . . . . . . . . . . 2-44
IX-8 O C T OBE R 2 8, 20 1 3
MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the
Stylized M Logo are trademarks or registered trademarks
of Motorola Trademark Holdings, LLC and are used under license.
All other trademarks are the property of their respective owners.
2013 Motorola Solutions, Inc. October 2013

ALL RIGHTS RESERVED

S2500 Hwug 102813

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

S2500 Hwug 102813

Uploaded by

Copyright:

Available Formats

Motorola Network Router

Hardware User Guide

2013 MOTOROLA SOLUTIONS, INC.

7/29/2009 Updates to 04/09 version (part number 8971715H06-A):

12/17/2009 Updated note regarding support for tagged VLAN ports

2/10/10 Added Diffie-Hellman Group 14 to list of public key

6/15/2010 Updated the descriptions of the startup status for the

7/20/2010 Clarified that the T1/E1 interfaces include CSU/DSU

9/14/2010 Updated the descriptions of the E&M module LEDs.

10/5/2010 Corrected chapter headers in Chapters 2-4

3/23/2011 Added an appendix with instructions for installing

4/5/2011 Updated the Changing the root and admin

4/25/2011 Added information about connecting analog base stations

5/9/2011 Updated Installing Tamper Evidence Labels appendix

6/14/2011 Corrected the instructions for setting the V.24 clock

10/25/2011 Updated CCGW Functionality section.

12/13/2011 Usability enhancement: moved cable pinout information

8/31/2012 Added an appendix documenting how to copy files

10/2/2012 Updated the Installing the S2500 Hardware chapter to

10/22/2012 Updated the information for how to access related

4/19/2013 Added note to SysconF Command Menus appendix

7/29/2013 Changed grounding to grounding (earthing)

9/4/2013 Changed definition of SCC acronym from System Support

ABOUT THIS GUIDE

CHAPTER 1: S2500 OVERVIEW

CHAPTER 2: INSTALLING THE S2500 HARDWARE

Cabling the V.24 Connector(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50

CHAPTER 3: LOGGING ON AND PERFORMING ADMINISTRATIVE TASKS

CHAPTER 4: CONFIGURING PATHS, PORTS, AND CONNECTORS

FCC Part 15 Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

APPENDIX B: TECHNICAL SUPPORT

Performing a Memory Dump . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-27

APPENDIX D: RELOADING THE SYSTEM SOFTWARE

APPENDIX E: SYSCONF COMMAND MENUS

APPENDIX F: INSTALLING TAMPER EVIDENCE LABELS

APPENDIX G: COPYING FILES TO AND FROM A TFTP OR FTP SERVER

Figure 2-33: Cabling a FlexWAN Serial Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-37

PROCEDURES & PROCESSES

ABOUT THIS GUIDE

WHO SHOULD USE THIS GUIDE?

HOW THIS GUIDE IS ORGANIZED

Notice Type Alerts you to...

Important features or instructions

Crucial features or instructions

Risk of personal injury, system damage, or loss of

Risk of severe personal injury

Syntax Evaluate the syntax provided and supply the appropriate

Commands Enter the command exactly as shown in text and press

Screen displays This typeface represents information as it appears on the

S2500 HARDWARE OVERVIEW

T1/E1 FlexWAN System Fwd and

T1/E1 Link, 10BASE-T

T1/E1 10BASE-T System Fwd and

V.24 System Fwd an

FIGURE 1-4 REAR PANEL OF THE S2500

Power Configuration label

S2500 SUPPORTED INTERFACES

TABLE 1-1 S2500 SUPPORTED INTERFACES

Interface # of Ports Description

TABLE 1-1 S2500 SUPPORTED INTERFACES (CONTINUED)

Interface # of Ports Description

USING THE S2500 IN YOUR NETWORK

TABLE 1-3 PACKET-SWITCHED SERVICES SUPPORTED BY S2500 ROUTERS