advertisement
M-PATH™ T1
Channel Service Unit
User’s Guide
77537 M-PATH 537
Plug-in CSU
77538 M-PATH 538
Plug-in CSU with Ethernet
Part #650-00222-00
Copyright
Trademark information
Revision history
Copyright © 1996, 1997, 2001, 2004 by Kentrox, LLC. All Rights Reserved.
Printed in the U.S.A.
Specifications published here are current or planned as of the date of publication of this document. Because we are continuously improving and adding features to our products, Kentrox reserves the right to change specifications without prior notice. You may verify product specifications by contacting our office.
In no event shall Kentrox be liable for any damages resulting from loss of data, loss of use, or loss of profits. Kentrox further disclaims any and all liability for indirect, incidental, special, consequential or other similar damages. This disclaimer of liability applies to all products, publications and services during and after the warranty period.
Kentrox, DataSMART, and CrossPATH are registered trademarks of Kentrox,
LLC. DataSMART MAX, DataSMART SPort, and M-PATH are trademarks of
Kentrox, LLC.
All other product names are trademarks or registered trademarks of their respective owners.
Part #
65-77538101
5000241
650-00222-00
Date
January 1997
December 2001
September 2004
Description
Issue 1
Issue 2
Issue 3, Rebranded.
2
Contents
Entering commands and logging in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3
4
Preface
This manual contains a detailed description of all operations of the M-PATH 537 and 538 Channel Service Units (CSUs). It provides specific information for configuring the M-PATH unit and for using it to monitor and troubleshoot your T1 circuit’s performance. It also provides detailed listings of all M-PATH menus, commands, and specifications.
Who should read this manual?
This manual is intended as a reference source for ongoing operation of the M-
PATH CSU. It covers all possible operations and configuration choices in detail.
For initial installation, power up, and basic configuration of the unit, we recommend that you first turn to the M-PATH Installation Guide. Note that installation and service should be performed only by trained and qualified personnel.
Viewing this manual as a PDF file
This manual is designed to be used as both a printed book and a PDF file, and includes the following features for PDF viewing:
■
■
Cross-references are clickable hyperlinks that appear in blue text.
Chapters and section headings are represented as clickable bookmarks in the left-hand pane of the Acrobat viewer.
■
Page numbering is consistent between the printed page and the PDF file to help you easily select a range of pages for printing.
You can obtain PDF files of our manuals by visiting
http://www.kentrox.com/library
.
Related publications
MIB source files
In addition to this manual, the following are available:
■
■
M-PATH Installation Guide
How to install, power up, configure, and verify the installation of the M-
PATH 537 and 538.
Kentrox DSU/CSU MIB Reference
MIB source files are available by visiting
http://www.kentrox.com/support
.
5
About this manual
Conventions used in this manual
This manual contains the following information:
“Preface”
(this section) explains the purpose and organization of this manual, and tells how to contact Kentrox Customer Support if you run into difficulties.
“Introduction”
describes the applications and features of the M-PATH.
“Entering commands and logging in”
introduces you to the M-PATH commands
and explains how to log in.
“Establishing system security”
shows how to secure the M-PATH
command-line interface.
“Configuring the system”
describes in detail all of the system-level configuration
choices you can make. This includes specifying the system source clock, configuring the alarm message output, and configuring the DCE and DTE control ports.
“Configuring interfaces”
describes in detail all the configuration choices available
for the network interface, the terminal interface, and the data ports, as well as assigning channels.
“Performance monitoring”
shows you how to access and use the M-PATH performance reports, alarm history report, and security history report.
“Troubleshooting”
shows you how to use the M-PATH to recognize and troubleshoot abnormal conditions in your T1 circuit. It describes the M-PATH frontpanel LEDs, alarm messages, system status displays, and diagnostic tools such as loopbacks and BERTs.
“Using network management”
shows you how to set up and use the M-PATH in an SNMP network management environment and how to manage it over Ethernet,
T1 data link, or serial-port IP interfaces. It describes the unit’s embedded SNMP agent and how to establish a Telnet link.
“Quick reference”
summarizes M-PATH menus and commands and also provides a comprehensive listing of product specifications.
At the back of the manual, you’ll also find a glossary of terms and an index.
This manual employs the following conventions when explaining command-line syntax:
Literals
Variables x|y
[ ]
Bold type identifies commands and syntax elements that must be entered exactly as shown in the text.
Italic type identifies variable syntax elements, such as values or alphanumeric strings you can enter.
A vertical line between elements means that the elements are mutually exclusive; you can select one and only one of the elements.
Brackets indicate items that are optional.
6
Preface
Who to call for assistance
Admonishments
If you need assistance with this product or have questions not answered by this manual, please visit our Support page on the Kentrox Web site. You are also welcome to call or send email to our Technical Assistance Center. Please have your product's software revision and hardware serial numbers available to give to the
Support representative. All product returns must include a Return Authorization number, which you can obtain by calling the Technical Assistance Center.
The numbers listed below are current at the time of publication. See the Kentrox
Web site for detailed contact and warranty information.
1-800-733-5511 (continental USA only)
1-503-350-6001 email: [email protected]
http://www.kentrox.com/support
Important safety admonishments are used throughout this manual to warn of possible hazards to persons or equipment. An admonishment identifies a possible hazard and then explains what may happen if the hazard is not avoided. The admonishments, in the form of Dangers, Warnings, and Cautions, must be followed at all times. These warnings are flagged by use of the triangular alert icon
(seen below), and are listed in descending order of severity of injury or damage and likelihood of occurrence.
DANGER!
Danger is used to indicate the presence of a hazard that will cause severe personal injury, death, or substantial property damage if the hazard is not avoided.
WARNING!
Warning is used to indicate the presence of a hazard that can cause severe personal injury, death, or substantial property damage if the hazard is not avoided.
CAUTION!
Caution is used to indicate the presence of a hazard that will or can cause minor personal injury or property damage if the hazard is not avoided.
Preface
7
General safety precautions
This equipment has been designed to the highest quality standards of materials, workmanship and safety. Do not bypass any of the safety features of this equipment or operate this equipment in an improper environment.
WARNING!
Service should be performed only by trained and qualified personnel.
To avoid hazard from electrical shock and/or fire, adhere to the safety practices listed in this section and identified within the instructions of this document.
Use normal caution when installing or modifying telephone lines. Dangerous voltages may be present. It is unsafe to install telephone wiring during a lightning storm.
Always disconnect all telephone lines at the network interface, and power connections from the wall outlets before servicing or disassembling this equipment.
All wiring external to the product(s) should follow the provisions of the current edition of the National Electrical Code or any national wiring rules that apply.
WARNING!
Potentially hazardous voltages inside. Service should be performed only by qualified personnel.
AVERTISSEMENT!
Tensions Dangereuses à l'intérieur. Confier la maintenance à une personne qualifiée.
Regulatory approvals
For a list of relevant regulatory approvals, refer to the DataSMART® 500 Series
and M-PATH T1™ Channel Service Units Regulatory Approvals.
8
Preface
C H A P T E R
1
Introduction
The M-PATH 537 and 538 channel service units (CSUs) provide in-band SNMP-managed digital service access to T1 and fractional T1 lines. M-PATH units plug into the Kentrox
2-slot and 12-slot universal shelves.
You can manage remote M-PATH CSUs via SNMP over an in-band data link on the T1 line (using a facility data link or 8-64 Kbps of a DS0 channel). The unit at the near end of the management path can be an SNMP manager or another M-PATH CSU.
The M-PATH 538 controller also contains a modular Ethernet jack on its front panel, allowing Ethernet IP access to the M-PATH 538 and M-PATH 537 units installed in the same shelf. Also, M-PATH can use the SLIP and PPP protocols for IP access, using the
DCE or DTE control ports in the universal shelf.
The M-PATH 538 can automatically configure an M-PATH 537 installed in the same shelf. Simply power up, connect, and configure the 538 controller before plugging in the
537.
Figure 1—M-PATH 538 and 537 front views
POWER
FAIL
AUTO
CFG
DATA
CV
RED
ALM
YEL
ALM
CV
STATUS
TEST
LLB
OFF
DPLB
T
X
D
R
X
D
CTS
RTS
NI
TI
DATA
PORT
LINK
T
X ETHERNET
M-PATH
538
T1 CSU
M-PATH 538
POWER
FAIL
DATA
CV
RED
ALM
YEL
ALM
CV
STATUS
TEST
LLB
OFF
DPLB
T
X
D
R
X
D
CTS
RTS
NI
TI
DATA
PORT
M-PATH
537
T1 CSU
M-PATH 537
9
Typical applications
The following figures show typical applications for the M-PATH plug-in in the two-slot and 12-slot universal shelves.
M-PATH CSUs at a wireless base station
This figure shows how a network management system (NMS) might be used to manage a group of wireless base stations. Each base station contains an M-PATH plug-in in a twoslot shelf. Instead of installing an extra phone line and modems to manage the units, you dedicate one of the DS0 time slots going to each plug-in for management.
The Kentrox CrossPATH Mini-DCS unit can support from one to four T1 or FT1 links to base stations, as well as two V.35 ports. You can manage the M-PATH plug-ins and the
CrossPATH Mini-DCS transparently via SNMP or Telnet from a remote NMS.
NOC
3 / 1 / 0
DCS
Radios
Base Station
M-PATH in shelf
Radios
Base Station
M-PATH in shelf
FT1s
(1 DS0 per unit for management)
NMS
Regional Hub/
Base Station
Router
Radios
FT1
CrossPATH Mini-DCS
Management traffic
MSC
3/1/0
DCS
Switch
T1
(3 DS0 for management)
10
Chapter 1: Introduction
M-PATH CSUs at a wireless base station and MSC
This figure shows how M-PATH CSUs might be used at both ends of the T1 links between a Mobile Switching Center (MSC) and a group of wireless base stations. Each base station contains an M-PATH CSU in a two-slot shelf, and the MSC has a 12-slot shelf containing one M-PATH unit for each T1 line.
The management path information goes via SNMP or Telnet from the NMS through a router attached to the12-slot M-PATH shelf via Ethernet. The remote M-PATH CSUs are managed in-band.
Radios
Base Station
M-PATH in shelf
T1/FT1s
(1 DS0 per unit for management)
MSC
T1/FT1s
Radios
Base Station
M-PATH in shelf
3/1/0
DCS
Switch
Ethernet
Router
Radios
Base Station
M-PATH in shelf
3 / 1 / 0
DCS
NMS
Typical applications
11
Features of the M-PATH
■
■
■
■
IP-based network management (all units)
■
Allows you to configure, monitor, and troubleshoot individual plug-ins using standard network management tools
Generates traps when network events occur
Responds to pings
Allows Telnet access
Supports MIB II (for LAN-based hosts), the DS1 MIB (for T1 line management), and an Enterprise MIB (which allows SNMP access to all commands available via the control port menu interface; this includes performance monitoring, diagnostics and reconfiguration).
■
A/B power input monitoring and SNMP status trap (M-PATH 538 only)
Options for SNMP connectivity
■
Allows in-band access to remote stand-alone units over Facility Data Link (FDL) or
DS0 channel: FDL requires Extended Super Frame (ESF) framing on the T1 line;
DS0 can be idle or assigned to the M-PATH plug-in’s data port
■
In-band IP management data rate can be 56 or 64 Kbps (idle DS0); 8 Kbps (DS0 assigned to data port); or 4 Kbps (FDL)
■
Allows an Ethernet connection using 10BaseT connector (if shelf contains an
M-PATH 538 controller)
■
Allows a local serial connection via SLIP or PPP protocol through shelf’s control port
■
■
Data ports support all standard interfaces — and more
■
Supports V.35, EIA-530, and RS449 interfaces
V.35 interface compatible with cabling for all models of DataSMART DSUs
Kentrox adapters support both terminal interface and data port from a single connector on 12-slot shelf
■
■
■
■
T1 performance monitoring
■
Provides detailed network interface reports
Provides detailed terminal interface reports
Retains summary report data for seven days
Shows real-time status
Provides separate NI reports for user and carrier
12
Chapter 1: Introduction
■
■
T1 diagnostics
■
LEDs indicate problems at the network interface, data ports, terminal interface
(M-PATH 537 and 538) and Ethernet interface (M-PATH 538)
Allows loopbacks to be set remotely or locally
Contains a built-in test code generator and bit error rate test (BERT) to test line and equipment
■
■
Auto-configuration in universal shelf
■
Works after you’ve powered, inserted, and configured the 538
Automatically configures 537 plug-ins when first inserted into the universal shelf
Automatically re-configures 537 plug-ins with a single command to the 538
Nonvolatile memory
■
Retains unit’s configuration for five years without power
Features of the M-PATH
13
14
Chapter 1: Introduction
C H A P T E R
2
Entering commands and logging in
This chapter describes:
■
■
Entering commands via the command line interface
Logging into the M-PATH
15
Using the M-PATH
With the command line interface you use a terminal to manage and monitor the
M-PATH CSU.
Using the command line interface
The M-PATH command line interface is accessible through various physical connections:
■
■
■
■
Telnet via the front-panel Ethernet 10BaseT connector (538 only)
Telnet link to a remote unit over a facility data link within the T1 data stream
Telnet via PPP/SLIP connection to the shelf’s rear-panel DCE or DTE control port
ASCII (non-IP) connection to the shelf’s rear-panel DCE or DTE control port
Menus vary according to your M-PATH model. Some commands apply only to the
M-PATH 538 with the Ethernet connector.
Figure 2—The Main menu
M-PATH 53n Version 1.nn Copyright (c) 1996-97 Kentrox
ADDRESS: 01:00:000 NAME: PORTLAND,OR
MM - Main Menu
SS - System Status and Remote Menu
R - Reports Menu
LM - Local Maintenance Menu
RM - Remote Maintenance Menu
AC - Alarm Configuration Menu
CC - Control Port Configuration Menu
DC - Data Port Configuration Menu
FC - Fractional T1 Configuration Menu
MC - Management Configuration Menu
NC - NI Configuration Menu
PC - Password Entry and Configuration Menu
SC - System Configuration Menu
TC - TI Configuration Menu
^D - Logout
^D<xx>:<yy>:<zzz>^E - Address Another Unit
MM>
16
Chapter 2: Entering commands and logging in
To see one of the menus, enter the menu name at the prompt. For instance, to see the
Reports menu, enter R at the prompt.
MM> R
REPORTS MENU
UNSR / UNLR
UTSR / UTLR
CNSR / CNLR
FESR / FELR
- User NI Short/Long Performance Report
- User TI Short/Long Performance Report
- Carrier NI Short/Long Performance Report
- Far End PRM Short/Long Performance Report
NSR:[z]
TSR:[z]
AHR
SHR
- User NI Statistical Performance Report
- User TI Statistical Performance Report
z = Display Report then Zero Counts (Optional)
- Alarm History Report
- Security History Report
PL:<len|style> - Set Page Length, <len> = 20 .. 70 (or 0 = Off), or
<style> = P (Page Break), M (More), or V (View)
R>
Each time you change menus, the command line prompt changes to indicate which menu is current. In the preceding figure, the first line shows a prompt of MM> meaning that the
Main menu is current. However, once R is entered and the Reports menu is displayed, the prompt becomes R>, indicating that the Reports menu is current.
The current menu displays when you press the Enter key. In normal use you are likely to use a series of commands from a given menu, and so you can make that menu current and get a menu listing whenever you need it by pressing the Enter key. However, you may enter any command at the command line, even if it is not on the “current” menu.
Command line syntax
A typical command line consists of the command and zero or more arguments, all separated by one or more delimiters. The following are all valid delimiters: a space, a tab, a comma, a colon, a forward slash. You can use any combination of valid delimiters to separate arguments.
For example, SD 12/08/97 and SD 12 08 97 are both valid commands to set the date to
December 8, 1997. However, SD 12-08-97 is not, because the dash is not a valid delimiter.
When entering an IP address or netmask, follow the custom and include periods as part of this ID. The M-PATH will interpret the ID as a single argument.
There are two exceptions to these rules. One is a string value entered for the SN, TCS,
RCS, WCS, TPW, EPS, APS, or DPS commands. In a string value, a space, comma, forward slash, or colon can appear in the argument, as long as there is a non-delimiter preceding it (not necessarily immediately preceding it). For example, this is a valid instance of the SN command:
SN PORTLAND, OR
The other exception is the syntax for logging into an M-PATH unit (see “Logging in” on page 18 ).
Type-ahead
You may enter the next command while a previous command is executing. The maximum type-ahead is three commands or 256 characters, whichever is less.
Using the M-PATH
17
Logging in
You can log into a M-PATH unit using serial communications over a control port or in-band over the T1 (using the facility data link or a DS0 channel). If the unit is configured for IP access, you can also log into it over Telnet. Passwords are not needed, but, when implemented, can restrict some users from using some commands.
Through the control port
In general, a password is not needed to log into an M-PATH CSU. Though the M-PATH supports passwords, the passwords do not prevent login but instead restrict users from executing various commands. (See Chapter 3 for procedures on setting passwords.)
Depending on whether you are accessing the M-PATH through Telnet, the data link, a
DS0 channel, or the DTE or DCE control port, the procedure for logging in differs.
Each CSU has a unique daisy-chain address. The command syntax to log into a unit is:
^Dxx:yy:0zz^E where
^D, ^E
xx
Press the Ctrl and D (or Ctrl and E) keys simultaneously.
is the slot location of the plug-in.
In a two-slot shelf, the value is 01 or 02. When you are looking at the front of the shelf, slot 1 is on the left and slot 2 is on the right.
In a 12-slot shelf, the value can be 01 through 12. When you are looking at the front of the shelf, slot 1 is the first slot on the left and slot 12 is the first slot on the right.
yy
0zz is the shelf address. This value is set via bits 1 through 4 of the SHELF
ADDRESS DIP switches on the rear-panel of the shelf. The bits are binary-encoded to allow values 00 through 15.
is the group address. This value is set via bits 1 through 4 of the GROUP
ADDRESS DIP switches on the rear-panel of the shelf. The bits are binary-encoded to allow values 000 through 015.
For information about how to set up the DIP switches on the shelf, refer to your
M-PATH Installation Guide.
When you log in using the syntax: ^Dxx:yy:0zz^E you see the full main menu.
Note that the colon is the only valid delimiter for the login command.
18
Chapter 2: Entering commands and logging in
Through the facility data link
Telnet access
Logging out
The facility data link (FDL) uses a signal embedded in the T1 framing pattern to enable you to log into a remote M-PATH 537 or 538 CSU on the far end of a T1 line. The FDL is available only if the two units are both using Extended Super Frame (ESF) framing.
You must be logged into the near-end M-PATH CSU before you can access a far-end unit.
Once you are logged into the near-end M-PATH CSU, enter this command:
ARC
The angle brackets in the command prompt change from “>” to “<” to indicate that you are logged into a far-end device.
You log out of the far-end device by entering this command:
DRC
If your M-PATH unit has been configured for IP access and you have set up a Telnet password on the unit, you can log into it using Telnet. When you enter the unit’s IP address and attempt to log in, you will be prompted for its Telnet password.If the M-PATH has not been set up for IP access and assigned a Telnet password, you will not be able to log in.
See Chapter 8 for information on configuring a M-PATH CSU for Telnet login.
You should always log out of the M-PATH when you are done.
To log out, enter ^D. (Press the Ctrl and D keys simultaneously.)
If you have logged into a remote M-PATH using ARC, use the DRC command or ^D to log out.
You can also log out by disconnecting the control port cable.
The M-PATH has an auto-logout feature that logs you out after a period of inactivity.
Auto-logout is always enabled when Telnet or ARC is being used. If auto-logout was disabled before a Telnet session is started, that Telnet session logs out automatically after 15 minutes of inactivity. Otherwise, if auto-logout is enabled, the Telnet session logs out after the specified period of inactivity. See
“Setting auto-logout for the control port” on page 34 .
Logging in
19
20
Chapter 2: Entering commands and logging in
C H A P T E R
3
Establishing system security
The M-PATH CSU can be accessed by an SNMP network manager or via the command line interface, using either a terminal or Telnet. In order to prevent unauthorized users from changing the system configuration, setting loopbacks, or performing other operations that might disrupt service, you must secure each of these interfaces.
This chapter tells how to secure the command line interface.
The SNMP and Telnet security features are discussed in Chapter 8
.
21
Securing the command line interface
Security for the command line interface is achieved through a system of passwords and privilege levels. If a password is not set, any user can access the command line without entering a password. In order to gain a specific privilege level, the user must enter a password that has that privilege level assigned to it.
Restricting access
By default, there are no restrictions on which commands you can run on the M-PATH.
Every user has superuser privileges. In order to restrict access, you must create at least one password with the superuser privilege level. Once you do, every user is restricted to the read-only privilege level unless they enter a password that permits more extensive privileges. You may create up to ten passwords (assuming you have superuser privileges) and assign them any privilege level you like.
NOTE
You must enter a superuser password to activate security. If you do not create a password with a superuser privilege level, every user that accesses the command line will be granted superuser privileges, regardless of whether or not you have created passwords for the other privilege levels.
Table 1—Privilege levels
Privilege level
Read-only
Maintenance
Configuration
Superuser
Description
Users with no password, and thus no privilege level, have read-only access. They can view menus, status screens, and performance reports, but they cannot execute any diagnostics nor change any configuration options.
Users with this privilege level can execute diagnostic tests, such as loopbacks and BERTs. Their activities can potentially disrupt data traffic through the device.
Users with this privilege level can execute all tests allowed at the Maintenance level, plus they can change the configuration options of the M-PATH. Their activities can potentially disrupt service to the device.
Users with this privilege level have access to all commands allowed at the Configuration level, plus they have access to the commands that set up and control passwords.
22
Chapter 3: Establishing system security
The commands available for setting up and controlling command line passwords are listed in the Password Entry and Configuration menu. To display this menu, log into the desired
CSU, then enter PC at the command line.
PASSWORD ENTRY AND CONFIGURATION MENU
EPS:<password> - Enter Password
password = 6 to 12 characters
APS:<access>:<password> - Add Password
access = SA - Super User
CA - Configuration
MA - Maintenance
password = 6 to 12 characters
DPS:<password> - Delete Password
password = 6 to 12 characters, or * for all
PUV - View User Access Privilege
PCV - View Password Configuration
Adding a password
Deleting a password
You create a new password by using the APS command. You must have superuser privileges. The command syntax is:
APS:access:password
access Specify the privilege level you want linked to the password: SA
(superuser), CA (configuration), or MA (maintenance).
password
Specify the password you want added. The string can comprise from six to twelve ASCII printable characters. (If the string you enter is either too long or too short, you’ll get an error message.)
Passwords are not case-sensitive and trailing spaces are not truncated.
Up to ten passwords are allowed. If you attempt to enter an eleventh password, you will get an error message. To add another password, you must first delete an existing password.
Each password must be unique.
You delete a password using the DPS command. You must have superuser privileges. The command syntax is:
DPS:password
password
Specify the password you want deleted. The string must match the password exactly, except for case. You can also enter the * wildcard character to delete all current passwords.
Securing the command line interface
23
Entering a password
Viewing a user’s access level
Viewing the current passwords
To gain the privilege level associated with a password, use the EPS command. No special privileges are required. The command syntax is:
EPS:password
password
Enter the password. Passwords are not case-sensitive.
If you enter the password correctly, M-PATH responds with the message
PASSWORD ACCEPTED. If you enter an incorrect password, it responds with the message PASSWORD DENIED.
If you are logged into the device, you can view your privilege level by using the PUV command. You do not need any special privilege level. You will receive one of the following messages:
“User has No Access Privileges”
“User has MA Access Privileges” (maintenance)
“User has CA Access Privileges” (configuration)
“User has SA Access Privileges” (superuser)
If your password was modified during your current session (e.g., a superuser deleted your password, then added it back with a different privilege level), the change will not become effective until the next time you specify the password with the EPS command.
You can view a listing of current passwords and their privilege levels using the PCV command. You must have superuser privileges.
An example listing is shown below. The left column lists the current passwords, the right column identifies the access privilege levels.
VIEW PASSWORD CONFIGURATION
Password Access
------------ ------
BROWNS MA
JOHNSOND CA
MITCHELLS SA
24
Chapter 3: Establishing system security
C H A P T E R
4
Configuring the system
This chapter discusses configuration operations that apply to the M-PATH as a whole. It covers the commands and options listed in the System Configuration, Control Port Configuration, and Alarm Configuration menus.
Topics include:
■
■
■
■
■
■
■
■
Setting the M-PATH real-time clock and source clock
Enabling auto-configuration
Enabling auto-logout
Resetting the M-PATH unit to its default state and clearing performance data
Configuring the control port
Configuring alarm message output
Specifying error thresholds for reporting
Downloading new system software using TFTP
For information on configuring interface ports and assigning channels, see Chapter 5.
For information on configuring the M-PATH for network management, see Chapter 8.
25
Specifying system parameters
You can control the system-level parameters and activities by using the command-line interface.
Command line access
The commands for configuring the system parameters are listed below. To display this menu, first log into the unit you want to program, then enter SC.
SYSTEM CONFIGURATION MENU
M-PATH 538 only
SD:<mm>,<dd>,<yy> - Set Date (Warning: This also clears reports)
ST:<hh>,<mm> - Set Time (Warning: This also clears reports)
SN:<id> - Set Name
EAC / DAC - Enable/Disable Auto Configuration
SAC:<xx>,<yy>,<zzz> - Send Auto-Configure Packet to unit
<slot>:<shelf>:<group>, * is all units
EDC / DDC - Enable/Disable DataSMART Compatibility
CLK:<src> - Clock Source, src = L (Loop), C (CSU Thru)
T (TI Receive), I (Internal), 1 (DP1)
ALGOUT:<n> - Autologout, n = 0 .. 60 minutes
ZALL - Zero All Counters used in User Reports
TSWDL:<i> - Download program from a file via TFTP
i = n.n.n.n, n = 0..255 (dec), the
IP address of the TFTP host system
BOOT:<b> - Re-boot the system
b = A (Active FLASH) or I (Inactive FLASH)
WYV - View "What's Your Version" Information
RSD - Reset System to Default Values
SCV - View System Configuration
Viewing the current settings
Before changing any system parameters, you may want to look at the current settings. You do this by executing the SCV command. This command displays the View System
Configuration screen.
VIEW SYSTEM CONFIGURATION
Date Time Name Address Autologout
------------ ----- --------------- --------- ----------
JAN 11, 1997 14:10 PORTLAND,OR 01:00:000 DISABLED
User Clock Current Clock ARC Mode Auto Cfg
----------- ------------- --------------- --------
LOOP LOOP DataSMART 72xxx ENABLED
26
Chapter 4: Configuring the system
Field
Date
Time
Name
Address
Autologout
User Clock
Current Clock
ARC Mode
Auto Cfg
Description
This field displays the current date of the real-time clock.
This field displays the current time of the real-time clock.
This field displays the name assigned to the M-PATH unit you are logged into. The name appears in the Main menu, in all performance reports, and in alarm messages.
It is also the name returned for the MIB II sysName object.
This field displays the physical (daisy-chain) address of the M-PATH unit you are logged into. The address is in the form of xx:yy:zzz, where xx is the slot location of the unit, yy is its shelf address, and zzz is its group address.
This field specifies the state of auto-logout. If auto-logout is enabled, it displays the auto-logout period in minutes.
This field identifies the clock source you have assigned to be used as the system clock.
This field tells you the actual clock source being used as the system clock. Under normal operating conditions, this field will be identical to the “User Clock.” It will differ from “User Clock” if the M-PATH has lost its primary clock source.
This field tells you if ARC mode is set for compatibility with a DataSMART 72000 series DSU/CSU (default) or a DataSMART 78000 series DSU.
This field tells you whether or not auto-configuration is enabled for the unit. When auto-configuration is enabled:
Configurable plug-ins (537), when first inserted into a shelf, request auto-configuration information from the
538 controller unit installed upstream in the shelf.
Controller plug-ins (538) respond to auto-configuration requests from downstream 537 units.
Specifying system parameters
27
Setting date and time
The M-PATH uses an internal, real-time clock to time stamp event occurrences. The time stamps appear in alarm messages and performance reports as an aid to troubleshooting. To make the time stamps accurate, you must set the date and time of the real-time clock upon system installation.
Once you have set the real-time clock, you need to reset it only if the M-PATH has an extended power loss. The real-time clock operates for ten hours, nominally, after power is lost.
CAUTION!
When you change the date or time parameters of the real-time clock, all performance data is cleared from the performance reports.
TIP
If you want to track between
Daylight Savings Time and
Standard Time, you will need to reset the “time” parameter when local time changes.
Set the date by using the SD command. You must have superuser or configuration privileges. The command syntax is:
SD:mm,dd,yy
mm dd
Specify the month. You can enter the three-letter abbreviation or the number of the month.
Specify the day of the month. The M-PATH performs a range check on the entered value to see if the day is valid for the given month and year.
yy
Specify the last two digits of the year.
Set the time by using the ST command. You must have superuser or configuration privileges. The command syntax is:
ST:hh,mm
hh
mm
Specify the hour. The time is specified in “24-hour” format, where
12:00 is noon and 00:00 is midnight. Allowed values are
0 to 23, inclusive.
Specify the minutes. Allowed values are 0 to 59, inclusive.
28
Chapter 4: Configuring the system
Naming the device
Each M-PATH is assigned a device name that appears in alarm messages, performance reports, and at the top of the main menu. You can specify any name up to 15 characters long. Usually you specify a name that represents your site or the service you are connected to.
The device name specified here is also the name returned with the MIB II sysName object.
The default device name is “PORTLAND,OR.”
You change the device name by using the SN command. You must have superuser or configuration privileges. The command syntax is:
SN:id
id
Enter the device name. The name can be up to 15 characters long, including spaces, commas, or colons. A space, comma, or colon may not appear in the first position. Trailing spaces are truncated.
The M-PATH automatically converts all alphabetic characters to upper case.
Enabling/disabling auto-configuration
TIP
Because auto-configuration copies the entire configuration image to newly installed plugins, make sure the controller’s system and IP configuration is completely correct before you insert any configurable 537s.
For complete information on auto-configuration, refer to
and
manual and Chapter 5 and
Appendix B of the M-PATH
Installation Guide.
When your site includes a mixture of M-PATH 538 controllers and M-PATH 537 units, the auto-configuration feature automatically copies the configuration image (system configuration and IP management configuration) from an M-PATH 538 to any M-PATH 537 installed downstream in the same shelf (or a shelf daisy-chained to that shelf.)
When an M-PATH 537 is installed for the first time in a given slot, it sends a “request for configuration” message to the M-PATH 538 controller at the head of its chain. The controller then sends a configuration packet, based on its own configuration image, to the
M-PATH 537 unit. See
Table 2 for the types of parameters in the configuration packet.
Auto-configuration is enabled on all plug-ins by default.
For auto-configuration to work, the following events must occur in this order:
■
■
■
The shelf is mounted and powered up.
The controller is plugged in, and you have fully configured it.
Auto-configuration is enabled on the controller (this is the default).
The preferred method of auto-configuring a new M-PATH 537 is to plug it into a powered shelf that contains a controller unit that you have configured (called hot swapping).
Alternatively, after the controller has been fully configured, you can turn power off to the shelf, plug in all the M-PATH 537 units, and then restore power to the shelf. All the
M-PATH 537 units in the shelf will then configure themselves.
Specifying system parameters
29
The downstream direction within the shelf is determined by the control port being used.
Even if you don’t plan to connect a device or shelf to either control port, you should know which control port is selected. The default control port is DCE.
The chain runs left-to-right with a DCE control port, right-to-left with a DTE.
downstream when using DCE downstream when using DTE
During auto-configuration, a controller will send only those parameters that it can interpret. If a configurable unit receives a parameter it can not interpret, it ignores the parameter, but still passes it downstream to the next unit.
Table 2—Parameters set up in auto-configuration
AC
NI
TI
DP
FC
Abbreviation Parameters
SC
NM
All system configuration parameters, except “name” and “address”
(the plug-in’s slot-shelf-group position determines its address)
All alarm configuration parameters
All network interface configuration parameters
All terminal interface configuration parameters
All data port configuration parameters
All fractional configuration parameters, including channel mapping
A, B and X
All M-PATH network management parameters on the MC and AMC menus, except the data port IP address
■
■
The control port IP address is determined by the shelf type and the slot where the controller is installed. For more information, see the appropriate chapter in the M-PATH
Installation Guide:
For the 2-slot shelf, refer to Chapter 2.
For the 12-slot shelf, refer to Chapter 3.
Auto-configuration must be enabled on all units
Auto-configuration must be enabled on both controller and configurable plug-ins. It is enabled by default.
To enable or disable auto-configuration, enter:
EAC
Enable auto-configuration.
DAC
Disable auto-configuration.
30
Chapter 4: Configuring the system
Specifying the system clock
For most applications, the M-PATH is set to derive its source clock from the network receive signal (Loop Timing). This is the most common timing setup and should be used if your T1 service provider supplies timing. If your T1 service provider does not supply tim-
ing, you must select an alternate source as specified in Table 3.
on
page 32 illustrates some common timing applications. When setting up your
T1 circuit timing, it is important to remember this general rule: There must be one and
only one timing source for the T1 circuit.
The default is Loop Timing (i.e., the network receive signal).
Table 3—Timing options
Timing option
Loop Timing (L)
CSU Through Timing (C)
TI Receive Timing (T)
Internal Master Timing
(uppercase I)
Data Port 1 Timing
(numeric 1)
(This is also known as Tail
Circuit Timing)
Description
This option tells the M-PATH to derive its system clock from the incoming signal at the network interface.
Select this option if: 1) the T1 service provider is supplying a timing source, or 2) you are using the far-end device in a point-to-point connection as the master timing source.
This option times data output by passing through the timing with the data. The timing signal passes through transparently.
Do not select the CSU Through Timing option if you want to assign any DS0 channels to the M-PATH unit’s data port.
This option tells the M-PATH to derive its system clock from the incoming signal at the terminal interface.
Select this option if: 1) the T1 service provider is not supplying a timing source, and 2) you want to receive timing from a device beyond the terminal interface, such as a PBX.
This option tells the M-PATH to use its internal oscillator as the system clock. In this case, the M-PATH becomes the master in a point-to-point connection. The far-end device should be set to Loop Timing.
Select this option only if the T1 service provider is not supplying a timing source.
This option tells the M-PATH to derive its system clock from the signal being received on the data port
connector’s external clock pins (see Table 15 on page
).
The data port configuration must be set to the data rate received and the clock supplied must meet the network accuracy standard of +32 ppm.
Select this option only if the T1 service provider is not supplying a timing source and the timing source is the device connected to the specified data port.
To use this option, at least one DS0 channel must be assigned to the data port. However, data port timing is not available if the IP management data link is using a channel assigned to the data port.
Specifying system parameters
31
Figure 3—Common timing applications
POINT-TO-POINT DSU/CSU ADD/DROP APPLICATION: SPAN UNTIMED
Internal Master Timing
NI
NI
Clock
Loop Timing
V.35
DP
DTE (Data)
TI
Voice
V.35
DP
DTE (Data)
FRACTIONAL T1 DSU/CSU ADD/DROP APPLICATION: SPAN TIMED BY CARRIER
Voice
TI
Loop Timing
TI
Voice
V.35
DP
DTE (Data)
NI
FT1
Master Clock
1 / 0
DCS
NI
FT1
Loop Timing
V.35
DP
DTE (Data)
CSU APPLICATION: CSU THROUGH TIMING
TI
Voice
TI
Voice
Radios
Clock
TI
NI
Carrier
Network
32
Chapter 4: Configuring the system
Secondary clock source
If the expected timing source is not present or is lost, the M-PATH defaults to Internal
Master Timing. This occurs under the conditions specified in Table 4.
Table 4—Conditions that cause a default to internal timing
Timing option
Loop Timing
CSU Through Timing
TI Receive Timing
Data Port Timing
Condition
The M-PATH defaults to internal timing if it cannot detect a framed incoming signal at the network interface, either because the signal is lost or because the signal is out of frame or AIS is detected.
If the M-PATH cannot detect a framed signal at the network interface or terminal interface, it sends a “keep alive” signal and also defaults to internal timing. This happens when the signal is lost or because the signal is out of frame or AIS is detected. For the format of the
“keep alive” signal, see “Specify the “keep alive” signal for the network interface” on page 49
.
The M-PATH defaults to internal timing if it cannot detect a clock in the incoming signal at the terminal interface, either because the signal is lost or because the signal is out of frame or AIS is detected.
The M-PATH defaults to internal timing if it cannot detect an XCLK signal at the data port, either because a clock signal is not present or because a DPLOS has occurred.
T
I
L
C
1
Setting the clock source
You set the M-PATH source clock by using the CLK command. You must have superuser or configuration privileges. The command syntax is:
CLK:src
The src value specifies the source clock as:
Loop Timing
CSU Through Timing
TI Receive Timing
Internal Master Timing
Data Port Timing (also known as Tail Circuit Timing)
Specifying system parameters
33
Setting auto-logout for the control port
Zeroing all counters
You can program the M-PATH to automatically log out a user who has been inactive for a specified period of time. This feature helps prevent situations where:
■
A user with a high privilege level forgets to log out, leaving the system open to unauthorized users.
■
■
A user forgets to log out and blocks other users from logging in.
A Telnet or ARC connection breaks down and hangs the connection.
You can specify an auto-logout of 0 (off), or from 1 to 60 minutes, inclusive. A setting of
0 disables the auto-logout timer for users who log in via a serial device connected to the control port. It does not disable the timer for users who log in via Telnet or ARC — you cannot disable auto-logout for these types of remote logins. When the timer is set to 0, the
M-PATH defaults to a 15-minute auto-logout period for Telnet or ARC.
The default for auto-logout is 0 (off).
To specify an auto-logout period for the control port, use the ALGOUT command. When you set the timer to a value greater than 0, that value is used as the auto-logout period for the control port, and for Telnet and ARC logins.
You must have superuser or configuration privileges to use the ALGOUT command. The command syntax is:
ALGOUT:n
n
Specify the auto-logout period in minutes, from 1 to 60, inclusive. 0 disables the timer (the auto-logout period for Telnet and ARC logins becomes 15 minutes).
If you change the configuration parameters for the M-PATH, you may want to clear the performance database. You do this by zeroing all counters. This clears the data from the following:
■
■
■
■
■
■
User NI Short and Long Performance reports
User TI Short and Long Performance reports
Far-end PRM Short and Long Performance reports
User NI Statistical Performance report
User TI Statistical Performance report
Error threshold counters
It does not clear the data from:
■
■
■
Carrier NI Short and Long Performance reports
Alarm History report
Security History report
To zero the counters, use the ZALL command. You must have superuser or configuration privileges.
34
Chapter 4: Configuring the system
Obtaining new system software
TIP
In most cases, the file name your administrator assigns to the M-PATH software will be case-sensitive. This depends on the TFTP host’s operating system.
You can obtain M-PATH system software updates either in a PC software download package or via Trivial File Transfer Protocol (TFTP).
To obtain the PC software download package, call Kentrox Customer Support for assistance.
To obtain the software update via TFTP, continue reading.
The TFTP software update process has three parts:
■
Your company’s network administrator or system administrator downloads a package containing the software and a README file from: http://www.kentrox.com/support .
■
The administrator then places the file on your company’s TFTP host system. (The file must be in the TFTP host’s default TFTP directory.) He or she informs you of the TFTP host’s IP address and the file name.
■
Using any active IP connection, you download new system software into the
M-PATH flash memory. (See Chapter 8 for information on selecting an IP connec-
tion.) After the file is successfully downloaded, enter the BOOT:I command to restart the unit and execute the software you just downloaded.
NOTE
Once you have booted your unit from the updated software, that software version becomes the active software version and is booted by default when you restart the unit or reset defaults. The unit stores the previous software version in what is now the inactive memory bank. To boot the previous software, enter BOOT:I again.
The TFTP IP address must be in your unit’s Source Address Screening list if Source
Address Screening is enabled. (See “Setting up IP source address screening” on page 135 .)
Use the following command to download a software update. You must have superuser privileges.
i
TSWDL:i
Enter the IP address of the TFTP host where the software update is stored. Valid addresses are 0.0.0.0 to 255.255.255.255.
Use the following command to boot your M-PATH unit from either the active or inactive memory bank.
NOTE
Booting the M-PATH CSU will log out all users, execute the self-test, zero counters in the performance reports and clear the Carrier NI, Security History, and Alarm History reports, and reset all performance data.
To boot the M-PATH CSU, you must have superuser privileges.
BOOT:b
b
Enter I for inactive software version or A (default) for currently active software version. Entering BOOT:I causes the inactive software version to become the active version and vice versa.
Specifying system parameters
35
Obtaining product version information
If you call Kentrox Customer Support, you should have the model and serial numbers for your M-PATH available to give to your representative. You can obtain this information from the command line.
Use the WYV command to obtain version information. You must have superuser, configuration, or maintenance privileges. The M-PATH displays the version information on the screen, similar to the following.
KENTROX 01-72538001, SERIAL nnnnnnnn,
STAT nnnnn, ACTIVE 1.nn, INACTIVE 1.nn
M-PATH 538 only
Resetting to default values
You can reset the M-PATH to its default power-up state at any time. The M-PATH will:
■
■
■
Log out all users
Restart its control program and execute self test
Reset all configuration parameters to their default state, including bandwidth assignments and IP addresses
■
Zero counters in the performance reports and clear the Carrier NI, Security History, and Alarm History reports
■
Reset all performance data
Once the self-test has been completed, you can log into the M-PATH CSU.
CAUTION!
A reset to defaults causes a service disruption until the M-PATH CSU is reconfigured for service. (If your required configuration is identical to the default, the service disruption lasts only as long as it takes for the unit to reboot.)
To reset the M-PATH to its default configuration, use the RSD command. You must have superuser or configuration privileges.
Clearing stored information
The actions to clear stored information from the M-PATH are summarized in Table 5
.
Table 5—Actions that clear stored information from the M-PATH
Action
Clears all configuration data
Set date or time(SD or ST,
) Not cleared
Zero all counters (ZALL,
Cycle power to unit
Boot unit (BOOT,
Not cleared
Not cleared
Reset to defaults (RSD, page 36
) Cleared
Clears Carrier NI, Alarm History, and Security History reports
Not cleared
Not cleared
Cleared
Cleared
Cleared
Clears all other reports
Cleared
Cleared
Cleared
Cleared
Cleared
36
Chapter 4: Configuring the system
Configuring the control port
You need to set up the control port parameters if you plan to communicate with the
M-PATH via a DCE or DTE control port. These parameters must be set up regardless of whether you plan to communicate through a terminal with an ASCII connection, a modem, or a SLIP or PPP connection for Telnet or SNMP.
There are six steps to using a control port:
1
Set the shelf’s SW5 switch to DCE or DTE to determine which control port should receive commands.
See Chapter 2 or Chapter 3 of the M-PATH Installation Guide.
2
Set the shelf’s rear-panel switches to the appropriate communication parameters
(baud rate, data bits, stop bits, and parity.). The switch settings must match the settings of the connected control device.
See Chapter 2 or Chapter 3 of the M-PATH Installation Guide.
3
Connect a cable between the port and the control device.
See Chapter 2 or Chapter 3 of the M-PATH Installation Guide.
4
Log into the M-PATH.
Step 4 is covered on
of this manual.
5
Enable or disable character echo, as necessary.
Step 5 is covered on
of this manual.
6
Specify the control port IP network interface (SLIP, PPP, or None; specify None if you are using ASCII only).
Step 6 is covered in Chapter 8 of this manual.
Commands related to control port configuration are listed below. To view this menu, log into the unit you are interested in, then enter CC.
CONTROL PORT CONFIGURATION MENU
EE / DE - Enable/Disable Character Echo
CCV - View Control Port Configuration
Configuring the control port
37
Viewing the current configuration
You can look at the current control port settings by executing the CCV command. This command displays the View Control Port Configuration screen, as shown below.
VIEW CONTROL PORT CONFIGURATION
Echo Control Port Daisy Chain CP Setup
-------- ------------ ----------- ---------
ENABLED DCE ENABLED 96,N,8,1
DCE Inputs DTE Inputs
---------- ----------
RTS DTR CTS DCD
--- --- --- ---
ON ON OFF OFF
Field
Echo
Control Port
Daisy Chain
CP Setup
DCE Inputs
DTE Inputs
Description
This field tells you if character echo is enabled or disabled.
This field tells you the port at which the M-PATH receives commands and outputs alarm messages.
This field is always enabled for the M-PATH CSU.
This field tells you the protocol settings of the control port: baud rate in hundreds, parity, data-bits-percharacter, and stop-bits-per-character.
These fields tell you the control port input signal state for RTS and DTR. Possible values for each include
ON or OFF.
These fields tell you the control port input signal state for CTS and DCD. Possible values for each include
ON or OFF.
Enabling/disabling character echo
When character echo is enabled, all printable characters sent to the control port are echoed back to the control device (e.g., characters are echoed on the screen of the control device).
If character echo is disabled, characters are not echoed back to the control device.
The default for character echo is “enabled”.
To enable or disable character echo, use the EE and DE commands, respectively. You must have superuser or configuration privileges.
EE
DE
Enable character echo.
Disable character echo.
38
Chapter 4: Configuring the system
Configuring alarms
Using the commands in the Alarm Configuration Menu, you can configure the
M-PATH to enable or disable alarm messages, set thresholds and threshold evaluation times, and change the alarm deactivation period.
TIP
If you are using an SNMP network management tool, you can enable or disable four types of
SNMP traps (start, link, authentication, and enterprise traps) independently of whether you enable or disable alarms. See
.
■
■
■
■
As part of the overall system setup, you can specify the types of alarm messages output by the M-PATH. You can:
Enable or disable the generation of alarm messages.
Set the errored second (ES) and unavailable second (UAS) thresholds upon which
EER alarms are generated.
Specify the “sliding” time period for ES or UAS threshold evaluation.
Specify whether or not an alarm should be generated on an incoming yellow condition.
■
Specify the duration of the M-PATH alarm deactivation period.
Alarms are always issued in ASCII format.
This section describes how to set up the configuration parameters for alarms. If you enable alarms, you may also need to specify which control port you are using (the DCE or the
DTE port), so that alarms are output correctly. By default, the alarms are output to DCE.
The commands for configuring alarms are listed below (enter AC to see this display).
ALARM CONFIGURATION MENU
EAM / DAM - Enable/Disable Alarm Messages
EYL / DYL - Enable/Disable YELLOW Activating an Alarm
DACT:<n> - Alarm Deactivation time in seconds, n = 1..15
EST:<n> - Errored Second Threshold, n = 0 .. 900
UST:<n> - Unavailable Second Threshold, n = 0 .. 900
ST15/ ST60 - Set Threshold Timing to 15 or 60 Minutes
ACV - View Alarm Configuration
Configuring alarms
39
Viewing the current configuration
Before changing the alarm configuration parameters, you may want to look at the current settings. You can do this by executing the ACV command. This command displays the
View Alarm Configuration screen, as shown below.
VIEW ALARM CONFIGURATION
Message Alarms Activated Alarm Deactivation
LOS+AIS+OOF Seconds
---------- ---------------- ------------------
DISABLED +YEL+EER 15
EST UST Threshold
Timing
--- --- ---------
13 10 15
Field
Message
Alarms Activated
Alarm Deactivation
Seconds
EST, UST
Threshold Timing
Description
This field tells you if alarm messages are enabled or disabled.
Alarm messages, when enabled, are displayed in user
(ASCII) format.
This field tells you what types of conditions generate alarms.
LOS, AIS, and OOF always generate alarms; you can enable or disable alarms for EER and incoming yellow.
This field tells you how many seconds the M-PATH continues in an alarm state once the alarm condition has been cleared.
These fields tell you the alarm thresholds for errored second
(ES) and unavailable second (UAS), respectively. A zero (0) value means that EER alarms for ES or UAS have been disabled.
This field tells you the “sliding” time period the M-PATH uses for ES and UAS threshold evaluation. The period can be either 15 or 60 minutes.
40
Chapter 4: Configuring the system
Enabling/disabling alarm messages
Enabling/disabling alarms on incoming yellow
The M-PATH outputs an alarm message to your control device when it enters an alarm state. This message identifies the alarm type, the time and date of the alarm occurrence, and the device name and address of the unit sending the message.
You can disable this alarm message output. For example, you may want to do this if you are using a “polling” program to monitor alarms on the devices in your network.
The default for alarm message output is “disabled”.
NOTE
Disabling alarm messages does not affect the other alarm reporting mechanisms in the
M-PATH, including the Alarm History report, the System Status report, SNMP traps, and
LED illumination.
To enable or disable alarm messages from the command line, use the EAM and DAM commands. You must have superuser or configuration privileges.
EAM
DAM
Enable alarm messages.
Disable alarm messages.
The M-PATH generates an alarm message if it detects an incoming yellow alarm code at the network interface, and thus notifies you of a far-end problem. If you do not want this notification, you can deactivate this alarm message. You might also want to deactivate this alarm message if you are using SF framing and are receiving bit patterns that generate a false yellow indication.
The default is to generate an alarm message on incoming yellow (enabled).
To enable or disable activation of an alarm on incoming yellow, use the EYL and DYL commands. You must have superuser or configuration privileges.
EYL
DYL
Enable alarm activation on incoming yellow.
Disable alarm activation on incoming yellow.
Configuring alarms
41
Setting the threshold for errored seconds
(ES)
You can specify that the M-PATH generate an EER alarm on excessive errored seconds
(ESs). This allows you to monitor the line for errors and detect problems that are not described by signal loss or out-of-frame alarms.
You set up an EER alarm on excessive ESs by using the EST command to specify the error threshold. You can specify a threshold value of 0 to 900, inclusive. A value of 0 disables EER alarm activation on errored seconds; a value of 900 means that an alarm will be generated if an ES occurs every second of a 15-minute time window (60 x 15).
You can set the time window to 15 minutes or 60 minutes by using the ST15 or ST60 command, respectively (see
page 43 ). The window is a “sliding” window.
The default threshold is 13 errored seconds and the default window is 15 minutes (~10
-8
).
To set the ES threshold, use the EST command. You must have superuser or configuration privileges. The command syntax is:
EST:n
n
Enter the number of ESs that must occur within the time window in order to activate an EER alarm. The allowed values are 0 to 900, inclusive. 0 disables EER alarm activation on an ES condition.
Setting the threshold for unavailable seconds (UAS)
If your line is experiencing chronically high error rates, you may elect to disable the errored second (ES) threshold and just use the unavailable second (UAS) threshold for generating EER alarms. This decreases the alarm sensitivity significantly, since a UAS occurs at the onset of ten consecutive severely errored seconds (SESs).
You use the UST command to specify the threshold used for generating an EER alarm on UASs. You can specify a threshold value of 0 to 900, inclusive. A value of 0 disables
EER alarm activation on unavailable seconds; a value of 900 means that an EER alarm will be generated if an unavailable second occurs every second of a 15-minute time window (60 x 15).
You can set the time window to 15 minutes or 60 minutes by using the ST15 or ST60 command, respectively (see
page 43 ). The window is a “sliding” window.
The default threshold is 10 unavailable seconds and the default time window is
15 minutes.
To set the UAS threshold, use the UST command. You must have superuser or configuration privileges. The syntax for the command is:
UST:n
n
Enter the number of UASs that must occur within the time window in order to activate an EER alarm. The allowed values are 0 to 900, inclusive. 0 disables alarm activation on a UAS condition.
42
Chapter 4: Configuring the system
Specifying the error threshold evaluation window
Setting the alarm deactivation time
You can specify a 15-minute or a 60-minute “sliding” time window for error threshold evaluation. If the specified error threshold is exceeded during this sliding window, the
M-PATH generates an EER alarm. Use the 15-minute window for increased error sensitivity; use the 60-minute window for a longer term view of line quality.
The following table relates evenly distributed bit error rates and the number of ESs that will occur in 15- and 60-minute time periods.
Error rate
1 x 10
-6
1 x 10
-7
1 x 10
-8
1 x 10
-9
ESs in 15 minutes
900
135
13
1
ESs in 60 minutes
—
540
54
5
The default window for threshold evaluation is 15 minutes.
To specify the sliding window for threshold evaluation, use the ST15 and ST60 commands. You must have superuser or configuration privileges.
ST15
ST60
Set the sliding window to 15 minutes.
Set the sliding window to 60 minutes.
You can program the M-PATH to remain in an alarm state up to 15 seconds after an alarm condition has cleared. This deactivation period applies to the following alarms:
■
■
■
■
■
NI LOS and TI LOS
NI AIS and TI AIS
NI OOF and TI OOF
NI YEL and TI YEL
NI EER and TI EER
It does not apply to:
■
ECF
The default alarm deactivation time is 15 seconds.
To set the alarm deactivation time, use the DACT command. You must have superuser or configuration privileges. The command syntax is:
DACT:n
n
Set the deactivation time from 1 to 15 seconds.
Configuring alarms
43
44
Chapter 4: Configuring the system
C H A P T E R
5
Configuring interfaces
This chapter covers the following topics:
■
■
■
■
Configuring the network interface
Configuring the terminal interface
Configuring the data port
Assigning channels
45
Configuring the network interface
Configure the network interface so that it is compatible with the T1 signal from the service provider; it provides the requested performance reports, remote loopbacks and alarms; and, optionally, it establishes a data link path for managing a far-end unit.
The M-PATH network interface should be configured for compatibility with the T1 signal received from the service provider.
You must set up the network interface parameters to match the requirements of your service provider. The framing format and line coding for the M-PATH must match the framing format and line coding for your T1 line. The defaults supplied by the M-PATH work for most applications.
All these commands apply to both the transmit and receive directions on the network interface.
The commands for configuring the network interface parameters are listed below. To view this menu, log into the unit you want to configure, then enter NC.
NI CONFIGURATION MENU
NSF/NESF/NERC - NI SF/ESF/Ericsson Framing Format
NAMI / NB8 - NI AMI/B8ZS Line Coding
EPRM / DPRM - Enable/Disable T1.403 PRM Generation out NI
FKA / UKA - Framed/Unframed Keep Alive
EYEL / DYEL: - Enable/Disable YELLOW Activation out NI
ADR54:<Trgt> - 54016 Address = C(CSU), D(DSU), or B(Both)
E54 / D54 - Enable/Disable 54016 Mode
Line Build Out
NL0 - 0.0 dB
NL1 - 7.5 dB
NL2 - 15.0 dB
NCV - View NI Configuration
You must set up the network interface parameters to match the requirements of your service provider. The framing format and line coding for the M-PATH must match the framing format and line coding of your T1 line. Further, the line build-out should always be left at 0.0 dB unless another value is specifically requested. Increased attenuation can interfere with the T1 service.
46
Chapter 5: Configuring interfaces
You can use the View Network Configuration display to see the current network interface settings. Enter NCV at the command line prompt.
VIEW NETWORK CONFIGURATION
Framing Line Code Line Build Out PRM Generation Keep Alive
------- --------- -------------- -------------- ----------
ESF B8ZS 0.0 dB DISABLED FRAMED 1’S
YEL Generation 54016 Address 54016 Mode
-------------- ------------- ----------
ENABLED EITHER DISABLED
Field
Framing
Line Code
Line Build Out
PRM Generation
Keep Alive
YEL Generation
54016 Address
54016 Mode
Description
This displays the current network framing: SF (super frame), ESF (extended super frame), or ERICS
(Ericsson-modified super frame).
This displays the current line coding: AMI or B8ZS.
This displays the state of line build-out at the network interface. Possible values are 0.0 dB, 7.5 dB, or
15.0 dB.
This displays the state of ANSI T1.403 Performance
Report Message (PRM) generation: ENABLED or DISABLED.
This displays the state of the Framed Keep Alive option: FRAMED 1’S or AIS. It is valid only for units with all DS0 channels assigned to the terminal interface.
This displays the state of yellow alarm generation at the network interface: ENABLED or DISABLED.
This displays the currently selected 54016 address filter: DSU, CSU, or EITHER.
This displays the state of 54016 transmission:
ENABLED or DISABLED.
Configuring the network interface
47
Specifying NI framing format
TIP
The following framing formats and line codes often go together: super frame and AMI
(NSF and NAMI); and extended super frame and B8ZS
(NESF and NB8) However, one does not depend on the other.
You must set the M-PATH network interface to recognize and transmit data in the same framing format used by the incoming T1 line. You can choose: super frame (SF; also known as D4), extended super frame (ESF), or Ericsson-modified super frame.
Note that if the incoming T1 line is in SF format, you may want to disable the M-PATH from generating alarms upon detection of incoming yellow at the network interface.
.
Also, the option of using the facility data link (FDL) for the Data Link path is available only if the NI framing format is set to extended super frame (ESF). See
“Selecting the IP network interface” on page 130 .
The default framing format is extended super frame (ESF).
Use the following commands to specify framing format. You must have superuser or configuration privileges.
NSF
NESF
NERC
Super frame
Extended super frame
Ericsson-modified super frame
Specifying NI line coding
You must set the M-PATH network interface to the line coding specified by your service provider. Two selections are available: AMI (alternate mark inversion) or B8ZS (binary 8 zeroes substitution).
The default line coding is B8ZS.
Use the following commands to specify line coding. You must have superuser or configuration privileges.
NAMI
NB8
AMI line coding
B8ZS line coding
48
Chapter 5: Configuring interfaces
Enabling/disabling
T1.403 loopback and
PRM generation
Specify the “keep alive” signal for the network interface
■
■
You can enable or disable the M-PATH from sending and receiving ANSI T1.403 performance report messages (PRMs). You should enable T1.403 PRMs if either of the following is true:
Your carrier requires T1.403 PRMs
You have a point-to-point application and you want to get far-end performance reports at the near end
When T1.403 mode is enabled, the M-PATH does the following:
■
■
■
Sends PRMs out the network interface to the far-end device
Receives PRMs from the far-end device (used to collect data for far-end reports)
Sets and resets remote loopbacks using T1.403-standard codes
When T1.403 mode is enabled, the M-PATH defaults to T1.403 standards for setting and resetting loopbacks, even if 54016 mode is enabled.
The default state is T1.403 mode disabled.
Use the following commands to enable or disable T1.403 mode. You must have superuser or configuration privileges.
EPRM
Enable sending and receiving ANSI T1.403 PRMs and loopback set and reset codes.
DPRM
Disable sending PRM messages to the network and disable all other activities defined by the standard.
This command has no effect unless all channels are assigned to the terminal interface.
If the terminal interface enters an out-of-frame (OOF) condition, the M-PATH keeps the network connection alive by sending the network a framed all-1s signal. This masks the presence of an alarm at the terminal end.
You can program the M-PATH to send the network an AIS alarm (unframed all-1s signal) when the terminal signal is out of frame. This generates an alarm at the far end.
The default “keep-alive” signal is a framed all-1s signal.
Use the FKA and UKA commands to specify the keep alive signal. You must have superuser or configuration privileges.
FKA
UKA
Send a framed all-1s signal.
Send AIS (unframed all-1s signal).
Configuring the network interface
49
Enabling/disabling yellow alarm output
Selecting the 54016 address
This command has no effect unless all channels are assigned to the terminal interface.
Yellow alarm output should be enabled only if the terminal equipment connected to the
M-PATH is incapable of generating a yellow alarm.
If yellow alarm output is enabled, the M-PATH generates and transmits the yellow alarm code toward the network any time an alarm condition is detected on the network interface.
The yellow alarm is transmitted two to three seconds after alarm conditions AIS, OOF or
LOS arise.
If the alarm output is disabled, the M-PATH will not generate a yellow alarm code.
The default for alarm generation on incoming yellow is disabled.
Use the following commands to enable or disable yellow alarm generation. You must have superuser or configuration privileges.
EYEL
DYEL
Enable generation of yellow alarm.
Disable generation of yellow alarm.
If 54016 mode is enabled, you can specify whether the M-PATH responds to 54016 requests addressed to a DSU, a CSU, or both. (See the next entry for procedures on enabling 54016 mode.)
The default is for the M-PATH to respond to both CSU and DSU requests. If you want the
M-PATH to respond only to DSU or CSU requests, set the 54016 mode appropriately.
Use the following command to specify the 54016 address mode. You must have superuser or configuration privileges. The command syntax is:
D
C
B
ADDR54:Trgt where Trgt is:
DSU
CSU both DSU and CSU
50
Chapter 5: Configuring interfaces
Enabling/disabling
54016 mode
Specifying transmit line build out attenuation
You can enable or disable the M-PATH from responding to requests that comply with the message format of AT&T TR54016, Issue 2. Enable 54016 mode when your service provider requests it.
When enabled for 54016, the M-PATH can do the following:
■
■
Respond to 54016 requests
Set and reset remote loopbacks using 54016 requests, if T1.403 is disabled (see
“Enabling/disabling T1.403 loopback and PRM generation” on page 49 ).
sent via the ESF facility data link.
The default is 54016 mode disabled.
Use these commands to enable or disable 54016 mode. You must have superuser or configuration privileges.
E54
D54
Enable 54016 mode.
Disable 54016 mode.
Your service provider may ask you to set the M-PATH to attenuate (reduce) the T1 signal at the network interface. Three line attenuation settings are available: 0.0 dB (no attenuation), 7.5 dB, or 15 dB.
The default line attenuation is 0.0 dB.
Use the following commands to specify line build out attenuation. You must have superuser or configuration privileges.
NL0
NL1
NL2
0.0 dB line attenuation
7.5 dB line attenuation
15.0 dB line attenuation
Configuring the network interface
51
Configuring the terminal interface
Configure the unit’s terminal interface so that its framing format, line coding, signal equalization, and idle code are all compatible with your terminal equipment.
You must configure the terminal interface of the M-PATH to make it compatible with the terminal equipment (T1 customer premise equipment) connected to it.
All these commands apply to both the transmit and receive directions on the terminal interface.
The commands for configuring the terminal interface parameters are listed below (enter
TC to see this display).
TI CONFIGURATION MENU
TSF/TESF/TERC - TI SF/ESF/Ericsson Framing Format
TAMI / TB8 - TI AMI/B8ZS TI Line Coding
TIDL:<c> - Idle Code, c = 00-FF Hex
TI Equalization
TE0 - 0 - 133 ft
TE1 - 133 - 266 ft
TE2 - 266 - 399 ft
TE3 - 399 - 533 ft
TE4 - 533 - 655 ft
TCV - View TI Configuration
52
Chapter 5: Configuring interfaces
Viewing the current
TI configuration
Before changing any terminal interface parameters, you may want to look at the current settings. To do this, enter TCV at the command line prompt. This produces a display similar to the one below.
VIEW TERMINAL CONFIGURATION
Framing Line Equalization Idle
Format Code Code
------- ---- ------------ ------
ESF B8ZS 0..133 ft 7F Hex
Field
Framing format
Line code
Equalization
Idle code
Description
This displays the current framing format applied to the terminal interface: SF (super frame), ESF (extended super frame), or ERICS (Ericsson-modified super frame).
This displays the current line coding applied to the terminal interface: AMI or B8ZS.
This displays the state of signal equalization at the terminal interface: 0..133ft, 133..266ft, 266..399ft,
399..533ft, or 533..655ft.
This displays the currently selected idle code. The range is 00 to FF hex.
Configuring the terminal interface
53
Specifying TI framing format
TIP
The following framing formats and line codes often go together: super frame and AMI
(NSF and NAMI); and extended super frame and B8ZS
(NESF and NB8).
However, one does not depend on the other.
You must set the M-PATH terminal interface to recognize and transmit data in the same framing format used by the terminating customer premises equipment, usually multi-channel radio equipment in a CDPD or cellular voice application. wireless radio T1 channel bank or digital PBX. You can choose: super frame (SF; also known as D4), extended super frame (ESF), or Ericsson-modified super frame.
The default framing format is extended super frame (ESF).
Use the following commands to set the framing format applied at the terminal interface.
TSF
TESF
TERC
Super frame
Extended super frame
Ericsson-modified super frame
Specifying TI line coding
You must set the M-PATH terminal interface to the same line coding used by the customer premises equipment. Two selections are available: AMI (alternate mark inversion) or B8ZS (binary 8 zeroes substitution).
The default line coding is B8ZS.
Use the following commands to specify line coding. You must have superuser or configuration privileges.
TAMI
TB8
AMI line coding
B8ZS line coding
Specifying TI idle code
You can specify the eight-bit idle code that is put into the unused DS0 channels of the terminal interface. The code may have any hex value between 00 and FF.
Whenever an out-of-frame condition occurs at the network interface, the M-PATH CSU puts the idle code into all channels assigned to the terminal interface.
The unit continuously transmits the idle code on any NI channel assigned to “idle”.
The default idle code is 7F hex.
Use the TIDL command to specify the eight-bit idle code. You must have superuser or configuration privileges. The command syntax is:
TIDL:c
c
Enter a hex number with a value between 00 and FF.
54
Chapter 5: Configuring interfaces
Specifying TI signal equalization
If the cable between the M-PATH and the customer premises equipment is longer than
133 feet, you may need to boost the signal level being output from the terminal interface.
By using the TEn commands, you can specify that the terminal interface outputs a DSXlevel signal equalized for cable lengths up to 655 feet.
The default equalization setting is 0.
Use the following commands to equalize the T1 signal at the terminal interface. You must have superuser or configuration privileges.
TE0
TE1
TE2
TE3
TE4
0 - 133 feet
133 - 266 feet
266 - 399 feet
399 - 533 feet
533 - 655 feet
Configuring the terminal interface
55
Configuring the data port
You can change many characteristics of the data port, including timing, physical interface, idle character, and loss-of-signal indicator. Changing these parameters often compensates for differences between the near-end M-PATH unit and the data terminal equipment or far-end unit.
You must configure the data port to match the configuration of the data terminal equipment (DTE) to which it is attached.
Most applications can use the default values. “Tail” circuits, long DTE cables at high data rates, and perhaps other situations identified by your technical support representative may require changing the settings from their default values.
The commands for configuring the data ports are listed below. To view this menu, log into the unit you want to configure, then enter DC.
DATA PORT CONFIGURATION MENU
EDI<n> / DDI<n> - Enable/Disable Data Inversion at Data Port, n=1
INTF<n>:<intf> - Interface at Data Port, n=1
intf = V (V.35 72xxx), E (EIA-530),
D (V.35 DataSMART 78xxx Compatible)
SCLK<n>:<clk> - Source Clock at Data Port, n=1
clk = I (Internal), E (External)
TCLK<n>:<cmd> - Transmit Clock Inversion at Data Port, n=1
cmd = E (Enable), D (Disable)
RCLK<n>:<cmd> - Receive Clock Inversion at Data Port, n=1
cmd = E (Enable), D (Disable)
IDL<n>:<char> - Idle Character at Data Port, n=1
char = 7E, 7F, FF
DPLOS<n>:<los> - LOS Input Signal at Data Port, n=1
los = R (RTS), D (DTR), B (Both), N (No Processing)
56
Chapter 5: Configuring interfaces
Viewing the current data port configuration
Before changing any data port parameters, you may want to look at the current settings.
To do this, enter DCV at the command line prompt. This produces a display similar to the one shown below.
VIEW DATA PORT CONFIGURATION
Port 1
--------
Data Inversion DISABLED
Interface V.35
Source Clock INTERNAL
Tx Clock Invert DISABLED
Rx Clock Invert DISABLED
Idle Character FF
LOS Input RTS
Field
Data Inversion
Interface
Source Clock
Tx Clock Invert
Rx Clock Invert
Idle Character
LOS Input
Description
This tells you whether or not data inversion is enabled at the data port. If inversion is enabled, the data is inverted in both directions (i.e., the data from the DTE is inverted before being transmitted to the network, and vice versa).
This tells you the electrical interface specified for the data port: V.35 cable-compatible with DataSMART
72000 series (default); EIA-530; or V.35 cable- compatible with DataSMART 78000 series.
This tells you which clock signal is being used to clock in transmit data at the data port: INTERNAL or EXTERNAL.
This tells you whether or not transmit clock inversion is enabled at the data port. If inversion is enabled, transmit data is sampled on the rising edge of the clock signal. If inversion is disabled, transmit data is sampled on the falling edge of the clock signal.
This tells you whether or not receive clock inversion is enabled. If inversion is enabled, receive data is changed on the falling edge of the clock signal. If inversion is disabled, receive data is changed on the rising edge of the clock signal.
This tells you the specified idle character for the data port: 7E, 7F, or FF hex.
This tells you which signals are currently being used to determine an LOS condition at the data port: RTS,
DTR, BOTH, or NONE.
Configuring the data port
57
Enabling/disabling data inversion
Specifying the data port electrical interface
These commands enable or disable data inversion at the data port. When you enable data inversion, all data received from the DTE is inverted: zeroes are changed to ones and ones are changed to zeroes before being transmitted to the network. Data received from the network is also inverted before being transmitted to the DTE. When data is inverted locally, it must also be inverted at the far-end device.
Data inversion is seldom necessary. It is sometimes used to resolve “ones density” problems caused by a high proportion of zeroes in the bit stream of the incoming or outgoing data.
The default state is data inversion disabled.
Use the following commands to enable or disable data inversion. You must have superuser or configuration privileges. The command syntax is:
EDI1
DDI1
Enable data inversion at the data port.
Disable data inversion at the data port.
You can individually configure the data port interface to support:
■
■
V.35 data port cables (uses same cables as DataSMART 72000 series DSUs; default)
EIA-530 data port cables
Configure the port to support the interface requirements of the attached DTE device.
The V.35 option is compatible with the same cables as DataSMART 72000 series DSUs:
Kentrox cables 95xxx054, 95xxx073, and 95xxx074, or their equivalents.
Use the INTF command to specify the interface type. You must have superuser or configuration privileges. The command syntax is:
INTF1:cmd
cmd
Enter V for V.35 72000 series or E for EIA-530.
NOTE
The D option makes the data port compatible with cables for DataSMART 78000 series
DSUs. These cables are not sold with the M-PATH CSU.
58
Chapter 5: Configuring interfaces
Specifying data port clocking
You can specify the clock signal used to clock transmit (Tx) data at the data port (see
Figure 4). Two clock selections are available: internal or external.
Internal clocking (the default) means that the transmit data is clocked by the data port’s internal clock, which is derived from the M-PATH system source clock.
External clocking means that data is clocked by a signal received on the data port connector’s external clock pins (see
through
on
External clocking is typically used:
■
With long cables (exceeding 50-100 feet) at high data rates with DTE that supports an external clock signal
■
If the M-PATH unit is driving a tail circuit (see
“Specifying the system clock” on page 31
)
■
If the M-PATH unit is connected to a Cisco router
The normal operation of synchronous serial data ports provides for three clock signals (see
):
1
The DCE supplies the receive (Rx) clock signal synchronized with the receive
(Rx) data.
2
The DCE also supplies the transmit (Tx) clock signal. The DTE normally transmits its data synchronized to this signal. Most data terminal equipment uses this signal.
3
The external clock signal is regenerated by the DTE.
In
Figure 4 , the external clock signal is the Tx clock signal regenerated by the DTE
and synchronized with the DTE’s transmitted data. Usually you employ this option when you are receiving excessive data errors at the data port due to cable propagation delay. Propagation delay becomes a problem when you are using a long data cable (exceeding 50 - 100 feet) at high data rates.
NOTE
Not all data terminal equipment supports an external clock signal. You must have terminal equipment capable of supplying this signal, however, in order to use the M-PATH unit’s external data port clock option.
Configuring the data port
59
Figure 4—Clock signals at the data port
M-PATH CSU
Rx Data
Rx Clock
Data Port (DCE)
Tx Data
Tx Clock
External Clock (XCLK)
DTE
TIP
SCLK specifies data port clocking, not system clocking. System clocking is specified with the
CLK command.
Requires a DTE and cable capable of supplying XCLK
The default data port clock is internal.
Use the SCLK command to specify the data port clock. You must have superuser or configuration privileges. The command syntax is:
SCLK1:clk
clk
Enter E to specify an external clock source, or enter I to specify the internal clock source.
Enabling/disabling transmit clock inversion
You can invert the transmit (Tx) clock signal and, by doing so, change the clock edge being used to sample transmit (Tx) data at the data port (refer to
Transmit data is normally sampled on the falling edge of the transmit clock. If you invert the clock signal, data is sampled on the rising edge of the clock.
The inversion is done on the data port TCLK signal when internal source clocking is chosen and on the XCLK signal when external source clocking is chosen.
Sampling data on the falling edge of the clock is standard; you will seldom need to invert the clock. If the far end is experiencing data errors, if the cable connecting the DTE to the data port is long enough to cause undue propagation delays, or if the clock signal has become inverted somewhere else in the network, then you may need to invert the clock edge.
The default state is transmit clock inversion disabled.
Use the TCLK command to invert the clock edge. You must have superuser or configuration privileges. The command syntax is:
TCLK1:cmd
cmd
Enter E to enable clock inversion, or enter D to disable clock inversion.
60
Chapter 5: Configuring interfaces
Enabling/disabling receive clock inversion
Specifying the data port idle character
You can invert the receive (Rx) clock signal and, by doing so, change the clock edge being
invert the clock signal, receive data is changed on the falling edge of the clock.
Changing receive data on the rising edge of the clock is standard; you will seldom need to invert the clock. If the local DTE is receiving data errors, if the cable connecting the data port and DTE is long enough to cause undue propagation delays, or if the clock signal has become inverted somewhere else in the network, you may need to invert the clock edge.
The default state is receive clock inversion disabled.
To enable or disable clock inversion, use this command:
RCLK1:cmd
cmd
Enter E to enable clock inversion, or enter D to disable clock inversion.
During certain alarm states and loopbacks, the M-PATH outputs an idle character on the
DS0 channels assigned to the data port. This idle character is transmitted to the network and to the DTE attached to the port. You can specify the value of this idle character as 7E,
7F, or FF hex.
The default idle character is FF. This value should work correctly for most equipment.
Some equipment may require 7E or 7F. These characters were chosen because FF is normally sent out by T1 equipment. It is also an abort character in HDLC, as is 7F. (They both have more than six consecutive ones.) The character 7E is the flag character (idle) in HDLC.
Use the IDL command to specify the idle character at the data port. You must have superuser or configuration privileges. The command syntax is:
IDL1:cmd
cmd
Enter 7E, 7F, or FF to specify the idle character.
Configuring the data port
61
Setting up DPLOS
(data port loss of signal) processing
You can specify which signals are monitored for LOS at the data port. You can monitor the RTS signal, the DTR signal, both signals, or neither signal.
Data port LOS can be used to identify cases where the M-PATH and network are operating correctly, but the DTE has failed, has lost power, or has been disconnected.
When a data port LOS condition occurs, the M-PATH fills the channels assigned to the data port with the idle character configured with the IDL1 command for transmission toward the network. DP LOS is reported using the System Status (S) command (see
“Examining system status” on page 101 ).
The default is to monitor RTS for LOS at the data port.
Use the DPLOS command to specify the signal(s) monitored for data port LOS. You must have superuser or configuration privileges. The command syntax is:
D
B
DPLOS1:cmd
cmd is one of the following:
R
Monitor RTS for LOS. This should work correctly with most equipment. Some equipment or cables may need a different setting.
Monitor DTR for LOS.
N
Monitor RTS and DTR for LOS. With this setting, the unit detects a
LOS if both RTS and DTR are low. If either signal is high, LOS is not detected.
Disable DPLOS monitoring. The M-PATH ignores RTS and DTR at the port and assumes that the data port is connected and receiving valid data.
62
Chapter 5: Configuring interfaces
Assigning channels
The T1 line provides access to 24 DS0 channels on the network interface. You can assign some of these channels to the data port, assign others to the terminal interface, and leave other channels idle. One of the data port channels or idle channels can also be used for a data link to a remote unit. The M-PATH has two tables where you can keep separate IP management configurations to handle differing demands on the
T1 line.
Topics in this section
In this section, you’ll find the following topics:
■
“Planning the channel assignment”
before setting up the unit, and why it’s important
■
■
■
“Methods of entering channels” - editing and loading channel configuration tables
“Five typical channel assignments”
- the most commonly used channel setups
“Rules for assigning channels” and
“How to assign channels” - you’ll need to read
about these topics if you’re not using one of the five typical channel setups
Planning the channel assignment
The T1 line has 24 channels you can assign to the terminal interface, data port, or idle.
In some simple cases, you may not need to plan the channel assignment. For example, the default configuration for M-PATH units maps each network interface channel to its corresponding channel on the terminal interface.
NOTE
It is important to have a channel assignment plan, especially when mapping channels to the data port. The M-PATH Configuration Worksheets can help you assign channels.
Consider these factors when assigning channels:
■
If you are using a DS0 channel to support an IP management data link to a remote
unit, include it in the plan. (The setups in “Five typical channel assignments”
all use the IP data link on a DS0 and use the NETIF command to configure it; see
“Selecting the IP network interface” on page 130
.) The data link can use an idle channel or a data port channel. An error message is displayed if you attempt to assign the data link to a channel used by the terminal interface. Also, if the data link uses a data port channel, data port timing (see
■
In a point-to-point connection, the units at both ends of the T1 line must have identical channel assignments. This is true whether you are using the terminal interface, the data port, or a remote data link. Your network service provider may have to tell you what channel assignments to use.
■
In some rare cases, your configuration may not guarantee sufficient ones density at the network interface to avoid setting off alarms or losing synchronization. This might happen when your DTE is inactive, even though you haven’t idled it. The solution may be to assign a set of alternating channels to the data port, and then configure the unassigned channels to outputting an idle code with high ones density.
Assigning channels
63
Methods of entering channels
When you assign channels using the command line interface, you are actually editing a table, which you load into hardware in a separate step. The M-PATH CSU has two such tables, so that you can keep two separate configurations. This feature is useful at sites where, for instance, you have separate configurations for day-time and night-time traffic.
illustrates how the configuration table editing commands affect the channel map used by the M-PATH CSU.
Figure 5 - Flow chart for configuration table editing commands
ADP1
ANI
Configuration
Table A
CPAB
CPBA
Configuration
Table B
BDP1
BNI
LXA LXB
Table X
(Executing
Channel Map)
The ADP1 and ANI commands edit Configuration Table A.
The BDP1 and BNI commands edit Configuration Table B.
The CPAB command copies Table A to Table B, and the CBPA command copies Table B to Table A.
Once Table A has been completely edited, the LXA command loads it into the executing channel map. The LXB command does the same for Table B.
If you change a working configuration so that the terminal interface or the data link move from one channel to another, make sure you have resolved the conflict for both of your unit’s configuration tables, or an error will occur when you try to load a table which has become invalid.
64
Chapter 5: Configuring interfaces
Five typical channel assignments
The rest of this chapter contains network interface channel assignments for five typical
M-PATH applications, as well as background on setting up a custom channel assignment.
Detailed procedures for setting up all these applications are in Chapter 6 of the M-PATH
Installation Guide. Typical applications are:
■
Channels 1-23, CSU using Robbed Bit Signaling; Channel 24, IP management data link @64 Kbps: see
“23-channel CSU, Robbed Bit Signaling, one DS0 for IP management” on page 66
.
■
Channels 1-22, CSU using Robbed Bit Signaling; Channel 23, Data Port 1 @ 56
Kbps; Channel 24, IP management data link @64 Kbps: see “22-channel CSU,
Robbed Bit Signaling, 56 Kbps data port, one DS0 for IP management” on page 67 .
■
Channels 1-23, CSU using Common Channel Signaling (CCS); Channel 24, IP management data link @64 Kbps; also used for ISDN PRI or data equipment on terminal
interface: see “23-channel CSU, Common Channel Signaling, one DS0 for IP management” on page 68
.
■
Channels 1-23, Data Port 1 @1536 Kbps (24 x 64 Kbps); Channel 24, IP management data link @64 Kbps: see
“23-channel DSU, 1472 Kbps, one DS0 for IP management” on page 69
.
■
Fractional T1 DSU @256 Kbps (4 x 64 Kbps); Channel 24, IP management data link
@64 Kbps: see
“Fractional T1 DSU, 256 Kbps, one DS0 for IP management” on page
.
■
None of the above: see
.
“Rules for assigning channels” on page 71 and
Assigning channels
65
23-channel CSU,
Robbed Bit
Signaling, one DS0 for IP management
This application sets Channels 1-23 to the terminal interface (voice-type channels). Channel 24 is reserved for IP management at 64 Kbps.
This application uses Robbed Bit Signaling, also called A-B bit or ABCD bit signaling or
Channel-Associated Signaling (CAS). Use it if your terminal equipment requires the SF or
ESF signaling bits.
Sample application
Radio
Cell Site Management Site
23 DS0 on T1
M-PATH CSU in shelf
DCS
TI NI T1
Switch
1 DS0 management
Channel map diagram
Terminal
Interface
1V
2V
3V
.
.
.
22V
23V
24 IDLE
Network
Interface
1
2
3
.
.
.
22
23
24 IDLE
■
The ANI1-23:V command assigns NI channels 1-23 to the terminal interface, voice-type channels.
The ANI24:I command sets NI channel 24 to idle.
■
■
The NETIF D:24,64 command assigns idle channel 24 to a 64 Kbps IP management data link.
The procedure for configuring this application is in Chapter 6 of the M-PATH
Installation Guide.
66
Chapter 5: Configuring interfaces
22-channel CSU,
Robbed Bit
Signaling, 56 Kbps data port, one DS0 for IP management
This application sets Channels 1-22 to the terminal interface (voice-type channels) and assigns Channel 23 to the M-PATH data port at 56 Kbps. Channel 24 is reserved for IP management at 64 Kbps.
This application uses Robbed Bit Signaling, also called A-B bit or ABCD bit signaling or
Channel-Associated Signaling (CAS). Use it if your terminal equipment requires the SF or
ESF signaling bits.
Sample application
Messaging
System
Radio
22 DS0 on T1
M-PATH CSU in shelf
TI NI
DCS
T1
DP1
1 DS0
Messaging
Equipment
Cell Site Management
Site
NMS
Voice
Switch
Channel map diagram
Terminal
Interface
1V
2V
3V
.
.
.
22V
23V
24 IDLE
Network
Interface
1
2
3
.
.
.
22
23
24 IDLE
Data Port 1
■
The ANI1-22:V command assigns network interface channels 1-22 to the terminal interface, voice-type channels.
■
The ADP1:56,23 command assigns network interface channel 23 to the data port at
56 Kbps.
The ANI24:I command sets network interface channel 24 to idle.
■
■
The NETIF D:24,64 command assigns the idle channel 24 to a 64 Kbps IP management data link.
The procedure for configuring this application is in Chapter 6 of the M-PATH
Installation Guide.
Assigning channels
67
23-channel CSU,
Common Channel
Signaling, one DS0 for IP management
This application sets Channels 1-23 to the terminal interface (data-type channels). Channel 24 is reserved for IP management at 64 Kbps.
Use it for Common Channel Signaling (CCS) or ISDN PRI applications, if you have data equipment on the terminal interface, or if a clear channel is required.
Sample application
Radio
Cell Site Management Site
23 DS0
M-PATH CSU in shelf
DCS
T1
T1
Switch
1 DS0 management
Channel map diagram
Terminal
Interface
1D
2D
3D
.
.
.
22D
23D
24 IDLE
Network
Interface
1
2
.
.
.
3
22
23
24 IDLE
■
The ANI1-23:D command assigns NI channels 1-23 to the terminal interface, data-type channels.
The ANI24:I command sets NI channel 24 to idle.
■
■
The NETIF D:24,64 command assigns the idle channel 24 to a 64 Kbps IP management data link.
The procedure for configuring this application is in Chapter 6 of the M-PATH
Installation Guide.
68
Chapter 5: Configuring interfaces
23-channel DSU,
1472 Kbps, one DS0 for IP management
This application assigns Channels 1-23 to the data port, which is connected to messaging equipment. All 23 data port channels are set to 64 Kbps for a total of 1472 Kbps at the data port. Channel 24 is reserved for IP management at 64 Kbps.
Sample application
Messaging
System
Messaging
Equipment
23 DS0
M-PATH CSU in shelf
DP1
NI T1
DCS
Cell Site Management
Site
NMS
Channel map diagram
Network
Interface
1
2
3
.
.
.
22
23
24 IDLE
...
Data Port 1
■
The ADP1:64,1-23 command assigns network interface channels 1-23 to the
M-PATH CSU’s data port at 64 Kbps.
The ANI24:I command sets NI channel 24 to idle.
■
■
The NETIF D:24,64 command assigns the idle channel 24 to a 64 Kbps IP management data link.
The procedure for configuring this application is in Chapter 6 of the M-PATH
Installation Guide.
Assigning channels
69
Fractional T1 DSU,
256 Kbps, one DS0 for IP management
This application assigns network interface channels 1-4 to the data port. Each data port channel is set to 64 Kbps for a total of 256 Kbps at the data port. All other channels are idle. You can change the number of active channels in the fractional T1 to any number from 1 to 23.
You can use any idle channel for an in-band data link; we use Channel 24 for consistency with the other examples.
Sample application
Messaging
System
Messaging
Equipment
4 DS0
M-PATH CSU in shelf
DP1
NI T1/
FT1
DCS
Cell Site Management
Site
NMS
Channel map diagram
Network
Interface
1
2
3
4
5 IDLE
.
.
.
22 IDLE
23 IDLE
24 IDLE
Data Port 1
■
The ADP1:64,1-4 command assigns network interface channels 1-4 to the M-PATH
CSU’s data port at 64 Kbps.
■
The ANI5-24:I command sets NI channels 5-24 to idle.
NOTE
To assign more or fewer channels to the data port, modify the above commands. For example, to assign eight channels to the data port, the commands are ADP1:64,1-8 and
ANI9-24:I.
■
The NETIF D:24,64 command assigns the idle channel 24 to a 64 Kbps IP management data link.
The procedure for configuring this application is in Chapter 6 of the M-PATH
Installation Guide.
70
Chapter 5: Configuring interfaces
Rules for assigning channels
Rules for assigning data port channels
When assigning network interface channels to the data port and the terminal interface, the channels for the data port must be grouped. Within the group, the channels can be contiguous or alternating. If the channels in the group are alternating, the intervening channels are assigned to idle.
For instance, if data port 1 has eight channels to assign, you can assign them in a single group of contiguous channels (1-8), but not two groups on contiguous channels (1-4 and
10-13). Or, if you want to use alternating channels, you can assign them to a single group of alternating channels (2, 4, 6, 8, 10, 12, 14), but not to two groups of alternating channels
(2, 4, 6, 8 and 14, 16, 18, 20).
The idle code MUST contain sufficient ones to keep the circuit synchronized. When you specify the idle code, make sure you select a code with sufficient ones.
NOTE
Besides assigning the channels, you must also specify the data rate for the data port. See
“Assigning DS0 lines to a port” on page 72 .
Rules for assigning terminal interface channels
The rules for channel assignments between the network interface and the terminal interface are:
1
The channel number on the TI side must match the channel number on the NI side.
2
If equipment connected to the TI requires the super frame signaling bits or the extended super frame signaling bits to be passed through the M-PATH CSU, set the channel type to V (voice).
3
If the equipment connected to the TI requires a 64 Kbps clear channel (no signaling bits), set the channel type to D (data).
4
You do not need to group the TI channels in any special way, as is the case with data port channels.
5
If you use an alternating scheme, you can assign a single data port channel to a channel in between two TI channels.
■
■
Compatible and incompatible configurations
The following formats and settings usually go together:
Super frame, AMI, 56 Kbps channel data rate, one channel on the data port.
Extended super frame, B8ZS, 64 Kbps channel data rate, aggregated channels on the data port.
The following format-and-setting combination is not recommended:
■
AMI, 64 Kbps channel data rate (this does not guarantee ones density on the
T1 line).
Assigning channels
71
How to assign channels
You set channel bandwidth using the commands listed in the Fractional T1 Configuration menu. To display this menu, enter FC.
FRACTIONAL T1 CONFIGURATION MENU
<table>DP<port>:<rate>[,<nicn>]
- DP=Assign NI Channel Map for Data Port
table A/B
port 1
- Tables A or B Containing Channel Assignment
- Data Port Number
rate 56/64
nicn 1 .. 24
- Channel Rate in 1000 bps
- NI Channel numbers assigned to Data Port or
1,3,5,...
- Can be alternating DS0 channel numbers or
1-24 - a contiguous range.
<table>NI<nicn>:<ticn>,<nicn>:<ticn>, ...
table A/B
- NI=Assign NI Channels to TI or IDLE
- Tables A or B Containing Channel Assignment
nicn 1 .. 24
ticn V,D,I
- NI Channel numbers
- Voice/Data on TI Channel or I for Idle
CPAB / CPBA
LXA / LXB
TAV / TBV
TXV
- Copy A to B or B to A
- Load and Execute Table A or B
- View Table A or B
- View Executing Channel Assignment
Assigning DS0 lines to a port
This command allows you to edit the data port channel assignments and the data rate in either table A or table B. You must have superuser or configuration privileges to use this command.
tableDP1:rate[,nicn]
table rate
Specify A or B to indicate which table you want to edit.
Specify either 56 or 64 Kbps.
nicn
Specify the NI channels that you want to assign to the data port, where nicn is one of the following:
A single channel number (for example, 11).
A range of channel numbers, delimited by a dash
(for example, 2-8).
A series of odd or even channel numbers, delimited by a comma
(for example, 7,9,11 or 10,12,14).
72
Chapter 5: Configuring interfaces
Assigning network channels to the terminal interface or IDLE
Use this command to:
■
■
■ assign network (NI) channels to the terminal interface (TI) idle out unused channels on the NI assign “voice” or “data” type to TI channels
Note that the assignments must be “straight across”; the NI channel must go to the TI channel of the same number.
NOTE
You can not assign the data link to a remote M-PATH unit over a channel that is assigned to the terminal interface.
You must have superuser or configuration privileges to use this command.
tableNIni_channel:[d,v,i]
tableNIni_channel_range:[d,v,i]
tableNIni_single_channel:[d,v,i]
table
Specify A or B to indicate which table you want to edit.
ni_channel_range
Specify a range of NI channels, delimited by a dash.
single_channel:i
Set a single channel to idle. For instance, 3:i idles NI channel 3.
Assigning channels
73
Viewing the contents of table A and B
You can inspect the contents of the tables by using the TAV and TBV commands. You must have superuser or configuration privileges.
TAV
TBV
Display the contents of table A.
Display the contents of table B.
The TXV command shows the current assignments. TXV does not require any privileges to use.
TXV
Display the current channel assignments on the M-PATH.
To look at Table A, for example, enter the TAV command from any prompt. The Table A report will look something like the display shown below. (This channel assignment is illustrated in example 2,
“22-channel CSU, Robbed Bit Signaling, 56 Kbps data port, one
DS0 for IP management” on page 67 .) The report displays the mapping of NI channels in
two different ways. The top of the report lists the ports in the left column and shows rate and all channels assigned to that port to the right. The bottom of the report lists every channel and shows its assignment and how it is configured (for idle, TI voice, TI data, data port, or data link).
VIEW TABLE A OF THE FRACTIONAL T1 CONFIGURATION
MAP RATE TOTAL NI CHANNELS
---- ---- ----- ------------------------------------------------
TI - - 1, 2, 3, 4, 5, 6, 7, 8, 9,10,11,12,13,14,15,16,
17,18,19,20,21,22
DP1 56 56 23
IDLE - - 24
DLNK 56 24
NI MAP NI MAP NI MAP NI MAP NI MAP NI MAP NI MAP NI MAP
------- ------- ------- ------- ------- ------- ------- -------
1:TI V 2:TI V 3:TI V 4:TI V 5:TI V 6:TI V 7:TI V 8:TI V
9:TI V 10:TI V 11:TI V 12:TI V 13:TI V 14:TI V 15:TI V 16:TI V
17:TI V 18:TI V 19:TI V 20:TI V 21:TI V 22:TI V 23:DP1 24:IDLE
CONFIGURED NETIF USES DS0 TS 24
Field Description
MAP
RATE
This identifies the port.
TI indicates the terminal interface.
DP1 indicates the data port.
IDLE indicates an idle channel.
DLNK indicates an idle channel is assigned to the IP management data link.
DLDP indicates a channel is assigned to both the data port and the data link.
This tells you data rates, 56 or 64 Kbps, for each DS0 channel currently assigned to the data ports or IP management data link (see
“Selecting the IP network interface” on page 130
). The Data Link channel can also have a data rate of 8Kbps when it uses a DS0 channel assigned to the data port.
TOTAL This displays the total bandwidth assigned to the data port (where bandwidth is determined by multiplying the rate per channel by the number of channels assigned to the port). If a 64 Kbps channel is assigned to the data port and data link at the same time, its bandwidth is reduced to 56 Kbps and the Data Link rate field displays 8Kbps.
NI CHANNELS This lists channel assignments by ports.
NI MAP This lists channel assignments by channel number.
TI V indicates a voice-type terminal interface channel.
TI D indicates a data-type terminal interface channel.
For the other values, see the MAP field in this table.
CONFIGURED/
PROPOSED
NETIF USES...
This displays the type of in-band data link used by the IP management data link channel.
NO DATALINK indicates no in-band data link is used.
DS0 TS nn DATALINK indicates the IP management data link uses time slot nn, where nn is between 1 and 24.
FDL DATALINK indicates the facility data link is used for
IP management.
CONFIGURED indicates the current setting.
PROPOSED indicates the setting was changed in the current session, but has not yet been saved.
Assigning channels
75
Configuring the interfaces from a table
These commands load a configuration from a table into the hardware, which then operates as configured. You must have superuser or configuration privileges.
LXA
LXB
Load configuration from Table A.
Load configuration from Table B.
Copying one table into another
You can copy the contents of one table into the other table using the CPAB and CPBA commands. You must have superuser or configuration privileges.
CPAB
CPBA
Copy Table A to Table B.
Copy Table B to Table A.
76
Chapter 5: Configuring interfaces
C H A P T E R
6
Performance monitoring
This chapter describes how to monitor the performance of the incoming T1 circuits by using the various reporting facilities available from the M-PATH command line.
Though this chapter describes different reports, learning to understand them is simplified by the fact that many are similar in format. For instance, all these reports are similar:
■
■
■
■
User NI report
User TI report
Far-end report
Carrier NI report
Because of the similarities of these reports, the easiest way to learn about them is to learn the most commonly-used report first, which is the User NI report. Descriptions of all other reports of the same type refer back to the description of the User NI report.
This chapter also describes other reports:
■
■
■
■
User NI Statistical Performance report
User TI Statistical Performance report
Alarm History report
Security History report
This chapter is organized as follows:
■
■
The first section shows how to access the various command line reports.
The other sections show how to interpret the command line reports.
Though the reports described here contain some information about alarm status, the Sys-
.
NOTE
You can also monitor performance of the incoming T1 circuits by using an SNMP network management system and accessing the M-PATH MIBs.
77
Accessing the reports
The Reports menu lists commands for accessing reports. To see the list, enter R at the command line.
REPORTS MENU
UNSR / UNLR
UTSR / UTLR
CNSR / CNLR
FESR / FELR
- User NI Short/Long Performance Report
- User TI Short/Long Performance Report
- Carrier NI Short/Long Performance Report
- Far End PRM Short/Long Performance Report
NSR:[z]
TSR:[z]
AHR
SHR
- User NI Statistical Performance Report
- User TI Statistical Performance Report
z = Display Report then Zero Counts (Optional)
- Alarm History Report
- Security History Report
PL:<len|style> - Set Page Length, <len> = 20 .. 70 (or 0 = Off), or
<style> = P (Page Break), M (More), or V (View)
TIP
For information on these and other reports, see the sections on interpreting performance reports starting on
.
To display any report, simply enter the appropriate command from the command line.
You do not need any special privilege level.
Most reports have a long or short version. The long version differs from the short version only in that it includes a breakdown of the performance information for the previous 24 hours, shown in 15-minute intervals.
For example, use these commands to display the User NI reports.
UNSR
UNLR
Display the short version of the User NI report.
Display the long version of the User NI report.
Using the Z option with the NSR and TSR commands
The NI and TI Statistical reports provide performance data similar to the NI and TI User reports, plus they provide in-service data about total errors counted at their respective interfaces. By using the Z option with the report command, either NSR or TSR, you can clear the error counts whenever the report is displayed. This way, the next time you display the report it will show just the errors accumulated since the last time you displayed the report.
The command syntax is:
NSR [Z]
TSR [Z]
Z
Clear the in-service data from the report, once the report is displayed.
78
Chapter 6: Performance monitoring
Clearing the performance database
Formatting the reports
The PL command formats all the reports, either for a printer or a terminal. You can set the page length and select either “page break” for output to a printer, or “more prompt” for output to a screen. A page length of 0 disables both page breaks and prompting.
By default, no page length is specified and page breaks and prompting are disabled. If you enter a page length, the command defaults to a “more prompt” (M) unless you specify
“page breaks” (P).
The PL command syntax is:
PL:len|style
len style
Specify the page length as 0, 20 ... 70. 0 disables page breaks and prompting.
Specify P for “page break,” M for “more prompt,” or V to display the current settings without changing anything.
For example, to fit a report on a 22-line monitor, enter:
PL:22:M
Any time you change the length or style parameter, a display will show the state of the settings after the change.
There are six actions you can take that will clear report data.
Resetting the date or time on the M-PATH using the ST or SD commands (see
“Setting date and time” on page 28
) clears the performance data and resets counters. Using the
ZALL command (see “Zeroing all counters” on page 34 ) has the same effect, without
changing the time.
The SD, ST, and ZALL commands clear data from all reports except the Carrier NI reports, the Alarm History report, and the Security History report.
■
■
■
The following actions will clear data from all reports, including the Carrier NI and history reports:
Cycling power to the M-PATH
Using the BOOT command (see
“Obtaining new system software” on page 35 )
Resetting the M-PATH to its defaults with the RSD command (see
“Resetting to default values” on page 36
). This command causes you to lose the current alarm history data, performance data, and configuration settings. Use the RSD command with caution.
This information is summarized in Table 5 on page 36
.
Accessing the reports
79
Interpreting the User NI and the User TI reports
The M-PATH monitors the received signal on a T1 line (both the network interface and the terminal interface) for a variety of different error conditions (see
counts the errors and then uses the count to determine the quality of the 1-second interval during which the errors occurred.
For each time interval, the M-PATH tallies the counts and displays the information in the reports. The reports also show the error conditions and whether or not an alarm was present.
The following figure shows an example of the User NI Short Performance Report
(UNSR). The UTSR report is very similar.
KENTROX MPATH 53n - USER NI SHORT PERFORMANCE REPORT
ADDRESS: 00:00:000 NAME: PORTLAND,OR
DATE: MAR 14, 1995 TIME OF DAY: 00:27
STATUS CODES: C=CRC6, B=BPV, L=LOS, O=OOF, E=EER, A=AIS, Y=YEL,
@=ALARM ACTIVE, T=TEST ACTIVE
SECOND OF INTERVAL: 757 OF 900 COMPLETED INTERVALS:96 OF 96
G.821 G.821 G.821 G.821
EE ES BES SES UAS CSS DM STATUS
------ ----- ----- ----- ----- ----- ---- ----------
CUR SEC 0 0 0 0 0 0 0 E @
PRE SEC 0 0 0 0 0 0 0 E @
CUR 15-MIN 3712 71 63 0 0 0 2 C E @
PRE 15-MIN 0 0 0 0 0 0 0 E @
CUR 24-HR 0 0 0 0 0 0 0 E @
03/13/95 2485 117 69 7 14 3 2 C O AY@
03/12/95 0 0 0 0 86400 0 0 L @
03/11/95 999999 86400 2139 0 0 72 1440 C E Y@
03/10/95 3296 459 192 17 313 3 7 C OE @T
03/09/95 4 1 1 0 0 1 0 C @
03/08/95 1 1 0 0 0 0 0
03/07/95 1 0 0 0 0 1 0
80
Chapter 6: Performance monitoring
Time intervals in the reports
The reports show the performance data for the current second, the previous second, the current 15-minute period, the previous 15-minute period, the current day, and the previous seven days.
Each day is broken into ninety-six intervals of 15 minutes each. Interval one starts at 00:00
(midnight), interval two at 00:15, interval three at 00:30, and so on.
CUR 15-MIN refers to the performance data tabulated so far for the 15-minute interval.
For instance, in the previous figure, the third row shows the performance for the
15-minute interval starting at 00:15 (notice that the time of day is 00:27).
Each 15-minute interval consists of 900 seconds. The field in the header labeled “SEC-
OND OF INTERVAL” shows how many seconds into the interval the measurement extends. In the example, the data has been collected for 757 seconds of the current interval.
In a report, CUR 24-HR refers to a rolling 24-hour period. In other words, it is the previous 96 15-minute intervals. The field labeled “COMPLETED INTERVALS” indicates whether or not the M-PATH has been running for the full ninety-six intervals that make up a 24-hour day. Unless the M-PATH was recently restarted, the completed intervals display should always read “96 OF 96.” The 24-hour count may show less than 96 15-minute intervals if it was cleared within the last 24 hours.
The report also shows the performance data for each of the last seven days, if the
M-PATH has been powered up for seven days; otherwise, it shows the data collected since the M-PATH was last powered up. For instance, if the M-PATH has only been powered up for 48 hours, the report will only have a listing for two days, since only two days have been completed so far.
If one of the time intervals shows a row of dashes (-), that means that either the M-PATH was powered down during that period or data has not yet been collected for that period.
A zero (0) in a field indicates that the unit was collecting data but no events happened that would cause the count for that field to be incremented.
Time intervals and the long report
The long report (use the UNLR or UTLR command) shows the same information as the short report and also includes performance data for each complete 15-minute interval in the current 24 hours (that is, the previous ninety-six 15-minute intervals). If not all of the
15-minute intervals are listed, it means the M-PATH has not been on for 24 hours. A dash displayed in a field means that the unit was powered down for that period.
The following figure shows the additional information provided by the long version of the
User NI report (UNLR).
TIME ACCUMULATED
02:30 0 0 0 0 0 0 0
02:15 0 0 0 0 0 0 0
02:00 0 0 0 0 0 0 0
01:45 0 0 0 0 0 0 0
01:30 0 0 0 0 0 0 0
01:15 0 0 0 0 0 0 0 E @
01:00 2746 21 20 0 0 0 2 C E @
00:45 104472 523 523 0 233 7 9 C LOEA @
00:30 4009 76 68 0 0 0 2 C E @
00:15 0 0 0 0 0 0 0 E @
Interpreting the User NI and the User TI reports
81
For each time interval there are eight types of performance measurements. These measurements are described below.
Field header Definition
EE
ES
BES
This field shows the number of error events (EEs) that have occurred, up to a maximum of 999,999.
If the line uses ESF framing, the following error conditions cause a single EE to be counted: a transition to the LOS condition a transition to the AIS condition a transition to the OOF condition a second with a controlled slip (also referred to as a frame slip)
1 a BPV error a CRC6 error
If the line uses SF framing, an EE is the number of BPVs per second.
This field lists the number of errored seconds (ESs) that have occurred. If the line uses ESF framing, an ES is any second that is not a UAS that contains: an LOS condition, or an AIS condition, or an OOF condition, or one or more CRC6 or BPV errors.
If the line uses SF framing, an ES is any second with a BPV, LOS, AIS, or OOF.
Note that controlled slips do not result in ESs (as per CCITT G.821 paragraph 1.8).
Also note that when a single LOS, AIS, or OOF condition lasts for several seconds, it counts as a single EE, not as several ESs and SESs.
This field lists the number of bursty errored seconds (BESs) that have occurred during the time interval, up to a maximum of 86,400.
A BES is any second that is not a UAS that contains: no LOS, AIS, or OOF conditions, and between 2 and 319 (inclusive) EEs.
SES This field lists the number of severely errored seconds (SESs) that have occurred, up to a maximum of 86,400. An SES is any second that is not a UAS that contains: an LOS condition, or an AIS condition, or an OOF condition, or
320 or more EEs.
UAS
CSS
This field lists the number of unavailable seconds (UASs) that have occurred, up to a maximum of
86,400. A UAS state is declared when ten consecutive SESs occur. The ten SESs are subtracted from the SES count and added to the UAS count. Subsequent seconds are accrued to the UAS count until the UAS state is cleared. The UAS state is cleared when ten consecutive non-SESs occur. When that happens, the consecutive ten non-SESs are subtracted from the UAS count.
This field lists the number of controlled slip seconds (CSSs) that have occurred, up to a maximum of
86,400. A controlled slip second is any second that contains one or more controlled slips (see also the definition for ES). Note that CSSs are accumulated during unavailable seconds (UASs).
During any one-second time period, the above error events can occur in various combinations. The possible combinations are: no errors; ES; CSS; ES and CSS; ES and BES; ES and BES and CSS; ES and SES; ES and SES and CSS; UAS;
UAS and CSS.
82
Chapter 6: Performance monitoring
Field header Definition
DM
STATUS
This field lists the number of degraded minutes (DMs) that have occurred, up to a maximum of
1,440. A DM is a sixty non-UAS and non-SES second period that contains 49 or more CRC6 or BPV errors (ESF framing) or 49 or more bipolar violations (SF framing).
This field shows the type of errored conditions that occurred during the time interval. The conditions are indicated by a single character as described below.
B For both ESF and SF, a “B” is displayed if a BPV occurs.
C If ESF is enabled, a “C” is displayed if a CRC6 error occurs.
L An LOS condition has occurred, but has not necessarily integrated to an alarm state.
O An OOF condition has occurred, but has not necessarily integrated to an alarm state.
E An Excessive Error Rate (EER) condition (but not necessarily an alarm) has occurred. This condition can occur only if the EER alarm is enabled.
A An AIS condition (but not necessarily an alarm) has occurred.
Y A yellow alarm has been detected.
S A controlled slip has occurred.
@ There is an alarm state active on the M-PATH.
T There is a (loopback, code generation, or BERT) test active on the M-PATH.
1
A controlled slip is declared when the
M-PATH
detects an accrued timing difference of exactly one frame between the transmitted and received data streams, resulting in the deletion or addition of a single frame in the received data stream.
Interpreting the User NI and the User TI reports
83
Interpreting the Far-end report
The FESR and FELR commands display the recent performance history of the received signal at the far-end network interface. The reports generated by the commands are similar to the User NI report. However, the data for the Far-end report is received from the remote device through Performance Report Messages (PRMs).
Because the Far-end reports are based on PRMs, PRM generation must be enabled in the far-end device, and the framing format of the T1 line must be ESF. (Use the EPRM command to enable PRM generation in the M-PATH and use the NESF command to enable
ESF framing format.)
The figure below shows an example of a short version of the Far-end report. Notice that it is the same as a User NI report except for the status codes described in the header and listed in the status column.
KENTROX MPATH 53n - FAR END PRM SHORT PERFORMANCE REPORT
ADDRESS: 00:00:000 NAME: PORTLAND,OR
DATE: JAN 13, 1995 TIME OF DAY: 10:53
STATUS CODES: C=CRC6, V=LCV, F=FRAME BIT ERR, E=SEVERE FRAME BIT,
S=SLIP, P=PAYLOAD LOOP BACK, M=MISSED 4 PRM, N=NO POWER
SECOND OF INTERVAL: 495 OF 900 COMPLETED INTERVALS: 1 OF 96
G.821 G.821 G.821 G.821
EE ES BES SES UAS CSS DM STATUS
------ ----- ----- ----- ----- ----- ---- ----------
CUR SEC 319 1 1 0 0 0 0 C VF
PRE SEC 319 1 1 0 0 0 0 C VF
CUR 15-MIN 6776 59 59 0 0 0 1 C VFE M
PRE 15-MIN - - - - - - -
CUR 24-HR - - - - - - -
Time intervals and the Far-end report
The method of dividing up time intervals for the Far-end report is the same as for the User
NI report. See “Time intervals in the reports” on page 81
.
84
Chapter 6: Performance monitoring
The following table describes the performance data displayed in the Far-end report.
Field header Description
EE
ES
BES
This first field lists the number of error events (EEs) that have occurred, up to a maximum of 999,999.
Only CRC6 errors are used to calculate error events.
The PRM message does not provide exact counts of CRC6 error events. Instead it uses 6 bits that indicate that the error rate fell within a certain range; then the highest number in the range (except for the last range, as noted below) is used as the error count in the Far-end report as follows:
1 CRC6 error-per-second counts as one EE
2 to 5 CRC6 errors-per-second count as 5 EEs
6 to 10 CRC6 errors-per-second count as 10 EEs
11 to 100 CRC6 errors-per-second count as 100 EEs
101 to 319 CRC6 errors-per-second count as 319 EEs
320 or more CRC6 errors-per-second count as 333 EEs
This field lists the number of errored seconds (ESs) that have occurred during the time interval, up to a maximum of 86,400. An ES is any second that is not a UAS that contains one or more CRC6 errors.
This field lists the number of bursty errored seconds (BESs) that have occurred during the time interval, up to a maximum of 86,400. A BES is any second that is not a UAS that contains between 2 and 319
(inclusive) CRC6 errors.
SES
UAS
This field lists the number of severely errored seconds (SESs) that have occurred during the time interval, up to a maximum of 86,400. An SES is any second that is not a UAS that contains 320 or more
CRC6 errors.
This field lists the number of unavailable seconds (UASs) that have occurred, up to a maximum of
86,400. A UAS state is declared when ten consecutive SESs occur. The ten SESs are subtracted from the
SES count and added to the UAS count. Subsequent seconds are accrued to the UAS count until the
UAS state is cleared. The UAS state is cleared when ten consecutive non-SESs occur. When that happens, the consecutive ten non-SESs are subtracted from the UAS count.
CSS
During any one second time period, the above error events can occur in various combinations. The possible combinations are: no errors; ES; CSS; ES and CSS; ES and BES;ES and BES and CSS; ES and SES; ES and SES and CSS; UAS;
UAS and CSS.
DM
This field lists the number of controlled slip seconds (CSSs) that have occurred during the time interval, up to a maximum of 86,400. A controlled slip second is any second that contains one or more controlled slips (see also the definition for ES). Note that CSSs are accumulated during unavailable seconds (UASs).
This field lists the number of degraded minutes (DMs) that have occurred during the time interval, up to a maximum of 1,440. A degraded minute is a sixty non-UAS and non-SES second period that contains
49 or more CRC6 errors (ESF framing) or 49 or more bipolar violations (SF framing).
Interpreting the Far-end report
85
Field header
Status
Description
This field shows the type of errored conditions that occurred during the time interval. The conditions are indicated by a single character as described below:
C A CRC6 error has been detected in the received T1 signal.
V A line code violation condition has occurred in the received network signal. A line code violation occurs when a bipolar violation that is not part of a zero-substitution code is received.
F A frame synchronization bit error has occurred in the received network signal. A frame synchronization bit error occurs when an error in the framing-bit-pattern is received.
E A severely-errored framing event has occurred in the received network signal. A severely-errored framing event occurs when two or more framing-bit-pattern errors occur within a
3-millisecond period.
A controlled slip has occurred at the received network signal. A controlled slip event occurs when there is a replication or deletion of a T1 frame by the receiving network interface.
P A payload loopback is active on the network interface.
M No PRMs have been received for four or more consecutive seconds. Each PRM contains information for four consecutive seconds, and so no data is lost if up to three PRMs are missing.
86
Chapter 6: Performance monitoring
Interpreting the Statistical reports
A Statistical report has two parts. The first part is a statistical summary of the recent performance history of the received signal. The second part is an in-service performance measurement of the received signal. The following figure shows an example of a Statistical report. The NI Statistical report (NSR) and TI Statistical report (TSR) differ only in that they monitor different interfaces.
KENTROX MPATH 53n - USER NI STATISTICAL PERFORMANCE REPORT
ADDRESS: 00:00:000 NAME: PORTLAND,OR
DATE: JAN 6, 1995 TIME OF DAY: 02:52
|-------------- G.821 ---------------|
%AS %EFS %ES %SES %DM %BES %CSS
------ ------ ------ ------ ------ ------ ------
CUR 15-MIN 100.00 100.00 0.0000 0.0000 0.0000 0.0000 0.0000
PRE 15-MIN 100.00 100.00 0.0000 0.0000 0.0000 0.0000 0.0000
CUR 24-HR 97.412 92.932 7.0679 0.0000 8.8435 6.9653 0.0797
START OF TEST: DATE: JAN 6, 1995
TIME: 00:14
PERFORMANCE MEASUREMENT COUNT
----------------------------- ----------
ESF ERRORS 188016
CRC6 ERRORS 111215
OUT OF FRAME ERRORS 0
FRAME BIT ERRORS 7471
BIPOLAR VIOLATIONS 0
CONTROLLED SLIPS 7
YELLOW ALARM EVENTS 0
AIS EVENTS 1344
LOSS OF FRAME EVENTS 985
LOSS OF SIGNAL EVENTS 6
Interpreting the Statistical reports
87
The report’s statistical summary
The statistical summary shows statistical percentages for the current 15-minute interval, the previous 15-minute interval, the current 24-hour interval, and each of the last seven
.
The percentages are computed from the counts stored in the performance database for the
User NI or TI report.
The statistical percentages are computed using the concept of an “available second”. In the formulas defined below, you will see the variable “Sec_avail”. An available second is simply any second that is not an unavailable second:
Sec_avail = Sec_total - UAS
Specifically, the number of available seconds for any time period is simply the number of total seconds for the time period (900 for 15 minutes, 86400 for 24 hours) minus the num-
ber of UAS seconds. See “UAS” on page 82 for a definition of an unavailable second.
Any time “Sec_avail” is zero for a time period and the formula for computing the percentage uses “Sec_avail” in a denominator, a series of dashes is displayed as the result instead of a numerical value.
88
Chapter 6: Performance monitoring
The following is a list of the seven fields in the statistical summary and the formulas used to compute their values.
Field header
%AS
%EFS
%ES
%SES
%DM
%BES
%CSS
Description
This field lists the percentage of available seconds (%AS) for the time interval. The formula for this statistic is:
%AS = (Sec_avail / Sec_total) x 100
This field lists the percentage of error-free seconds (%EFS) for the time interval. An error-free second is any available second that was not an errored second. The formula is:
%EFS = ((Sec_avail - ES) / Sec_avail) x 100 where ES is the number of errored seconds for the time interval.
This field lists the percentage of errored seconds (%ES) for the time interval. The formula for this statistic utilizes ES, where ES is the number of errored seconds. The formula is:
%ES = (ES / Sec_avail) x 100
Note that the sum of %EFS and %ES should be 100%.
This field lists the percentage of severely errored seconds (%SES) for the time interval. The formula for this statistic utilizes SES, where SES is the number of severely errored seconds (using the same definition as for the User NI report). The formula is:
%SES = (SES / Sec_avail) x 100
This field lists the percentage of degraded minutes (%DM) for the time interval. The formula for this statistic utilizes DM, where DM is the number of degraded minutes (using the same definition as for the
User NI report). The formula is:
%DM = (DM / ((Sec_avail / 60) rounded to next higher integer)) x 100
This field lists the percentage of bursty errored seconds (%BES) for the time interval. The formula for this statistic utilizes BES, where BES is the number of bursty errored seconds for the time interval (using the same definition as for the User NI report). The formula is:
%BES = (BES / Sec_avail) x 100
This field lists the percentage of controlled slip seconds (%CSS) for the time interval. The formula for this statistic utilizes CSS, where CSS is the number of controlled slip seconds for the time interval (using the same definition as for the User NI report). The formula is:
%CSS = (CSS / Sec_avail) x 100
Interpreting the Statistical reports
89
The Statistical report’s in-service performance measurement
The second part of the report displays counts of various error conditions in the received network signal. These are just raw counts, not percentages. The data for this display is kept in registers separate from the registers used for other reports. You can reset the counts at any time. Resetting the count does not affect performance information (including the information in the first part of the Statistical report). The error counts are useful for running an in-service test on the network line.
To run an in-service test on the NI or TI interface, use these steps:
1
Issue the NSR or TSR command using the Z option to clear (zero-out) the error counts. For example,
NSR Z
This displays the Statistical report, showing the error counts at the time the command was issued, and then clears the error data.
2
Wait the desired time interval.
3
Issue the command again.
This displays the error counts accumulated since the time you cleared the error counts.
The figure below shows an example of an in-service performance measurement. The header shows the start of the test, which is the time that the error counts were last cleared. Below that are two columns, listing the type of error condition and a corresponding error count. The maximum value that may appear in any count field is
2
32
-1 (4,294,967,295). When this limit is reached, the count wraps to zero (0).
KENTROX MPATH 53n - USER NI STATISTICAL PERFORMANCE REPORT
ADDRESS: 00:00:000 NAME: PORTLAND,OR
DATE: JAN 6, 1995 TIME OF DAY: 02:52
|-------------- G.821 ---------------|
%AS %EFS %ES %SES %DM %BES %CSS
------ ------ ------ ------ ------ ------ ------
CUR 15-MIN 100.00 100.00 0.0000 0.0000 0.0000 0.0000 0.0000
PRE 15-MIN 100.00 100.00 0.0000 0.0000 0.0000 0.0000 0.0000
CUR 24-HR 97.412 92.932 7.0679 0.0000 8.8435 6.9653 0.0797
START OF TEST: DATE: JAN 6, 1995
TIME: 00:14
PERFORMANCE MEASUREMENT COUNT
----------------------------- ----------
ESF ERRORS 188016
CRC6 ERRORS 111215
OUT OF FRAME ERRORS 0
FRAME BIT ERRORS 7471
BIPOLAR VIOLATIONS 0
CONTROLLED SLIPS 7
YELLOW ALARM EVENTS 0
AIS EVENTS 1344
LOSS OF FRAME EVENTS 985
LOSS OF SIGNAL EVENTS 6
90
Chapter 6: Performance monitoring
■
■
■
■
■
Interface Statistical report
Counts of the following error conditions are maintained and displayed in response to the
NSR or TSR command:
ESF Errors (ESF only): this event is a CRC error or bipolar violation (BPV)
CRC6 Errors (ESF only)
Out of Frame Errors (ESF and SF)
Frame Bit Errors (ESF and SF)
Bipolar Violations (ESF and SF): this event is any bipolar violation generated in error (not including intentional bipolar violations generated by B8ZS coding)
■
Controlled Slips: this event is the addition or deletion of a single frame in the received data stream, due to a timing difference of exactly one frame between the transmitted and received data streams
■
Yellow Alarm events: this event is a transition from the condition of “not receiving yellow” to the yellow condition
■
AIS events: this event is a transition from the condition of “not receiving AIS” to the
AIS condition
■
Loss-of-Frame events: this event is a transition from the framed condition to the
OOF condition
■
Loss-of-Signal events: this event is a transition to the LOS condition
Interpreting the Statistical reports
91
Interpreting the Alarm History report
The Alarm History report (use the AHR command) shows the last 20 alarm messages. The alarm messages in the report are the same messages sent to the control port device when the control port alarm messages are enabled and configured for ASCII format.
A message is added to the report every time an interface changes to a different alarm state.
The “Alarm Cleared” message is not issued unless all alarms on that line are cleared. The report logs up to twenty messages, most recent first. Once the report reaches twenty messages, subsequent messages cause the oldest message to be dropped.
See “Monitoring alarm messages” on page 100
for a full list of the types of alarm messages that can appear in this report and their meanings.
The alarm messages are always displayed in user format (ASCII text).
Alarm messages will always appear in the Alarm History report, even if alarm messages were disabled with the DAM command in the Alarm Configuration Menu.
Information in the Alarm History report is not cleared when an ST, SD, or ZALL command is executed.
The following actions will clear the Alarm History report:
■
■
■
Power cycling the M-PATH
Executing the RSD command (see
“Resetting to default values” on page 36
Executing the BOOT command (see
“Obtaining new system software” on page 35
An example of the Alarm History report is shown below.
SET ALM JAN.13,1995 10:52 NI EER PORTLAND,OR addr = 00:00:000
CLR ALM JAN.13,1995 10:52 NI PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:51 NI YEL PORTLAND,OR addr = 00:00:000
CLR ALM JAN.13,1995 10:50 NI PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:47 NI YEL PORTLAND,OR addr = 00:00:000
CLR ALM JAN.13,1995 10:31 NI PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:18 NI EER PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:18 NI OOF PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:18 NI EER PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:18 NI OOF PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:18 NI LOS PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:17 NI EER PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:16 NI YEL PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:16 NI EER PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:16 NI LOS PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:16 NI EER PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:16 NI OOF PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:16 NI AIS PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:16 NI OOF PORTLAND,OR addr = 00:00:000
SET ALM JAN.13,1995 10:16 NI LOS PORTLAND,OR addr = 00:00:000
92
Chapter 6: Performance monitoring
Interpreting the Security History report
■
■
The Security History report (use the SHR command) shows the last 10 events that might indicate unauthorized attempts to access the M-PATH. The report includes three types of events:
An incorrect Telnet password has been entered (Telnet Password).
The M-PATH has read or written an incorrect SNMP community string (SNMP Rd
CommString or SNMP Wr CommString).
■
The M-PATH has received a trap or message from a device whose IP address is not on the Source Screening Address list (IP Screen).
The report logs up to 10 events, most recent first. Once the report reaches 10 events, each subsequent new event causes the oldest event to be dropped.
The IP address of the device which caused the security event is listed under “Comments.”
You can configure the SNMP agent to send an SNMP Authentication Trap whenever one
.
Information in the Security History report is not cleared when an ST, SD, or ZALL command is executed.
The following actions will clear the Security History report:
■
■
■
Power cycling the M-PATH
Executing the RSD command (see
“Resetting to default values” on page 36
Executing the BOOT command (see
“Obtaining new system software” on page 35
An example of the Security History report is shown below.
Date/Time Security Event Comments
------------------ ------------------- ----------------------------
MAR.13, 1995 11:52 Telnet Password Src IP Addr: 192.0.2.1
FEB.13, 1995 11:52 SNMP Wr CommString Src IP Addr: 192.0.2.1
JAN.13, 1995 10:51 IP Screen Src IP Addr: 255.255.255.255
Interpreting the Security History report
93
Interpreting the Carrier NI report
TIP
For the purpose of monitoring the NI performance, there is generally no reason to use the
Carrier NI report. The same information is available in more detail in the User NI report.
The Carrier NI report allows you to view the carrier’s version of the performance data of the NI signal received by the M-PATH.
At many sites, the M-PATH is at the point of demarcation on a T1 line between a carrier and a customer premise. Therefore, the M-PATH keeps two sets of registers, both of which collect performance data on the unit’s signal received at the network interface: one set of registers for the customer and one set of registers for the carrier.
The customer can view the performance data collected in the customer registers by using the User NI report. The customer can also view the performance data collected in the carrier registers by using the Carrier NI report. The carrier accesses the data in the carrier registers from a remote device using the facility data link.
The customer cannot alter the data in the contents of the carrier’s registers (clear it, for instance), nor can the carrier alter the data in the customer’s registers.
The format of the Carrier NI report is similar to that of the User NI report. The figure below shows a short version (using the CNSR command), though a long version (using the CNLR command) is available. The method of calculating the values in the report is per AT&T 54016.
KENTROX MPATH 53n - CARRIER NI SHORT PERFORMANCE REPORT
ADDRESS: 00:00:000 NAME: PORTLAND,OR
DATE: JAN 6, 1995 TIME OF DAY: 00:31
SECOND OF INTERVAL: 85 OF 900 COMPLETED INTERVALS: 2 OF 96
EE ES BES SES UAS CSS LOFC
------ ----- ----- ----- ----- ----- -----
CUR SEC 0 0 0 0 1 0 0
PRE SEC 0 0 0 0 1 0 0
CUR 15-MIN 0 0 0 0 14 0 1
PRE 15-MIN 5036 93 85 0 0 0 0
CUR 24-HR 5371 95 85 2 47 1 1
94
Chapter 6: Performance monitoring
C H A P T E R
7
Troubleshooting
TIP
Always deal with the highestpriority alarms first.
■
■
■
This chapter describes how to troubleshoot M-PATH units. It contains the following information:
How LEDs and alarm messages alert you when something is wrong
How to find out the type of alarm and the interface at which it is occurring
A list of all error conditions in the System Status report, and suggestions on how to resolve them
■
A description of how to use the M-PATH diagnostic tools, including self test, loopbacks, and BERTs
Following is a quick guide to the alarms generated by M-PATH units and to the pages in this chapter that provide appropriate troubleshooting procedures for the alarms. The alarms are listed in priority order, from highest to lowest priority. Always deal with the highest-priority alarms first.
Figure 6—Troubleshooting the M-PATH
NI LOS (page
)
ECF (page
)
NI AIS (page
High Priority
DP LOS (page
)
TI YEL (page
)
)
)
BPV (page
CRC (page
Medium Priority
Low Priority
95
Interpreting the front-panel LEDs
Figure 7—LEDs when conditions are NORMAL
Green: power-on
Blinking green: user is logged on
Flashing red-to-green: software download in progress
Green “heartbeat” blink
(537 only): unit has sent autoconfiguration request
Green: valid data at NI
Off
Off
Off
Off
Yellow or blinking yellow: tests being run
Off: no active tests
Yellow: transmit (TxD) or receive (RxD) data
Yellow CTS LED: status of
“clear to send”
Yellow RTS LED: status of
DTR and/or RTS
T
X
D
R
X
D
CTS
RTS
LINK
T
X
POWER
FAIL
AUTO
CFG
DATA
CV
RED
ALM
YEL
ALM
CV
STATUS
TEST
LLB
OFF
DPLB
NI
TI
DATA
PORT
ETHERNET
M-PATH 538
T1 CSU
Green: auto-configuration is enabled
Off: auto-configuration is not enabled
Green: valid data at TI, no alarms
Off: TI disabled
Yellow: Ethernet link can receive data
Green: Ethernet link is transmitting data
96
Chapter 7: Troubleshooting
Figure 8——LEDs when conditions are ABNORMAL
Red: equipment failure (EQF)
Off: power loss
Red: NI LOS
Fast-blinking red: NI OOF
Slow-blinking red: NI AIS
Yellow: incoming NI Yellow Alarm
Red: LOS, OOF, AIS, or Yellow
Alarm on terminal interface
Off: no data flow
Off: either an NI alarm is active or the data port was not programmed
Off: DTE not ready to send data
T
X
D
R
X
D
CTS
RTS
LINK
T
X
POWER
FAIL
AUTO
CFG
DATA
CV
RED
ALM
YEL
ALM
CV
STATUS
TEST
LLB
OFF
DPLB
NI
TI
DATA
PORT
ETHERNET
M-PATH 538
T1 CSU
Blinking yellow: BPV or CRC on network interface
Blinking yellow: BPV or CRC on terminal interface
Interpreting the front-panel LEDs
97
Table 6—LED indicators and their meanings
LED Indicator Condition
POWER/FAIL Green Power is on, self-test successful.
Green, blinking steadily A user is logged into the
M-PATH unit.
Green, “heartbeat” blink
(two blinks, then pause)
The plug-in (537) is requesting configuration.
Red-to-green, flashing Software program is being downloaded.
Red
Off
Green
Power is on, self-test failed.
No power is being received.
Auto-configuration has been enabled.
AUTO CFG
(538 only)
NI DATA
NI CV
NI RED ALM
NI YEL ALM
TI CV
TI STATUS
DATA PORT TxD
Green
Yellow, blinking
Red
Blinking fast
(5 times per second)
Valid framed signal is being received at the network interface.
Code violation (such as a CRC or
BPV) at the network interface.
LOS alarm. The T1 signal has been lost at the network interface.
OOF alarm. The T1 signal is out-offrame at the network interface. Some or all of the DS1 framing bits have been lost.
Blinking slow
(about once per second)
Incoming AIS alarm. The equipment on the other end is in test or alarm state.
Yellow
Yellow, blinking
The equipment on the other end of the circuit is in OOF or LOS alarm.
Code violation (such as a CRC or
BPV) at the terminal interface.
Red
Green
Yellow
Extended “off”
Alarm (LOS, OOF, AIS, or Yellow) at the terminal interface.
Valid framed signal is being received at the terminal interface.
Data is being transmitted (input) at the data port. Note that under normal conditions this LED may fluctuate in intensity.
Spaces are being received at the data port. The spaces are transmitted to the network if RTS and CTS are high.
98
Chapter 7: Troubleshooting
Table 6—LED indicators and their meanings (continued)
LED
DATA PORT RxD
DATA PORT CTS
DATA PORT RTS
ETHERNET LINK
(538 only)
ETHERNET Tx
(538 only)
Indicator
Yellow
Off
Yellow
Off
Yellow
Off
Yellow
Green
Condition
Data is being received (output) at the data port. Note that under normal conditions this LED may fluctuate in intensity.
Zeros are being output at the data port if RTS and CTS are on.
Channels are assigned and the NI is not in alarm. The M-PATH is ready to exchange data with the DTE.
This LED is off when it is not possible to transmit data out the data port. This may be because an NI alarm is present or the data port is not programmed or no channel is assigned.
Request to send is asserted. The DTE is ready to send data to the M-PATH, according to the conditions established by the DPLOS command.
The DTE is not ready to send data
(per the conditions configured by the
DPLOS command) or is not connected or channels are not assigned.
The unit is successfully receiving link integrity signals via Ethernet.
The unit is successfully transmitting data via Ethernet.
Interpreting the front-panel LEDs
99
Monitoring alarm messages
The M-PATH generates the alarm messages listed in
Table 7 and outputs them at the con-
trol port. If you receive an alarm message, you should use the Status (S) command to get the details of the problem.
Only one alarm can be active at a time per unit. If two alarm conditions exist on a unit, that unit issues an alarm message only for the higher priority alarm. When the higher priority alarm is cleared, the unit then issues the next lower priority alarm, if one is still present.
The table shows the alarms in decreasing order of priority.
Table 7—Alarms generated by M-PATH units
Alarm Description
ECF
NI LOS
NI AIS
NI OOF
NI YEL
NI EER
TI LOS
TI OOF
TI EER
DP LOS
External clock failure. This occurs when you specify data port timing and the M-PATH cannot detect a signal on the data port external clock pins.
Loss of T1 signal at the network interface.
Incoming AIS (alarm indicator signal) at the network interface. Some device upstream of the network interface is in an LOS or OOF alarm state on the far side or in a test mode.
Out-of-frame T1 signal at the network interface. Some or all DS1 framing bits have been lost.
Incoming yellow alarm at the network interface. A device upstream of the network interface is in an OOF or LOS alarm state on the near side.
Excessive error rate detected on the T1 signal at the network interface.
Loss of the T1 signal at the terminal interface.
Out-of-frame T1 signal at the terminal interface. Some or all DS1 framing bits have been lost.
Excessive error rate detected on the T1 signal at the terminal interface.
Loss of DTR and/or RTS at the data port.
100
Chapter 7: Troubleshooting
Examining system status
TIP
For a discussion of how the
M-PATH transitions in and out of alarm states based on errored
signal conditions, see “T1 alarms and signal processing” on page 153.
If the M-PATH is in an alarm state or if you notice an abnormal condition, use the System
Status report display to get more information. You can view the system status from the front-panel or the command line interface. Both the front-panel display and the command line report use the same status codes, which are explained in
.
The system status tells you the current condition of the M-PATH, including any alarms that may be active as well as current — and possibly intermittent— signal conditions at the network interface, the terminal interface, and the data ports. Both the LCD status display and the command line status display are dynamic and are updated as conditions change on the M-PATH.
Using the command line
To see the command line display, enter S at the prompt. A screen similar to the one shown below appears. The display is updated once per second if the status changes, with the new status line added at the bottom. You exit the display by pressing Ctrl-C.
OPERATIONAL STATUS (^C TO EXIT)
JAN 4, 1997
TIME SYSTEM NI TI Data Port Power
----- --------- ------- ------- --------- -------
ALRM LPBK IN OUT IN OUT DP1 A B
----- ---- ---- --- --- --- --- --- --- ---
07:31 NLOS - LOS YEL LOS AIS CON ON OFF
Screen column
TIME
SYSTEM ALRM
SYSTEM LPBK
NI IN, NI OUT
TI IN, TI OUT
Data Port
Power
Description
This column shows the time of day (in 24-hour format) that the status line was generated.
This column shows the highest priority state.
This column shows if a loopback is active.
These columns show the network interface RCV and
XMT signal conditions.
These columns show the terminal interface RCV and
XMT signal conditions.
These columns show the data port input signal condition.
This column shows the status of the two DC power feeds to the 12-slot shelf. It is available only for the 538 controller, and can be ignored if the unit is installed in a two-slot shelf.
Examining system status
101
Status codes
explains the status codes and refers to a page for possible solutions.
Table 8—Status codes
Code Description Solution
ALRM — Alarm Status
TOOF
TAIS
TYEL
TEER
1LOS
—
ECF
NLOS
NOOF
NAIS
NYEL
NEER
TLOS
LPBK — Loopback Status
No alarm exists.
External clock failure.
Loss of the network input signal.
The network input signal is out of frame.
Normal behavior.
Incoming AIS (alarm indication signal) at the network interface.
Incoming yellow alarm at the network interface.
Excessive error rate detected on the network input signal.
Loss of the terminal input signal.
The terminal input signal is out of frame.
Incoming AIS (alarm indication signal) at the terminal interface.
Incoming yellow alarm at the terminal interface.
Excessive error rate detected on the terminal input signal.
Loss of DTR and/or RTS at data port 1.
LLB
LOC
PLB
TLB
—
RLLB
RPLB
RDP1
DP1
DT1
No loopback is set.
Code has been sent to set a remote line loopback.
Code has been sent to set a remote payload loopback.
Code has been sent to set remote data port loopback.
A line loopback is set on the local device.
A local loopback is set on the local device.
A payload loopback is set on the local device.
A terminal loopback is set on the local device.
A data port loopback is set on the local device.
A data terminal loopback is set on the local device.
NI IN (Rx) — Network Input Status
LOS
OOF
AIS
Loss of the network input signal.
The network input signal is out of frame.
Incoming AIS (alarm indication signal) at the network interface.
Normal behavior.
Loopback test in progress.
Loopback test in progress.
Loopback test in progress.
Loopback test in progress.
Loopback test in progress.
Loopback test in progress.
Loopback test in progress.
Loopback test in progress.
Loopback test in progress.
102
Chapter 7: Troubleshooting
Table 8—Status codes (continued)
Code
YEL
BPV
QRS
324
247
511
1’S
0’S
Description Solution
Incoming yellow alarm at the network interface.
A bipolar violation has been detected on the network input signal.
This applies only if the network signal is using SF framing.
A BERT running QRS test code is active at the network interface. Normal behavior when a
BERT is active.
A BERT running 3 in 24 test code is active at the network interface.
Normal behavior when a
BERT is active.
A BERT running 2047 test code is active at the network interface.
Normal behavior when a
BERT is active.
A BERT running 511 test code is active at the network interface.
Normal behavior when a
BERT is active.
A BERT running all 1s test code is active the network interface.
Normal behavior when a
BERT is active.
A BERT running all 0s test code is active at the network interface.
Normal behavior when a
BERT is active.
Valid data is being received. No errors detected.
Normal behavior. —
NI OUT (Tx) — Network Output Status
AIS
YEL
QRS
324
247
511
1’S
0’S
COD
—
AIS (alarm indication signal) is being transmitted out the network interface.
Yellow alarm is being transmitted out the network interface. This occurs when LOS, OOF, or incoming AIS is detected at the network input signal.
QRS test code is being transmitted out the network interface.
3 in 24 test code is being transmitted out the network interface.
See the entry in this table for
Network input status codes
LOS, OOF, or AIS.
Normal behavior when a
BERT is active.
Normal behavior when a
BERT is active.
2047 test code is being transmitted out the network interface.
511 test code is being transmitted out the network interface.
All 1s test code is being transmitted out the network interface.
All 0s test code is being transmitted out the network interface.
Normal behavior when a
BERT is active.
Normal behavior when a
BERT is active.
Normal behavior when a
BERT is active.
Normal behavior when a
BERT is active.
Normal behavior.
The M-PATH is in the process of setting or resetting a remote loopback.
Valid data is being transmitted out the network interface.
Normal behavior.
Examining system status
103
Table 8—Status codes (continued)
Code Description Solution
TI IN (Rx) — Terminal Input Status
LOS
OOF
AIS
YEL
BPV
—
Loss of the terminal input signal.
The terminal input signal is out of frame.
Incoming AIS (alarm indication signal) at the terminal interface.
Incoming yellow alarm at the terminal interface.
A bipolar violation has been detected on the terminal input signal.
Valid data is being received. No errors detected.
Normal behavior.
TI OUT (Tx) — Terminal Output Status
YEL
AIS
—
Yellow alarm is being transmitted out the terminal interface. This occurs when incoming yellow alarm is detected at the network input signal.
Troubleshoot the alarm causing the output.
AIS (alarm indication signal) is being transmitted out the terminal interface. This occurs when LOS, OOF or incoming AIS is detected on the network input signal.
Troubleshoot the alarm causing the output.
Valid data is being transmitted out the terminal interface.
Normal behavior.
Data Port (DP)
—
CON
LOS
No bandwidth (channels) have been assigned to the data port.
Bandwidth is assigned to the port, and the port is not in a
LOS condition.
Bandwidth is assigned to the port, but a loss of DTR or RTS has been detected.
Normal behavior.
Normal behavior.
104
Chapter 7: Troubleshooting
Troubleshooting tree
Troubleshooting alarms
The best troubleshooting method is to start with the highest priority alarm, find its cause and fix it, and then turn to the next highest priority. The following alarm list is arranged from high to low priority. You may also want to use some of the diagnostic tools described later in this chapter.
NOTE
High-priority alarms tend to arise from more basic problems than low-priority alarms.
Often, fixing a high-priority alarm will also automatically correct alarms of lower priority. Network management systems use the words “critical”, “major”, and “minor” to rank alarms in terms of seriousness. These two rankings are similar, but not always identical.
NI LOS—high priority
If you receive a loss-of-signal condition at the network interface...
An NI LOS condition occurs when the M-PATH cannot detect a signal at its network interface. To troubleshoot for this condition:
■
Make sure that you have correctly connected the cable between the M-PATH network interface and your T1 service provider’s equipment.
■
If you built the cable on-site, check the cable connectors. A reversal of the transmit and receive pairs, or an open receive pair, can cause this condition.
■
If the above appear to be okay, ask your T1 service provider to test your T1 line and correct any problems found.
TI LOS—high priority
If you receive a loss-of-signal condition at the terminal interface...
A TI LOS condition occurs when the M-PATH cannot detect a signal at its terminal interface. To troubleshoot for this condition:
■
Make sure that you have correctly connected the cable between the M-PATH terminal interface/data port and your CPE equipment.
■
If you built the cable on-site, recheck the cable connectors. A reversal of the transmit and receive pairs, or an open transmit pair (CPE-to-M-PATH), can cause this condition.
NOTE
If you assign channels to the terminal interface but do not connect equipment to it, the unit will generate the TI LOS alarm.
Troubleshooting tree
105
ECF—high priority
NI OOF—high priority
If the incoming signal at the network interface is out-of-frame...
An out-of-frame condition occurs when the framing type you have configured for the network interface does not match the framing type of the incoming T1 signal. Allowed framing types are ESF, SF, or Ericsson. To troubleshoot this condition:
■
■
Ask your T1 service provider to change the framing type of your T1 line.
A highly errored incoming signal can also cause an OOF condition.
NI AIS—high priority
■
■
■
If you receive an external clock failure (ECF) alarm...
An ECF alarm occurs when the M-PATH is configured for data port timing, but it cannot detect a clock signal at the data port, either because the signal is not present or because the signal is significantly out of timing. To troubleshoot this condition:
■
Verify whether or not the M-PATH should really be set to data port timing. You should only use this timing option if a timing source is not provided by the T1 service. Controlled slips may occur if you set the M-PATH to data port timing when a network clock is present.
Check the cable connection between the data port and your external clock source.
Verify that your external clock source is powered up and configured correctly.
Verify that your external clock source provides the correct type of clock signal, as shown in the M-PATH specifications (see
).
TI OOF—medium priority
If an alarm indication signal (AIS) is detected at the network interface...
An incoming AIS at the network interface indicates a problem with remote equipment on the T1 circuit. For example, the far-end equipment may not be connected or configured properly or is in a test mode, or the network interface unit (i.e., NIU or smart jack) may be in loopback, or your service provider may not have enabled your circuit yet. To troubleshoot this condition:
■
Ask your T1 service provider to trace the source of the AIS signal.
If the incoming signal at the terminal interface is out-of-frame...
An out-of-frame condition occurs when the framing type you have configured for the terminal interface does not match the framing type of the signal being received at the terminal interface. Allowed framing types are ESF, SF, or Ericsson. To troubleshoot this condition:
■
Change the framing type of the terminal interface (see mat” on page 54 ) or
■
Change the framing type of the attached CPE equipment.
Note that a highly errored incoming signal can also cause an OOF condition. Check the description of TI EER.
106
Chapter 7: Troubleshooting
DP LOS—medium priority
NI EER—medium priority
TI YEL— medium priority
If you receive a loss-of-signal indication at the data port...
A DP LOS condition occurs when the M-PATH is not able to handshake as expected with an attached DTE device.
The M-PATH can monitor two handshake lines on the data port: DTR and RTS. You can configure your M-PATH to use DTR, RTS, both lines, or neither line as the DP LOS crite-
ria (see “Setting up DPLOS (data port loss of signal) processing” on page 62
). When the specified line goes low, the M-PATH assumes that the DTE equipment has been disconnected or has failed. To troubleshoot this condition:
■
■
■
■
Check the cable connection between the M-PATH data port and the DTE.
Verify that the cable is connected to the correct port on the DTE.
Verify that you are using the correct cable for your application.
Make sure that the DTE is powered up and that its serial port is activated.
Refer to Chapter 2 or Chapter 3 of the M-PATH Installation Guide for instructions on how to properly connect cables.
■
■
If an excessive error rate is detected at the network interface...
The errors may be BPVs, CRC6 errors, or framing errors. There are several potential causes of an excessive error rate at the network interface. To troubleshoot this condition:
■
Make sure you haven’t set too low a threshold for detecting errored seconds or unavailable seconds. A low setting increases error sensitivity. You might want to use
the factory default threshold setting (see page 42
).
■
Make sure that you have correctly connected the cable between the M-PATH network interface and your T1 service provider’s equipment. (Refer to Chapter 2 or
Chapter 3 of the M-PATH Installation Guide for instructions on how to properly connect the cable.)
■
If you built the cable on-site, recheck the cable connectors. Loose or intermittent connections can cause an excessive error condition.
■
Make sure that you have configured the line coding of the network interface to match
the line coding of your T1 line: either AMI or B8ZS. (See “Specifying NI line coding” on page 48
.)
Make sure the system clock is configured correctly.
If all the above appear to be okay, ask your T1 service provider to test your T1 line and correct any problems found.
If incoming yellow alarm is detected at the terminal interface...
An incoming yellow alarm at the terminal interface indicates that the CPE equipment attached to the interface is having a problem with the signal it is receiving from the
M-PATH. Most often, it is getting no signal at all. To troubleshoot this condition:
■
Check for an open, short, or wiring error in the cable between the M-PATH terminal interface port and the CPE equipment. An open receive pair (M-PATH TI port output to CPE input) can cause this condition.
Troubleshooting tree
107
NI YEL—medium priority
TI EER—low priority
TI AIS—low priority
If incoming yellow is detected at the network interface...
An incoming yellow condition at the network interface indicates that the far end equipment has a problem with the signal it is receiving from the M-PATH. To troubleshoot this condition:
■
Check for an open, short, or wiring error in the cable between the M-PATH network interface port and your T1 service provider’s network interface unit (i.e., NIU or smart jack). An open transmit pair can cause this condition.
■
If your application uses SF framing, and all 24 channels are used for data transmission, the actual data content can sometimes cause a “false yellow” condition. ESF framing is recommended for such applications. Other work-arounds may also be possible, depending upon your application.
If an excessive error rate is detected at the terminal interface...
The errors may be BPVs, CRC6 errors, or framing errors. There are several potential causes of an excessive error rate at the terminal interface. To troubleshoot this condition:
■
Make sure you haven’t set too low a threshold for detecting errored seconds or unavailable seconds. A low setting increases error sensitivity. You might want to use
the factory default threshold setting (see page 42
).
■
Make sure that you have correctly connected the cable between the M-PATH terminal interface/data port and your CPE equipment. (Refer to chapter 2 or chapter 3 of the M-PATH Installation Guide for instructions on how to properly connect the cable.)
■
If you built the cable on-site, recheck the cable connectors. Loose or intermittent connections can cause an excessive error condition.
■
Make sure that you have configured the line coding of the terminal interface to
■
Make sure the system clock is configured correctly.
■
■
■
If an alarm indication signal (AIS) is detected at the terminal interface...
An incoming AIS at the terminal interface may indicate that the CPE equipment attached to the terminal interface is not operational. To troubleshoot this condition:
Check the programming of the CPE and make sure that its TI port is enabled.
Check the wiring between the M-PATH TI port and the CPE.
Make sure that the framing type of the CPE matches the framing type configured for
108
Chapter 7: Troubleshooting
BPV—low priority
CRC—low priority
If bipolar violations (BPVs) are detected at the network interface or the terminal interface...
A bipolar violation is an error in the normal polarity of received pulses. A bipolar violation occurs when two or more pulses of the same polarity appear in a row.
■
■
Bipolar violations are often caused by local problems with your T1 line. To troubleshoot this condition:
Make sure that your T1 wiring consists of only individually-shielded twisted pairs.
Check that all cable connections are secure and connected to the correct terminals.
Refer to Chapter 2 or Chapter 3 for instructions on how to properly connect cables.
■
Make sure that you’ve set the line coding of the NI or TI interface to match the line coding of the T1 circuit: either AMI or B8ZS. A mismatch in line coding can often result in BPV errors.
■
Make sure the system clock is configured correctly.
If CRC6 (6-bit cyclic redundancy check) errors are detected at the network interface or the terminal interface...
CRC6 errors relate to ESF framing only. A CRC6 error indicates that bits were received in error in the previous extended superframe.
■
■
CRC6 errors are often caused by remote problems with your T1 line. To troubleshoot these types of errors:
■
Make sure that you’ve set the line coding of the NI or TI interface to match the line coding of the T1 circuit: either AMI or B8ZS. This line code should be maintained throughout the connected circuit. A mismatch in line coding can often result in
CRC6 errors.
■
If the errors show up on the NI port, ask your T1 service provider to monitor the receive side of your line for CRC6 errors.
If the errors show up on the TI port, check the configuration of the CPE.
Make sure the system clock is configured correctly.
Troubleshooting tree
109
Running the self-test diagnostics
At any time, you can initiate the M-PATH self-test. The self-test verifies the functions of
M-PATH hardware circuitry. There will be a brief service interruption during the self-test.
When you execute the self-test, the M-PATH automatically resets any loopbacks and deactivates any test code generation and bit error rate tests (BERTs). It does not clear the performance database, nor does it log you out of the system.
You cannot activate the self-test if you have logged into the M-PATH remotely, either through the ARC command or via Telnet or SNMP. The self-test would break your remote login connection.
To initiate self-test from the command line, enter the DST command. You must have superuser, configuration, or maintenance privileges.
Self-test error messages
The following messages announce pass or fail conditions discovered by the self-test.
Contact our Technical Support organization if the self-test returns a “fail” condition.
Command line display
SELF TEST PASSED
RTC TEST FAILED
FLASH ID FAIL
FLASH SUM FAIL
PROGRAM WORD FAIL
PROGRAM CHECK SUM FAIL
RAM TEST FAILED AT ADDR:<hex address>
RAM CHECKSUM FAILED
RAM PATTERN TEST FAILED
NI READ/WRITE TEST FAILED
CGD DETECTION TEST FAILED
CGD BIT ERROR RATE TEST FAILED
NI DATA TEST FAILED
TI READ/WRITE TEST FAILED
DATA PORT1 TEST FAILED
110
Chapter 7: Troubleshooting
Using loopbacks
The M-PATH provides loopbacks to support line segment testing. Line segment testing allows you to probe the T1 circuit to isolate where data flow is being corrupted or disrupted.
You can set all loopbacks locally, in your near-end device. You can also set the line, payload, and data port loopbacks remotely, in a far-end device. If you set a loopback in a far-end device, you can use the M-PATH to run bit error rate tests (BERTs) to test the
T1 signal.
Line loopback
NI
NI framer
Blocked
DP
DP Idle
Blocked
TI
AIS
The line loopback allows the carrier (or a far-end device) to test the T1 signal at the
M-PATH network interface. When set to line loopback, the M-PATH loops the incoming
T1 signal back to the network. The T1 signal does not penetrate the M-PATH (it is a minimum-penetration loopback), and does not pass through the M-PATH framer. The signal, including framing and line coding errors, is returned to the network unaltered and the carrier can test the looped signal for errors.
Once the line loopback is set, the incoming network signal is interrupted, so the M-PATH outputs AIS at the terminal interface and idle characters at the data port.
You can set the line loopback using the front-panel switch (see page 117
); locally using
the command line (see page 117
); or remotely in a far-end device (see page 118
).
Using loopbacks
111
Payload loopback
TIP
You can also use a bi-directional BERT to isolate T1 line problems. See
.
NI
NI framer
Blocked
DP DP Idle
TI
Blocked
AIS
By testing the T1 signal through a line loopback as described earlier, the carrier (or the farend device) can determine if there are problems in the network line. What they cannot determine, however, is whether the problems are occurring on the input or output side of the looped line. To further isolate the source of the problems to one side of the line or the other, you can change from a line loopback to a payload loopback.
Payload loopback is the same as line loopback, except that the signal passes through the
M-PATH framer before being looped back. The framer strips out BPV errors and recalculates CRC (for ESF framing format) but does not alter the payload data.
The condition of the returned signal indicates the cause of the problem:
■
The line is okay if the returned signal contains no bit pattern errors, no BPVs, and no
CRC6 errors.
■
The problem is outbound if the returned signal contains pattern bit errors, but no
BPVs or CRC6 errors.
■
The problem is inbound and at the remote end if the returned signal contains pattern bit errors and CRC6 errors, but no BPVs.
■
The problem is inbound and at the local end if the returned signal contains pattern bit errors, CRC6 errors, and BPVs.
■
The problem is probably a remote clock slip if the returned signal contains pattern bit errors and is bursty, but contains no BPVs and no CRC6 errors.
Once the payload loopback is set, the incoming network signal is interrupted, and so the
M-PATH outputs idle characters at the data ports and AIS at the terminal interface.
You can set the payload loopback locally at the request of the carrier or a far-end site (see
), or you can set it remotely in a far-end device (see page 118 ).
112
Chapter 7: Troubleshooting
Local loopback
TIP
The local loopback is similar to a “hard” loopback set at the network interface.
NI
Blocked
NI framer
AIS
DP
TI framer
TI
The local loopback allows you to verify if the M-PATH is assigning channels correctly to the terminal interface and data port. When set in this loopback, the M-PATH combines all the incoming channels from the terminal interface and data port into the T1 bit stream, runs the bit stream through the NI framer, loops the bit stream back, and drops out the channels to the data port and/or terminal interface. By attaching terminal devices capable of monitoring the looped signals, you can verify that the correct channels are being returned to the correct ports.
When the M-PATH is set in a local loopback, the outgoing T1 signal at the network interface is interrupted. The M-PATH outputs AIS at the network interface.
The framer strips out BPV errors and recalculates CRC (for ESF framing format) but does not alter the payload data.
You can only set a local loopback in your local M-PATH (see page 117 ); you cannot set
it remotely.
Using loopbacks
113
Data port loopback
NI
NI framer
TI DS0s
DP DS0s
Blocked
DP
DP Idle
TI framer
TI
Normal traffic
The data port loopback allows the carrier (or a far-end device) to examine the fractional
DS0 channels assigned to the data port. When set to data port loopback, the M-PATH receives the T1 signal at the network interface, distributes the fractional DS0 channels as assigned to the data port, then loops the channels back to the network. It does this without affecting the rest of the received payload. Normal transmission occurs at the terminal interface.
Full-bandwidth test codes (QRSS, 3 in 24, all-1s, all-0s) will fail if the unit has some network interface channels set to the terminal interface and others set to the data port because of differences in timing delays between the terminal interface and data port circuits. You can remedy this problem by doing one of the following during the test:
■
■
■
Assign all channels to the terminal interface.
Assign all channels to the data port (rate=64 Kbps per channel).
Use a different test pattern.
Once the data port loopback is set, transmission at the data port is interrupted. The
M-PATH sends idle characters out the port to notify the connected DTE device.
You can set the data port loopback locally to facilitate testing with the carrier or a far-end
), or you can set it remotely in a far-end device (see
).
114
Chapter 7: Troubleshooting
Data terminal loopback
Terminal interface loopback
NI
Blocked
TI framer
TI
Normal traffic
DP Idle
DP
Typically, you use the data terminal loopback to verify the cabling between the data port and the attached DTE device. You can also monitor the looped signal for errors at the DTE.
The data terminal loopback allows you to loop the incoming signal at the data port. When set in this loopback, the M-PATH loops the incoming signal back to the DTE device sending the signal. The signal does not penetrate the M-PATH. The signal, including all line coding errors, is returned to the DTE device unaltered.
You can only set a data terminal loopback in your local M-PATH (see
); you cannot set it remotely.
When set in a data terminal loopback, the M-PATH inserts the data port idle character into the channels assigned to the data port. Normal activity continues at the network interface and the terminal interface.
NI
Blocked
TI framer
TI
Idle
DP
Typically, you use the terminal interface loopback to verify the cabling between the terminal interface and the CPE. You can also attach a test set to the terminal interface, send test codes, then run bit error rate tests on the looped signal.
The terminal interface loopback allows you to loop the incoming T1 signal at the terminal interface in add/drop devices. When set in this loopback, the M-PATH loops the incoming
T1 signal back to the CPE attached to the terminal interface. The signal does not penetrate the M-PATH. The signal, including all line coding errors, is returned to the CPE unaltered.
When set in a terminal interface loopback, the M-PATH inserts an idle character into channels assigned to the terminal interface. Normal activity continues at the network interface and data port.
You can only set a terminal interface loopback in your local M-PATH (see page 117 ); you
cannot set it in a remote device.
Using loopbacks
115
Data port/data terminal loopback
(via front-panel switch)
NI
NI framer time slot assignment
TI
Normal traffic
DP
The test switch on the front-panel of the M-PATH allows you to set a local line loopback
(LLB) or a combined data port and data terminal loopback (DPLB). This combined loopback is illustrated above. You can only set this loopback via the front-panel switch; it is not available through the command line interface.
116
Chapter 7: Troubleshooting
Setting and resetting loopbacks in your local device
You can set and reset loopbacks in your local device from the command line. Only one loopback, either local or remote, may be set at one time. You cannot set a loopback if another loopback is already active, if test codes are being transmitted, or if a BERT is active.
If you have logged into the M-PATH via the ARC command, the M-PATH does not allow you to set any loopback because loopbacks can potentially break the data link. The
M-PATH does allow you to set the line, payload, and data port loopbacks via Telnet or
SNMP. However, if you are managing the M-PATH via the T1 payload (using the FDL or a DS0 channel as a data link), be aware that these loopbacks could potentially break the connection by breaking the T1 payload.
NOTE
A far-end device can set your local device in line, payload, or data port loopback by sending the remote loopback commands described in the next section. A far-end device can also set your device in line loopback by sending standard line loopback set and reset code, or in data port loopback by sending 127 set code and 127 reset code (V.54 loop code).
local loopback commands
Using the command line
The figure below illustrates the Local Maintenance menu. You use the commands in this menu to set or reset loopbacks in your local device. You must have superuser, configuration, or maintenance privileges.
LOCAL MAINTENANCE MENU
SLL - Set Line Loop Back
SPL - Set Payload Loop Back
SLO - Set Local Loop Back
STI - Set TI Loop Back
SDP<n> - Set Data Port Loop Back at Data Port, n=1
SDT<n> - Set Data Terminal Loop Back at Data Port, n=1
RLB - Reset Loop Backs
DST - Do Self Test
SLL
SPL
SLO
STI
SDP1
SDT1
Set a line loopback.
Set a payload loopback.
Set a local loopback.
Set a terminal interface loopback.
Set a data port loopback on data port 1.
Set a data terminal loopback on data port 1.
To reset a loopback in your local M-PATH, enter RLB.
Using the front-panel switch
The three-position rocker switch on the M-PATH CSU’s front panel lets you select a line
loopback (LLB; see page 111 ) or a combined data port and terminal loopback (DPLB; see
page 116 ). Selecting either LLB or DPLB on this switch will run the test on the local unit
until you set the switch OFF.
Setting and resetting loopbacks in your local device
117
Setting and resetting loopbacks remotely
You can set a line, payload, or data port loopback remotely, in a far-end device. If you set one of these loopbacks, you can then send test code through the loop and run BERTs on the code to troubleshoot for errors. This section describes how to set and reset remote loopbacks. For a description of how to set and run test codes and BERTs, see
Only one loopback, either local or remote, may be set at one time. You cannot set a loopback if another loopback is already active, if test code is being transmitted, or if a BERT is active. You cannot use the SRL, SRP, or SRDP commands over the data link or via Telnet.
The figure below illustrates the Remote Maintenance menu. You use the commands listed in this menu to set and reset remote loopbacks. You must have superuser, configuration, or maintenance privileges.
remote loopback commands
REMOTE MAINTENANCE MENU
SRL - Set Remote Line Loop Back
SRP - Set Remote Payload Loop Back
SRDP<n> - Set Remote Data Port Loop Back, n = 1
RST1 - Reset Remote Loop Back
SQC/S3C/S1C/S0C - Send Test Codes at NI: QRS, 3/24, 1, 0
S5C<n> - Send 511 Test Code in Data Port <n> Bit Stream
S2C<n> - Send 2047 Test Code in Data Port <n> Bit Stream
RTC - Reset Test Codes
BTQ/BT3/BT1/BT0 - Activate BERT using Test Codes: QRS, 3/24, 1, 0
BT5<n> - Activate BERT using 511 at Data Port n = 1
BT2<n> - Activate BERT using 2047 at Data Port n = 1
SRL
SRP
Set a remote line loopback.
Set a remote payload loopback.
SRDP1
Set a remote data port loopback on data port 1.
To reset a remote loopback, enter RST1.
You may receive one or more of the following messages when setting or resetting remote loopbacks.
SENDING LOOP BACK SET CODE — The M-PATH is requesting a loopback.
REMOTE LOOP BACK IS SET— The remote loopback is set.
UNABLE TO CONFIRM REMOTE LOOP BACK IS SET — The M-PATH tried to set the remote loopback but was unable to confirm that the loopback was set.
UNABLE TO SET REMOTE LOOP BACK — The M-PATH cannot set a loopback because a loopback is already set, a test code is being generated, or a BERT is active.
LLB
OFF
DPLB
M-PATH 538
118
Chapter 7: Troubleshooting
Using test codes and BERTs
When you set a remote loopback in a far-end device, you’ll usually want to run a bit error rate test (BERT) on the looped signal. A BERT allows you to send a test code through a looped back line, then counts the errors returned in the signal. For example, the figure below illustrates how you might use a BERT in conjunction with a line loopback.
Local M-PATH output test code
BERT counter
NI transmission facility
NI
Remote M-PATH line loopback
To use a BERT in conjunction with a remote loopback, do the following:
1
Set the remote loopback. You can set a remote line or payload loopback to test the full T1 signal, or you can set a data port loopback to test the channels assigned to a specific data port.
2
Send test codes through the loop.
To test the full T1 signal, assign all of the network interface channels to the terminal interface or assign them all to the data port. Then send one of the following test codes: QRS, 3 in 24, all 1s, or all 0s.
To test the channels assigned to the data port, send a 511 or 2047 code on the data port channels.
3
Activate the BERT and monitor the BERT error report.
4
Exit BERT.
5
Reset the test codes.
6
Reset the loopback.
You can also use BERT in a bidirectional, point-to-point test. In this application, you set each M-PATH in the point-to-point connection to output specific test code. Then you activate BERT on that test code in each device. This allows you to test the T1 signal between the network interfaces of the two devices.
Local M-PATH output test code
BERT counter
NI transmission facility
NI
Remote M-PATH
BERT counter output test code
Using test codes and BERTs
119
How BERTs work
When a BERT is first activated, the M-PATH initializes all counters to zero. It starts monitoring the incoming network signal for the specified test pattern. (In the case of a data port loopback, the M-PATH looks for the specified test pattern only on the channels mapped to the specified data port.)
When the M-PATH recognizes the test pattern, it begins tracking time and errors. The time counter continues to count even during time of sync loss. The time and error counters continue to count until they reach their maximum limit as specified below; they do not roll over.
You can exit BERT by typing Ctrl-C.
RM> btq
^C to TERMINATE
SEARCHING FOR PATTERN
Pattern Detected
TEST BIT ERRORED BURSTY SEV ERR UNAVAIL TOTAL BIT
SECONDS ERRORS SECONDS SECONDS SECONDS SECONDS ERRORS
------- ------ ------- ------- ------- ------- ---------
1 0 0 0 0 0 0
2 0 0 0 0 0 0
3 0 0 0 0 0 0
4 0 0 0 0 0 0
5 0 0 0 0 0 0
6 0 0 0 0 0 0
7 0 0 0 0 0 0
8 1 1 0 0 0 1
9 3 2 1 0 0 4
10 5 3 2 0 0 9
11 6 4 3 0 0 15
12 5 5 4 0 0 20
13 5 6 5 0 0 25
14 5 7 6 0 0 30
15 4 8 7 0 0 34
16 0 8 7 0 0 34
17 0 8 7 0 0 34
18 0 8 7 0 0 34
19 0 8 7 0 0 34
20 0 8 7 0 0 34
120
Chapter 7: Troubleshooting
Field
TEST SECONDS
BIT ERRORS
ERRORED SECONDS
BURSTY SECONDS
SEV ERR SECONDS
UNAVAIL SECONDS
TOTAL BIT ERRORS
Description
The number of seconds, up to 2
32
maximum, that the
M-PATH has been running the test after first detecting the test pattern.
The number of bit errors, up to 65,535 maximum, that have occurred in the current second.
The number of errored seconds, up to 65,535 maximum, that have occurred since the M-PATH first detected the test pattern.
The number of bursty errored seconds, up to 65,535 maximum, that have occurred since the M-PATH first detected the test pattern.
The number of severely errored seconds, up to 65,535 maximum, that have occurred since the M-PATH first detected the test pattern.
The number of unavailable seconds, up to 65,535 maximum, that have occurred since the M-PATH first detected the test pattern.
The running total of bit errors, up to 2
32
maximum, that have occurred since the M-PATH first detected the test pattern.
Using test codes and BERTs
121
Command line access
test code commands
BERT commands
You set and reset test codes and activate a BERT by using the commands listed in the
Remote Maintenance menu. You must have superuser, configuration, or maintenance privileges to use these commands.
REMOTE MAINTENANCE MENU
SRL - Set Remote Line Loop Back
SRP - Set Remote Payload Loop Back
SRDP<n> - Set Remote Data Port Loop Back, n = 1 .. 4
RST1 - Reset Remote Loop Back
SQC/S3C/S1C/S0C - Send Test Codes at NI: QRS, 3/24, 1 ,0
S5C<n> - Send 511 Test Code in Data Port <n> Bit Stream
S2C<n> - Send 2047 Test Code in Data Port <n> Bit Stream
RTC - Reset Test Codes
BTQ/BT3/BT1/BT0 - Activate BERT using Test Codes: QRS, 3/24, 1 ,0
BT5<n> - Activate BERT using 511 at Data Port n = 1 .. 4
BT2<n> - Activate BERT using 2047 at Data Port n = 1 .. 4
Each test code is sent out framed. To set and reset test codes:
SQC
S3C
S1C
S0C
S2C1
S5C1
RTC
Send framed QRS code out the network interface.
Send framed 3-in-24 code out the network interface.
Send all 1s out the network interface. This may be required by the carrier.
Send all 0s out the network interface.
Send a 2047 code in the channels assigned to data port 1.
Send a 511 code in the channels assigned to data port 1.
Reset the test code generation.
To activate a BERT on the test codes:
BTQ
BT3
BT1
BT0
BT5n
BT2n
Activate a BERT on QRS test code.
Activate a BERT on 3-in-24 test code.
Activate a BERT on all 1s test code.
Activate a BERT on all 0s test code.
Activate a BERT on 511 test code in channels assigned to data port n.
Activate a BERT on 2047 test code in channels assigned to data port n.
To de-activate or exit a BERT, enter Ctrl-C.
When you first activate a BERT, you will receive the message SEARCHING FOR
PATTERN. When the M-PATH recognizes the test pattern, the BERT report will appear on the display.
122
Chapter 7: Troubleshooting
C H A P T E R
8
Using network management
M-PATH supports network management via Telnet and the Simple Network Management
Protocol (SNMP).
This chapter tells you:
■
■
How to configure for Telnet
How to configure for SNMP
About obtaining IP addresses
Many of the procedures in this chapter require a valid IP address. If there is a network administrator or system administrator at your company, he or she is responsible for obtaining valid IP addresses and issuing them to you. Almost all IP-based networks (except the very smallest local networks) require IP addresses to be unique. Because of this requirement, you must obtain a valid IP address for your unit to function; your unit’s
default IP addresses will not work.
If there is no one at your company who is responsible for obtaining valid IP addresses, contact your Internet service provider. Kentrox cannot issue IP addresses for you.
123
Basic network management (Telnet)
To manage M-PATH with SNMP or Telnet, you must configure the unit to operate with TCP/IP networks. Configuring the unit for management via Telnet is the first step in configuring for SNMP.
The M-PATH must be configured to operate in a TCP/IP network to use the base level of network management.
■
■
■
To manage an M-PATH with SNMP or Telnet, it must be configured to operate with TCP/
IP networks. The minimal IP network configuration for each unit consists of:
Setting the IP interface protocol
Setting the Telnet password
Setting the IP address, netmask, and default router address for each IP interface the unit will use
■
Configuring the IP network interface used for managing the unit
■
■
■
If you want to communicate with M-PATH CSUs using SNMP, these steps are also required:
Enabling the SNMP agent
Setting the SNMP read, write, and trap community strings
Setting up IP address screening, if extra IP network security is desired
124
Chapter 8: Using network management
Command line access
The M-PATH has two management configuration menus:
The Management Configuration menu contains the commands needed to set up a basic IP network interface and communicate with the unit via Telnet.
The Advanced Management Configuration menu contains the commands needed to set up
SNMP communications with an M-PATH unit.
Superuser or configuration access is required to use either menu.
Enter MC to display the Management Configuration menu.
MANAGEMENT CONFIGURATION MENU
TPW:<str> - Set Telnet Password, str=0 to 15 characters
0 characters disables Telnet
NETIF:<p>[,<dl>[,<spd>]]
- Set IP Network Interface Paths
<p> = N, E, PS, S, D, ES, ED, ESD, PSD, or SD
N = None, E = Ethernet, P = PPP, S = SLIP,
D = Datalink - if Datalink, use dl and spd
<dl> = F (FDL), 1-24 (DS0 Tslot) - if DS0, use spd
<spd> = 56 (56k of DS0 Tslot), 64 (All of Tslot)
IPR:<ipa> - Set Default Route IP Address
IPA:<p>,<ipa> - Set IP Addresses
IPM:<p>,<mask> - Set IP Masks
p = E (Ether), C (PPP/SLIP), D (Datalink)
<ipa> and <mask> = n.n.n.n, n = 0 .. 255 (dec)
<ipa> for Datalink is IP Address of remote unit
<mask> is the same for Ctl Port and Datalink
AMC - Advanced Management Configuration Menu
MCV - View Management Configuration
Enter AMC to display the Advanced Management Configuration menu.
ADVANCED MANAGEMENT CONFIGURATION MENU
ESNMP/DSNMP - Enable/Disable SNMP Agent
TCS:<str> - Set SNMP Trap Comm String, str=1 to 15 characters
RCS:<str> - Set SNMP Read Comm String, str=1 to 15 characters
WCS:<str> - Set SNMP Write Comm String, str=1 to 15 characters
SSA:<p> - Set Packet Screening via Source Address
p = I (IP Addr), N (None)
TRAP:<c>,<t> - SNMP Trap Generation c = E (Enable), D (Disable)
t = S (Start), L (Link), A (Auth), E (Enterprise)
ADD:T,<ip>[,dlci] - Add IP Address to Trap Dest List
<dlci> = optional identifier for Data Link Traps
ADD:I,<ip>[,mask] - Add IP Address to Screening List
DEL:<l>,<ip> - Delete Address from Screening or Trap Dest Lists
<l> = I (IP Screen List), T (Trap Dest List)
<ip> and [mask] = n.n.n.n, n = 0 .. 255 (dec)
[mask] used only for IP Screen List and is optional
AMCV - View Advanced Management Configuration
Basic network management (Telnet)
125
View the current settings
Before changing any management parameters, you may want to look at the current settings. You do this by executing the MCV command. This command displays the View
Management Configuration screen. To see the Telnet password, you must have superuser privileges. To see advanced management parameters, enter the AMCV command.
VIEW MANAGEMENT CONFIGURATION
Telnet Password IP Interface Paths DL Path
--------------- ----------------------- ------------
NONE NONE
CP IP Addr DL IP Addr CP & DL IP Mask IP Default Router
---------------- ---------------- ---------------- --------------
192.0.2.1 192.0.2.1 255.255.255.0 192.0.2.2
Ethernet IP Addr Ethernet IP Mask
---------------- ----------------
192.0.2.1 255.255.255.0
VIEW ADVANCED MANAGEMENT CONFIGURATION
SNMP Agent Trap Comm String Read Comm String Write Comm String
---------- ----------------- ----------------- -----------------
DISABLED snmptrap public private
Addr Screening Traps Enabled
-------------- ------------------------------------
NONE Start Link Authentication Enterprise
IP Source Address Screening Trap Destination
--------------------------------- ------------------------
IP Addr IP Mask IP Addr VC
--------------- --------------- ---------------- ------
192.0.2.2 0
126
Chapter 8: Using network management
Field Description
Telnet Password This field tells you the current Telnet password. If there is no
Telnet password, the Telnet Server will not be active and you will not be able to Telnet to the unit.
IP Interface Paths This field tells you the currently selected IP interfaces. Possible values you may see in this field are ETHER, PPP, SLIP,
DATALINK, or NONE.
DL Path
CP IP Addr
This field tells you which in-band IP data link is selected. Possible values are DS0 MODE, FDL MODE, or NONE.
This field tells you the control port IP address the unit is currently using for SLIP and PPP.
DL IP Addr This field tells you the data link IP address the unit is currently using.
CP & DL IP Mask This field tells you the control port and data link IP netmask the unit is currently using for SLIP, PPP, and the data link.
IP Default Router This field tells you the address of the IP Router the unit must send packets to in order to get them into the IP network.
Ethernet IP Address This field shows the Ethernet IP address the unit is currently using.
Ethernet IP Mask This field shows the Ethernet IP netmask the unit is currently using.
SNMP Agent This field tells you if the SNMP Agent is enabled or disabled.
Trap Comm String This field tells you the current value of the SNMP Trap
Community String. The default value is “snmptrap”.
Read Comm String This field tells you the current value of the SNMP Read
Community String. The default value is “public”.
Write Comm String This field tells you the current value of the SNMP Write
Community String. The default value is “private”.
Addr Screening This field tells you if IP addresses are currently being screened by the unit.
Traps Enabled This field tells you which SNMP trap types will be sent if the
SNMP Agent is enabled. The trap types are Start, Link,
Authentication, Enterprise, or any combination of the above.
IP Source Addr
Screening: IP Addr
This field shows which IP addresses are allowed to communicate with the M-PATH unit. This field can have up to ten entries.
Duplicate entries are not valid.
IP Source Addr
Screening: IP Mask
This field contains the IP mask that determines which IP subnet the unit belongs to. If a mask is present, any other IP host in the subnet is allowed to communicate with the unit. This field can have up to ten entries. Duplicate entries are not valid.
Trap Destination:
IP Addr
This field tells you which IP addresses the unit sends traps to. This field can have up to ten entries. Duplicate entries are valid.
Trap Destination:
VC
This field tells you which virtual circuit (VC) the unit uses to send out traps.
Basic network management (Telnet)
127
About IP addressing
To send and receive data across the IP network, every device (or host, in IP terminology) on the network requires a unique IP address. An IP address consists of four decimal numbers between 0 and 255, separated by periods. Each address is composed of two parts: a network part, which identifies the subnet containing the host; and a host part, which identifies the actual host device.
An IP address mask, also called a netmask, is used in conjunction with the IP address to determine which part of the address is the network part and which is the host part. In the examples in this guide, the netmask is 255.255.255.0, which sets the first three numbers of the IP address as the network part and the last number as the host part.
Typically, you get IP addresses from your network or system administrator or Internet
Service Provider (ISP). If you are the network or system administrator, get a network address from the InterNIC. Kentrox cannot provide you with IP addresses. Assign an
IP address to each host in the IP network.
Sample configuration with
IP addresses
The following sample illustrates how to assign network interface channels on the
M-PATH CSU; configure the M-PATH network interface; assign IP addresses and IP netmasks; set up a Telnet password, and enable SNMP.
For more information on assigning channels and selecting the IP network interface, see
Chapter 5 . For more information on setting the IP addresses and netmasks, see
IP addresses and netmasks” on page 132
. For more information on configuring network interfaces with the NETIF command, see
“Selecting the IP network interface” on page 130
.
In this example, the remote wireless site has a radio with a data port and an M-PATH CSU mounted in a two-slot shelf. The NMS, going through a router at the switching site, can manage the M-PATH at the remote site with in-band IP management using DS0 channel
24. Channel 23 goes to the data port and channels 1-22 are used for voice traffic. (See
Figure 9 .) Compare this example with the configuration on
Figure 9—In-band managed wireless site
FT1,
22 DS0
M-PATH CSU in shelf
196.65.1.3
Radio
T1
3 / 1 / 0
DCS
Router
196.65.1.13
DLCI = 347
NMS
196.65.1.4
Data Port, 1 DS0
Cell Site Management
Site
128
Chapter 8: Using network management
■
■
■
■
■
■
Configuration Commands
■
The ANI1-22:V command assigns network interface channels 1-22 to the terminal interface, voice-type channels.
■
The ADP1:64,23 command assigns network interface channel 23 to the data port at
56 Kbps.
The ANI24:I command sets network interface channel 24 to idle.
The NETIF D:24,64 command assigns the idle channel 24 to a 64 Kbps IP management data link.
The LXA command loads network interface configuration Table A into the unit.
The IPA:D, 196.65.1.3 command assigns IP address 196.65.1.3 to the IP data link.
The IPM:D, 255.255.255.0 command assigns the data link IP netmask.
The SSA:D, 196.65.1.4 command insures that only the management workstation illustrated in the figure can manage the M-PATH.
■
The ADD:T,196.65.1.13, 347 command sends traps to the router over DLCI 347.
(Your Frame Relay service provider will tell you which DLCI to use.)
■
The TPW: KENTROX command sets the Telnet password to KENTROX (all caps).
■
The ESNMP command enables the SNMP agent on the M-PATH CSU.
Basic network management (Telnet)
129
Selecting the IP network interface
You select the IP network interface by using the NETIF command. Settings for the nearend and far-end M-PATH units must be identical. There are two forms of the command, depending on whether you want an IP network interface that includes the IP management data link. You must have superuser or configuration privileges to use either form.
IP network interfaces that include a data link
The near-end unit (more closely linked to the network management system) is configured as SD, ED, ESD, or PSD. The far-end unit is configured as D. This prevents the M-PATH units from trying to manage each other, or two different control devices trying to manage the same M-PATH unit.
If the IP network interface includes a data link, you must enter an IP address and IP net-
mask for the data link (see “Setting the IP addresses and netmasks” on page 132 ).
The data link can be assigned to:
■
The Facility Data Link (FDL) which runs at 4 Kbps and is available only if both the near-end and far-end M-PATH units are using Extended Super Frame (ESF) NI framing (see
“Specifying NI framing format” on page 48 ).
■
One of the T1 channels (time slots) that is idle or assigned to a data port. You can set a channel to 56Kbps or 64 Kbps; if the channel has been assigned to a data port, use
).
If the channel is idle, the data link runs at 56 Kbps or 64 Kbps, as you set it with the
NETIF command.
If the channel is assigned to a data port and is set to 56 Kbps, the data link uses the
“spare “ 8 Kbps on that channel. Data port timing (see
page 31 ) is not available if the
data link is assigned to a data port.
The command syntax is:
NETIF:p ,dl [,spd ]
p
If the channel is assigned to a data port and is set to 64 Kbps, the data link takes
8 Kbps and the actual data link transfer rate is automatically reduced to 56 Kbps.
You do not have to reconfigure either unit, and you can still get 64 Kbps on all the
other data port channels. Data port timing (see page 31
) is not available if the data link is assigned to a data port.
Specify the protocol:
D (Data Link)
SD (SLIP and Data Link)
ED (Ethernet and Data Link)
ESD (Ethernet, SLIP and Data Link)
PSD (PPP, SLIP and Data Link)
dl spd
Enter F to use the Facility Data Link (FDL) or a number from 1 to
24 to select a time slot for the data link.
Enter 56 to set the data link data rate to 56 Kbps, or 64 to select 64
Kbps. If you specified F, this value is ignored.
130
Chapter 8: Using network management
Setting the Telnet password
IP network interfaces that do not include a data link
The command syntax is:
NETIF:p
p
Specify the protocol:
S (SLIP)
E (Ethernet)
PS (PPP and SLIP)
ES (Ethernet and SLIP)
N (none)
IP network interfaces that include Ethernet (M-PATH 538 only)
The E (Ethernet), ES (Ethernet and SLIP), ED (Ethernet and Data Link), and ESD (Ethernet, SLIP and Data Link) protocols, all listed above, are available only on the M-PATH
538. If you select any of these options, you need to set an Ethernet IP address and netmask using the IPA:E and IPM:E commands.
IP network interfaces that include PPP or SLIP (M-PATH 538 and 537)
■
The PS (PPP and SLIP) and PSD (PPP, SLIP and Data Link) protocols use PPP to manage the controller, SLIP to manage M-PATH 537 units in the shelf, and Data
Link protocol (if PSD is selected) to manage the far-end unit.
■
The S (SLIP) and SD (SLIP and Data Link) protocols use SLIP to manage the controller and the configurable units in the shelf, and Data Link protocol (if SD is selected) to manage the far-end unit.
Managing M-PATH 538 and 537 units with ASCII mode
If you prefer to use ASCII mode instead of IP to manage M-PATH units, select N (None) for all units in the shelf.
The M-PATH Telnet server is enabled and disabled via the Telnet password. A null password (i.e. “”, string length of zero) disables Telnet. Any non-null string enables Telnet.
The Telnet password can be up to 15 characters long.
To access the unit via Telnet, the Telnet password must be a non-null string and the IP network interface must be enabled and configured properly.
You set the Telnet password using the TPW command. The syntax for the command is shown below. You must have superuser privileges.
TPW:str
str
Enter the Telnet password. The password can be up to 15 characters long including spaces (trailing spaces are not truncated).
Basic network management (Telnet)
131
Setting the IP addresses and netmasks
TIP
If you do not know what your IP address and IP netmask should be, ask your network administrator or system administrator.
If you do not have a network or system administrator, obtain a set of valid IP addresses from your Internet service provider.
Kentrox cannot issue
IP addresses.
Every device (or host) on an IP network requires an IP address and IP netmask. You need to set an IP address and netmask for every IP network interface you select (see the
NETIF command).
IP address
The IP address is the unique address for a device in the IP network. The default IP address is 192.0.2.1. You must change this IP address before adding the unit to an IP net-
work.
You set the IP address by using the IPA command. You must have superuser or configuration privileges. The changed IP address takes effect only after you have logged out.
The command syntax is:
IPA:p, ipa
p
Options are E (538 only), C, or D.
C assigns the IP address to the control port interface for SLIP or
PPP, and to the local unit for data link communications; E assigns the IP address to the Ethernet interface; and D assigns the IP address for data link communications.
The use of D depends on the way you have set NETIF. When
NETIF is set to SD, ED, ESD, or PSD, then IPA:D designates the
remote unit’s data link IP address. When NETIF is D alone, then
IPA:D designates the data link IP address of the local unit that you are currently configuring. When NETIF is set to any value that does not include D, do not set a data link IP address.
ipa
Enter the IP address using the format nnn.nnn.nnn.nnn, where nnn can be any number from 0 to 255, inclusive. An IP address of
0.0.0.0 is not valid.
When communicating via the Ethernet interface, you need to assign the controller an
Ethernet IP address and a serial port IP address (for communicating to other units in the shelf via SLIP). The two IP addresses must be on different subnets.
When managing a far-end unit over the data link, you need to assign a data link IP address
(see definition above). The near-end unit’s control port IP address and the far-end unit’s data link IP address must be on the same subnet.
All units in a daisy chain need control port IP addresses in the same subnet. If you are using auto-configuration, all configurable units in the daisy chain are automatically assigned compatible control port IP addresses when inserted into the shelf.
132
Chapter 8: Using network management
IP netmask
An M-PATH unit uses the IP netmask to determine if a packet is destined for a device on the same IP network as itself. If the packet is destined for its network, the unit can send the packet directly to the host. If the packet is destined for a different network, the unit sends the packet to the IP address of its default router.
The control port and data link use the same IP netmask. You change this netmask with the
C parameter.
The default IP netmask is 255.255.255.0. Changes to the IP netmask take effect upon logout.
You set the IP netmask by using the IPM command. You must have superuser or configuration privileges. The command syntax is:
IPM:c, mask
c
can be E (538 only) or C.
C assigns the IP netmask to the control port and data link interface.
E assigns the IP netmask to the Ethernet interface.
mask
The IP netmask. It takes the form nnn.nnn.nnn.nnn, where nnn can be any number from 0 to 255, inclusive. The default is
255.255.255.0.
When configuring a 538 controller to use the Ethernet interface, you should specify both a control port/data link netmask and an Ethernet IP netmask.
Basic network management (Telnet)
133
Setting the default router IP address
Hosts that are on the same IP network can send packets to each other directly. If a host wants to send packets to a host that is not on the same network, the packets must be sent to a router that understands the topography of the network. The M-PATH needs to know the address of its default router in order to send packets to another network. This could occur if an SNMP management station is on a different network and is trying to retrieve information from an M-PATH unit.
If a packet is destined for a different network, the unit sends the packet to the IP address of its default router. If there is no default router defined, or if the definition is invalid, the unit discards the packet.
In order for the default router to send a packet to the proper network, you have to configure the default router’s static route table. If the default router isn’t connected directly to the host, the default router has to link the host address with a forwarding address that will accept the packet and forward it to the host.
The static route table can also be used to forward packets to an M-PATH unit that does not have its own Ethernet IP address. In that case, the unit’s control port or data link IP address must be linked in the table with the controller’s Ethernet address.
NOTE
You should always set the address of the default router. If a default router does not exist and an M-PATH unit tries to send a packet to a host not on its subnet, the packet will be discarded. This is true for Ethernet, data link, PPP, and SLIP connections.
The default value for the default router address is 192.0.2.2.
If you are accessing the IP network via Ethernet, the controller’s default router must be on the same subnet as its Ethernet IP address. The default router address for the configurable units in the shelf must be the SLIP IP address of the controller.
If you are accessing the IP network via the control port, all units in the shelf must be set to the same default router, which must be on the same subnet as the terminal server.
For a far-end unit accessing the IP network over the data link, the default router is the near-end M-PATH CSU.
If you have enabled auto-configuration, the 538 controller at the head of the daisy-chain automatically sets up the default router addresses of downstream configurable units.
You set the default router by using the IPR command. The syntax for the command is shown below. You must have superuser or configuration privileges.
IPR:ipa
ipa
The default router address. It takes the form nnn.nnn.nnn.nnn, where nnn can be any number from 0 to 255, inclusive. A default router address of 0.0.0.0 is not valid.
134
Chapter 8: Using network management
Setting up IP source address screening
Adding an address or netmask to the IP screening list
Before you can enable IP screening, you must have at least one IP address in the screening list. The list can contain up to ten addresses. This list cannot contain multiple entries of the same address, unlike the SNMP trap host list. This list is empty at first power-up.
Adding a netmask to the IP screening list allows you to receive IP packets from any host on the same subnet as the IP address you specify.
You add an IP address to the IP screening list by using the ADD command. You must have superuser or configuration privileges. The command syntax is:
ADD:I:ipa[,mask]
I
ipa mask
Specify IP source address screening.
Add the specified IP address to the list.
Use this netmask to define the subnet the specified IP address belongs to, and accept IP packets from any host in that subnet.
See “Setting the IP addresses and netmasks” on page 132 for a
detailed description of the ipa and mask fields.
Enabling and disabling IP source address screening
M-PATH units can screen IP packets based on the source IP address. This security feature lets you screen out packets from any host that is not supposed to access the unit.
For instance, if you know that only network managers should access the M-PATH, you can add their host addresses to the IP screening list and lock out all other hosts by enabling
IP source address screening.
All source address screening commands (the commands discussed in the rest of this section) are found in the Advanced Management Configuration (AMC) menu.
You can enable IP source address screening after filling in the IP addresses allowed access to the M-PATH.
The default is address screening disabled.
You set the IP Source Address Screening using the SSA command. You must have superuser or configuration privileges. The command syntax is:
SSA:c
The c parameter specifies the address screening.
I
N
Screen based on IP source addresses.
No IP address screening.
Basic network management (Telnet)
135
Deleting an address from the IP screening list
Before you delete an address from the IP source screening list, you must disable IP source screening with the SSA command.This reduces the risk that you will accidentally delete the IP address of the host that you are using to access the M-PATH unit.
Enabling or disabling source address screening does not take effect until you log out and log back in.
You delete an address from the IP screening list by using the DEL command. You must have superuser or configuration privileges. The command syntax is:
DEL:I:ipa
I
ipa
Specify IP source address screening.
Delete the specified SNMP manager’s IP address from the list. See
“Setting the IP addresses and netmasks” on page 132 for a detailed
description of the ipa field.
or
DEL:I:*
Delete all entries in the list by using the * wildcard.
136
Chapter 8: Using network management
Configuring for SNMP
To enable the SNMP management capabilities of the M-PATH, the following parameters must be set:
■
■
■
Enable the SNMP Agent.
Set the SNMP community strings, if necessary.
Add the management hosts to the trap list.
NOTE
This section assumes you have already set up the M-PATH for an IP network. It includes: setting the IP address and netmask, setting the default router, and selecting the network interface.
Enabling and disabling the SNMP agent
The M-PATH has a fully functional internal SNMP agent. This agent supports MIB II and the DS1 MIB (RFC 1406), link-up, link-down, warm-start, and cold-start traps, and the
Kentrox DSU/CSU Enterprise MIB.
The IP network interface must be configured since SNMP only works over IP networks.
You enable and disable the SNMP agent by using the ESNMP and DSNMP commands, respectively. You must have superuser or configuration privileges.
A warm-start trap is generated by the M-PATH CSU whenever you transition its SNMP agent from disabled to enabled.
The agent is disabled by default.
ESNMP
DSNMP
Enable the SNMP agent.
Disable the SNMP agent.
Configuring for SNMP
137
Setting SNMP community strings
Configuring the
SNMP trap hosts
There are three SNMP community strings: read, write, and trap. The community strings are another form of (loose) security. If you want to prevent just any SNMP manager from retrieving data from the SNMP agent, you can change the read community string. Make sure that the SNMP managers you wish to have access have the same community strings as the ones on the M-PATH unit.
Read community string
The read community string controls who can read data from the agent. The default value is “public”.
Write community string
The write community string controls who can write data to the agent using SNMP Sets.
The default value is “private”.
Trap community string
The trap community string controls who can read a trap sent from the agent. The default value is “snmptrap”.
You set the SNMP community strings by using the RCS, WCS, and TCS commands. You must have superuser or configuration privileges. The command syntax is shown below.
The strings are allowed to have spaces in them, but you probably won’t want any as other management stations may not allow spaces in community strings.
RCS:str
WCS:str
TCS:str where str is 1 to 15 characters.
M-PATH units can send SNMP traps to multiple IP network hosts. In order to send SNMP traps, you must enable the M-PATH SNMP agent by using the ESNMP command (see
“Enabling and disabling the SNMP agent” on page 137 ).
There can be multiple entries of a single address in the SNMP trap list.
138
Chapter 8: Using network management
Adding an address to the SNMP trap host list
The SNMP trap host list contains the IP addresses of all IP network hosts that you want the M-PATH unit to send traps to. The SNMP trap host list is empty at first power-up.
You add an IP address to the SNMP trap list by using the ADD command.
If your unit is configured for NETIF=D and the IP management path goes straight to a trap host without communicating through an M-PATH unit, you must associate the path’s Data
Link Connection Identifier (DLCI) with the trap host’s IP address. Your carrier or network administrator should be able to provide the DLCI.
You must have superuser or configuration privileges. The command syntax is:
ADD:T:ipa[,dlci]
T
ipa
Specify SNMP trap list.
Add the specified IP address to the list.
dlci
See “Setting the IP addresses and netmasks” on page 132 for a
detailed description of the ipa and mask fields.
Enter the DLCI associated with the trap host’s IP address.
Deleting an address from the SNMP trap list
If there are multiple entries of a single address in the table, each entry must be deleted.
One deletion does not clear out all occurrences of that address.
You delete an address from the SNMP trap list by using the DEL command. The syntax for the command is shown below. You must have superuser or configuration privileges.
DEL:T:ipa
T
ipa
Specify SNMP trap list.
Delete the specified SNMP manager’s IP address from the list. See
“Setting the IP addresses and netmasks” on page 132 for a detailed
description of the ipa field.
or
DEL:T:*
Delete all entries in the list by using the * wildcard character.
Configuring for SNMP
139
Using SNMP traps
SNMP traps are like M-PATH alarm messages; they indicate alarm conditions in the network.
Configuration for
SNMP traps
■
■
To use SNMP traps, you must:
■
Connect the M-PATH to a TCP/IP network via Ethernet, over a SLIP or PPP connection on the control port, or via the data link.
Enable the M-PATH SNMP agent by using the ESNMP command (see
Enable or disable any combination of start, link, authentication, and enterprisespecific traps.
).
SNMP traps also need a destination IP address. You have ten possible trap destinations
defined by the trap host list (see “Configuring for SNMP” on page 137 ). At the trap host
destination there must be an SNMP network management application, such as SunNet
Manager, or HP OpenView. These programs understand SNMP and can interact intelligently with the M-PATH SNMP agent.
Types of
SNMP traps
M-PATH units can generate these trap types:
■
■
Start traps:
■
■
Warm-start
Cold-start
Link traps:
■
■
Link-down
Link-up
Authentication traps:
■
■
■
■
Telnet Password
SNMP Rd CommString
SNMP Wr CommString
IP Screen
Enterprise traps:
Excessive Error Rate (EER)
Power Feed A, Power Feed B
Warm-start trap
The warm-start trap is generated when you enter ESNMP (enable SNMP) from the command line for the previously disabled agent.
Cold-start trap
The cold-start trap is generated every time the M-PATH is power-cycled. Cold-start traps are not generated until ten seconds after the unit is power-cycled. This allows time for the hardware providing the low-level IP network interface to start up and stabilize before attempting to send a packet.
140
Chapter 8: Using network management
Link-down trap
A link-down trap is generated when ifOperStatus (MIB II) changes to down. Link-down traps are generated for the network interface, terminal interface, and data port.
Link-up trap
A link-up trap is generated when ifOperStatus (MIB II) changes to up. Link-up traps are generated for the network interface, terminal interface, and data port.
Telnet Password
A Telnet Password trap is generated when an incorrect Telnet password has been entered.
SNMP Rd CommString
A SNMP Rd CommString trap is generated when the M-PATH has read an incorrect
SNMP community string.
SNMP Wr CommString
A SNMP Wr CommString trap is generated when the M-PATH has written an incorrect
SNMP community string.
IP Screen
An IP Screen trap is generated when the M-PATH has received a trap or message from a device whose IP address is not on the Source Screening Address list.
NOTE
The events that generate the Telnet Password, SNMP Rd CommString, SNMP Wr
CommString, and IP Screen traps are also logged in the Security History report (see
“Interpreting the Security History report” on page 93
).
Excessive Error Rate
An Excessive Error Rate trap is generated whenever the Excessive Error Rate threshold is
exceeded (see “Specifying the error threshold evaluation window” on page 43 ). Excessive
Error Rate traps are generated for the network interface (NEER) and terminal interface
(TEER).
Power Feed A, Power Feed B
The M-PATH 538 controller generates a Power Feed A trap whenever it detects a loss of power from power feed A in the 12-slot shelf. (The trap has no meaning when the controller is installed in a two-slot shelf.) In the same way, a Power Feed B trap is generated when a loss of power from power feed B is detected. A 537 unit can not generate this trap.
See “Examining system status” on page 101
).
Using SNMP traps
141
MIB objects included in SNMP traps
SNMP allows any MIB object to be included in a trap. The M-PATH includes information on its status and that of the T1 line, to speed analysis. Each trap type includes different information.
Warm-start trap
A warm-start trap includes the ifDescr and ifIndex of all interfaces on the unit.
Cold-start trap
A cold-start trap includes the ifDescr and ifIndex of all interfaces on the unit.
■
■
■
■
■
Link-down trap for a T1 interface
A link-down trap for a T1 interface includes the following:
ifDescr — “T1 Network Interface”
ifIndex — this is the instance number for that interface
dsx1LineStatus — a bitmap of the T1 line’s current state
dsx1CurrentESs — the number of errored seconds for the current interval
dsx1CurrentUASs — the number of unavailable seconds for the current interval
■
■
Link-down trap for a data port interface
A link-down trap for a data port interface includes the following:
ifDescr — “Data Port 1 Interface”
ifIndex — this is the instance number for that interface
■
■
■
■
■
Link-up trap for a T1 interface
A link-up trap for a T1 interface includes the following:
ifDescr — “T1 Network Interface”
ifIndex —this is the instance number for that interface
dsx1LineStatus — a bitmap of the T1 line’s current state
dsx1CurrentESs — the number of errored seconds for the current interval
dsx1CurrentUASs — the number of unavailable seconds for the current interval
■
■
Link-up trap for a data port interface
A link-up trap for a data port interface includes the following:
ifDescr — “Data Port 1 Interface”
ifIndex — this is the instance number for that interface
■
■
■
Telnet Password authentication trap
The Telnet Password trap includes the following:
dsRpShrDateTime — the date and time the event occurred
dsRpShrEventType — “rpShrTelnetPassword” (Type 1)
dsRpShrComments — the source IP address of the unit that sent the incorrect
Telnet password
■
■
■
SNMP IP Screen authentication trap
The SNMP IP Screen trap includes the following:
dsRpShrDateTime — the date and time the event occurred
dsRpShrEventType — “rpShrSrcIpAddressScreen” (Type 2)
dsRpShrComments — the source IP address of the device that sent the message to the
M-PATH unit
■
■
■
SNMP Rd CommString authentication trap
The SNMP Rd CommString trap includes the following:
dsRpShrDateTime — the date and time the event occurred
dsRpShrEventType — “rpShrReadCommString” (Type 3)
dsRpShrComments — the source IP address of the unit that caused the event
■
■
■
SNMP Wr CommString authentication trap
The SNMP Wr CommString trap includes the following:
dsRpShrDateTime — the date and time the event occurred
dsRpShrEventType — “rpShrWriteCommString” (Type 4)
dsRpShrComments — the source IP address of the unit that caused the event
■
■
■
■
■
Set NI Excessive Error Rate trap
The Set NI Excessive Error Rate trap includes the following:
ifDescr — “Set NI Excessive Error Rate (NEER)”
ifIndex —this is the instance number for that interface
dsx1LineStatus — a bitmap of the T1 line’s current state
dsx1CurrentESs — the number of errored seconds for the current interval
dsx1CurrentUASs — the number of unavailable seconds for the current interval
■
■
■
■
■
Clear NI Excessive Error Rate trap
The Clear NI Excessive Error Rate trap includes the following:
ifDescr — “Clear NI Excessive Error Rate (NEER)”
ifIndex —this is the instance number for that interface
dsx1LineStatus — a bitmap of the T1 line’s current state
dsx1CurrentESs — the number of errored seconds for the current interval
dsx1CurrentUASs — the number of unavailable seconds for the current interval
■
■
■
■
■
Set TI Excessive Error Rate trap
The Set TI Excessive Error Rate trap includes the following:
ifDescr — “Set TI Excessive Error Rate (TEER)”
ifIndex —this is the instance number for that interface
dsx1LineStatus — a bitmap of the T1 line’s current state
dsx1CurrentESs — the number of errored seconds for the current interval
dsx1CurrentUASs — the number of unavailable seconds for the current interval
Using SNMP traps
143
Traps and alarm conditions
■
■
■
■
■
Clear TI Excessive Error Rate trap
The Clear TI Excessive Error Rate trap includes the following:
ifDescr — “Clear TI Excessive Error Rate (TEER)”
ifIndex —this is the instance number for that interface
dsx1LineStatus — a bitmap of the T1 line’s current state
dsx1CurrentESs — the number of errored seconds for the current interval
dsx1CurrentUASs — the number of unavailable seconds for the current interval
A/B On Power Transition trap (M-PATH 538 only)
The A/B On Power Transition trap includes the following:
■
dsSsPowerStatus — indicates that power has turned on
A/B Off Power Transition trap (M-PATH 538 only)
The A/B Off Power Transition trap includes the following:
■
dsSsPowerStatus — indicates that power has turned off
The following table correlates unit and alarm conditions to traps.
Alarm Condition
NI LOS
NI OOF
NI AIS
NI YEL
NI EER
TI LOS
TI OOF
TI AIS
TI YEL
TI EER
DP LOS
Agent-enabled
Power-up
Trap
Link down port 1
Link down port 1
Link down port 1
Link down port 1
Excessive Error Rate trap
Link down port 2
Link down port 2
Link down port 2
Link down port 2
Excessive Error Rate trap
Link down port 3
Warm-start trap
Cold-start trap
144
Chapter 8: Using network management
C H A P T E R
9
Quick reference
This chapter contains:
■
■
■
A listing of all menus and commands available through the command line interface
A summary of commands accessible through an ARC login
A description of how the M-PATH generates T1 alarms, based on signal conditions at the network and terminal interfaces
■
A complete listing of the M-PATH specifications
145
Command line menus and commands
The command line interface provides eighteen “help” menus. These menus group the various commands by function and describe the use and syntax of each command.
To display a menu, simply enter the one- or two-letter acronym for the menu title.
Main menu (MM)
MPATH 53n Version 1.nn Copyright (c) 1996 Kentrox
ADDRESS: 00:00:000 NAME: PORTLAND,OR
MM - Main Menu
SS - System Status and Remote Menu
R - Reports Menu
LM - Local Maintenance Menu
RM - Remote Maintenance Menu
AC - Alarm Configuration Menu
CC - Control Port Configuration Menu
DC - Data Port Configuration Menu
FC - Fractional T1 Configuration Menu
MC - Management Configuration Menu
NC - NI Configuration Menu
PC - Password Entry and Configuration Menu
SC - System Configuration Menu
TC - TI Configuration Menu
^D - Logout
^D<xx>:<yy>:<zzz>^E - Address Another Unit
MM>
System Status and Remote menu (SS)
SYSTEM STATUS AND REMOTE MENU
ARC/DRC - Access to/Disconnect from Remote Unit Control
S - System Status Screen Command
SSV - View System Setup
Reports menu (R)
REPORTS MENU
UNSR / UNLR
UTSR / UTLR
CNSR / CNLR
FESR / FELR
- User NI Short/Long Performance Report
- User TI Short/Long Performance Report
- Carrier NI Short/Long Performance Report
- Far End PRM Short/Long Performance Report
NSR:[z]
TSR:[z]
AHR
SHR
- User NI Statistical Performance Report
- User TI Statistical Performance Report z = Display Report then Zero Counts (Optional)
- Alarm History Report
- Security History Report
PL:<len|style> - Set Page Length, <len> = 20 .. 70 (or 0 = Off), or
<style> = P (Page Break), M (More), or V (View)
R>
146
Chapter 9: Quick reference
Local Maintenance menu (LM)
LOCAL MAINTENANCE MENU
SLL - Set Line Loop Back
SPL - Set Payload Loop Back
SLO - Set Local Loop Back
STI - Set TI Loop Back
SDP<n> - Set Data Port Loop Back at Data Port, n=1
SDT<n> - Set Data Terminal Loop Back at Data Port, n=1
RLB - Reset Loop Backs
DST - Do Self Test
Remote Maintenance menu (RM)
REMOTE MAINTENANCE MENU
SRL - Set Remote Line Loop Back
SRP - Set Remote Payload Loop Back
SRDP<n> - Set Remote Data Port Loop Back, n = 1
RST1 - Reset Remote Loop Back
SQC/S3C/S1C/S0C - Send Test Codes at NI: QRS, 3/24, 1, 0
S5C<n> - Send 511 Test Code in Data Port <n> Bit Stream
S2C<n> - Send 2047 Test Code in Data Port <n> Bit Stream
RTC - Reset Test Codes
BTQ/BT3/BT1/BT0 - Activate BERT using Test Codes: QRS, 3/24, 1, 0
BT5<n> - Activate BERT using 511 at Data Port n = 1
BT2<n> - Activate BERT using 2047 at Data Port n = 1
Alarm Configuration menu (AC)
ALARM CONFIGURATION MENU
EAM / DAM - Enable/Disable Alarm Messages
EYL / DYL - Enable/Disable YELLOW Activating an Alarm
DACT:<n> - Alarm Deactivation time in seconds, n = 1..15
EST:<n> - Errored Second Threshold, n = 0 .. 900
UST:<n> - Unavailable Second Threshold, n = 0 .. 900
ST15/ ST60 - Set Threshold Timing to 15 or 60 Minutes
ACV - View Alarm Configuration
Control Port Configuration menu (CC)
CONTROL PORT CONFIGURATION MENU
EE / DE - Enable/Disable Character Echo
CCV - View Control Port Configuration
Command line menus and commands
147
Data Port Configuration menu (DC)
DATA PORT CONFIGURATION MENU
EDI<n> / DDI<n> - Enable/Disable Data Inversion at Data Port, n=1
INTF<n>:<intf> - Interface at Data Port, n=1
intf = V (V.35), E (EIA-530),
D (V.35 DataSMART Compatible)
SCLK<n>:<clk> - Source Clock at Data Port, n=1
clk = I (Internal), E (External)
TCLK<n>:<cmd> - Transmit Clock Inversion at Data Port, n=1
cmd = E (Enable), D (Disable)
RCLK<n>:<cmd> - Receive Clock Inversion at Data Port, n=1
cmd = E (Enable), D (Disable)
IDL<n>:<char> - Idle Character at Data Port, n=1
char = 7E (0x7E), 7F (0x7F), FF (0xFF)
DPLOS<n>:<los> - LOS Input Signal at Data Port, n=1
los = R (RTS), D (DTR), B (Both), N (No Processing)
DCV - View Data Port Configuration
Fractional T1 Configuration menu (FC)
FRACTIONAL T1 CONFIGURATION MENU
<table>DP<port>:<rate>[,<nicn>]
- DP=Assign NI Channel Map for Data Port
table A/B - Tables A or B Containing Channel Assignment
port 1 - Data Port Number
rate 56/64 - Channel Rate in 1000 bps
nicn 1 .. 24 - NI Channel numbers assigned to Data Port
1,3,5,... - Can be alternating DS0 channel numbers or
1-24 - a contiguous range.
<table>NI<nicn>:<ticn>,<nicn>:<ticn>, ...
- NI=Assign NI Channels to TI or IDLE
table A/B - Tables A or B Containing Channel Assignment
nicn 1 .. 24 - NI Channel numbers
ticn V,D,I - Voice/Data on TI Channel or I for Idle
CPAB / CPBA - Copy A to B or B to A
LXA / LXB - Load and Execute Table A or B
TAV / TBV - View Table A or B
TXV - View Executing Channel Assignment
Management Configuration menu (MC)
MANAGEMENT CONFIGURATION MENU
TPW:<str> - Set Telnet Password, str=0 to 15 characters
0 characters disables Telnet
NETIF:<p>[,<dl>[,<spd>]]
- Set IP Network Interface Paths
<p> = N, E, PS, S, D, ES, ED, ESD, PSD, or SD
N = None, E = Ethernet, P = PPP, S = SLIP,
D = Datalink - if Datalink, use dl and spd
<dl> = F (FDL), 1-24 (DS0 Tslot) - if DS0, use spd
<spd> = 56 (56k of DS0 Tslot), 64 (All of Tslot)
IPR:<ipa> - Set Default Route IP Address
IPA:<p>,<ipa> - Set IP Addresses
IPM:<p>,<mask> - Set IP Masks
p = E (Ether), C (PPP/SLIP), D (Datalink)
<ipa> and <mask> = n.n.n.n, n = 0 .. 255 (dec)
<ipa> for Datalink is IP Address of remote unit
<mask> is the same for Ctl Port and Datalink
AMC - Advanced Management Configuration Menu
MCV - View Management Configuration
148
Chapter 9: Quick reference
Advanced Management Configuration menu (AMC)
ADVANCED MANAGEMENT CONFIGURATION MENU
ESNMP/DSNMP - Enable/Disable SNMP Agent
TCS:<str> - Set SNMP Trap Comm String, str=1 to 15 characters
RCS:<str> - Set SNMP Read Comm String, str=1 to 15 characters
WCS:<str> - Set SNMP Write Comm String, str=1 to 15 characters
SSA:<p> - Set Packet Screening via Source Address
p = I (IP Addr), N (None)
TRAP:<c>,<t> - SNMP Trap Generation c = E (Enable), D (Disable)
t = S (Start), L (Link), A (Auth), E (Enterprise)
ADD:T,<ip>[,dlci] - Add IP Address to Trap Dest List
<dlci> = optional identifier for Data Link Traps
ADD:I,<ip>[,mask] - Add IP Address to Screening List
DEL:<l>,<ip> - Delete Address from Screening or Trap Dest Lists
<l> = I (IP Screen List), T (Trap Dest List)
<ip> and [mask] = n.n.n.n, n = 0 .. 255 (dec)
[mask] used only for IP Screen List and is optional
AMCV - View Advanced Management Configuration
Network Interface Configuration menu (NC)
NI CONFIGURATION MENU
NSF/NESF/NERC - NI SF/ESF/Ericsson Framing Format
NAMI / NB8 - NI AMI/B8ZS Line Coding
EPRM / DPRM - Enable/Disable T1.403 PRM Generation out NI
FKA / UKA - Framed/Unframed Keep Alive
EYEL / DYEL: - Enable/Disable YELLOW Activation out NI
ADR54:<Trgt> - 54016 Address = C(CSU), D(DSU), or B(Both)
E54 / D54 - Enable/Disable 54016 Mode
Line Build Out
NL0 - 0.0 dB
NL1 - 7.5 dB
NL2 - 15.0 dB
NCV - View NI Configuration
Password Entry and Configuration menu (PC)
PASSWORD ENTRY AND CONFIGURATION MENU
EPS:<password> - Enter Password
password = 6 to 12 characters
APS:<access>:<password> - Add Password
access = SA - Super User
CA - Configuration
MA - Maintenance
password = 6 to 12 characters
DPS:<password> - Delete Password
password = 6 to 12 characters, or * for all
PUV - View User Access Privilege
PCV - View Password Configuration
Command line menus and commands
149
System Configuration menu (SC)
SYSTEM CONFIGURATION MENU
SD:<mm>,<dd>,<yy> - Set Date (Warning: This also clears reports)
ST:<hh>,<mm> - Set Time (Warning: This also clears reports)
SN:<id> - Set Name
EAC / DAC - Enable/Disable Auto Configuration
SAC:<xx>,<yy>,<zzz> - Send Auto-Configure Packet to unit
<slot>:<shelf>:<group>, * is all units
EDC / DDC - Enable/Disable DataSMART Compatibility
CLK:<src> - Clock Source, src = L (Loop), C (CSU Thru)
T (TI Receive), I (Internal), 1 (DP1)
ALGOUT:<n> - Autologout, n = 0 .. 60 minutes
ZALL - Zero All Counters used in User Reports
TSWDL:<i> - Download program from a file via TFTP
i = n.n.n.n, n = 0..255 (dec), the
IP address of the TFTP host system
BOOT:<b> - Re-boot the system
b = A (Active FLASH) or I (Inactive FLASH)
WYV - View "What's Your Version" Information
RSD - Reset System to Default Values
SCV - View System Configuration
Terminal Interface Configuration menu (TC)
TI CONFIGURATION MENU
TSF/TESF/TERC - TI SF/ESF/Ericsson Framing Format
TAMI/TB8 - TI AMI/B8ZS TI Line Coding
TIDL:<c> - Idle Code, c = 00-FF Hex
TI Equalization
TE0 - 0 - 133 ft
TE1 - 133 - 266 ft
TE2 - 266 - 399 ft
TE3 - 399 - 533 ft
TE4 - 533 - 655 ft
TCV - View TI Configuration
150
Chapter 9: Quick reference
Commands available via ARC
You can log into a remote M-PATH or DataSMART unit by using the ARC command.
This command establishes the remote login via the FDL (facility data link) line in the T1 signal. The T1 framing format must be ESF (extended super frame). The DRC command disconnects the remote login.
NOTE
If you are logging into an M-PATH unit, you can use a data link within time slot 1 through
24 of the T1 signal. In this case, the framing format can be either SF or ESF. Use the
NETIF command to select a data link time slot.
The ARC command’s actions are affected by the EDC/DDC commands. The default power-up value is DataSMART 72000 series compatible, including DataSMART MAX and SPort. No action is required.
EDC (enable DataSMART 78000 series compatibility) command
Use the EDC command prior to executing ARC to specify that you are connecting to a
DataSMART 78000 series DSU/CSU. Executing EDC has the following effects:
■
Remote data loopbacks: all SRDP data port commands and the next RST1 command following SRDP generate the 127 code in a format compatible with DataSMART
78000 series DSU/CSUs. The code is transmitted continuously for 10 seconds or until the loop action is verified.
■
T1.403 remote payload loopbacks: if the DataSMART 78000 series DSU/CSU is the remote plug-in, then the M-PATH does not expect loopback retention codes to be transmitted from the DataSMART unit.
DDC (disable DataSMART 78000 series compatibility) command
Use the DDC command to disable DataSMART 78000 series DSU/CSU compatibility and restore ARC compatibility with DataSMART 72000 series units, including MAX and
SPort. Executing DDC has the following effects:
■
Remote data loopbacks: all SRDP commands and the next RST1 command following SRDP generate the code in a format compatible with Annex B of T1.403-1994.
The code is transmitted for approximately 2.5 seconds, followed by a transmission of all ones lasting approximately 2.5 seconds. Since the remote plug-in is required to perform the loop activity within 2 seconds of receiving the all-ones code, the M-
PATH sends a momentary loop code again after the 2.5 seconds of all ones to confirm the loop actions. If ten seconds elapses before the loop action is verified, the loop is considered unverified. Setting and resetting remote data port loopbacks may not be reliable if this setting is incorrect.
■
T1.403 remote payload loopbacks: the M-PATH expects retention codes as defined in T1.403-1994. If they are not received (as from a DataSMART 78000 series plugin) the plug-in actuates the loopback and immediately resets it.
Commands available via ARC
151
Command compatibility
DataSMART 78000 series DSU/CSU compatibility
You can access most M-PATH commands via an ARC remote login. The only commands you cannot access are those that could potentially break the FDL link, or those that set up the network interface or the terminal interface. The commands that you cannot access through ARC are:
M-PATH menu
System Status menu
Local Maintenance menu
Remote Maintenance menu
NI Configuration menu
System Configuration menu
TI Configuration menu
Commands not accessible via ARC
EDC, DDC
DST, SDP, SDT, SLL, SLO, SPL, STI
BTC, SRP, SRL, SRDP, SQC, S0C, S1C, S2C,
S3C, S5C, RTC, RST1
NAMI, NB8, NERC, NESF, NL0, NL1,
NL2, NSF
MCSWDL
TAMI, TB8, TERC, TE1, TE2, TE3, TE4,
TESF, TSF
You can execute only a subset of the commands for the DataSMART 78000 series DSU/
CSU via an ARC remote login. The subset consists of the commands found on the
M-PATH Control Port Configuration menu and on its Status and Remote menu.
M-PATH menu
Commands accessible via ARC
Command functions
S System Status Screen command System Status and
Remote menu
Fractional T1
Configuration menu
■
■
CPA/CPB Copy A to B or B to A
LXA/LXB
TAV/TBV
TXV
ADP1/BDP1
ANI/BNI
Load and execute table A or table B
View table A or table B
View executing channel assignment
Assign channels to data port in table A or table B
Assign channels to terminal or idle in table A or table B
The FC command works only when an M-PATH or a DataSMART 72000 series
DSU/CSU is the local unit. The FC command returns a DataSMART 78000 series
DC menu from a DataSMART 78000 series DSU/CSU.
The DC command returns an FC menu from an M-PATH or a DataSMART 72000 series DSU/CSU and a DC menu from a DataSMART 72000 series DSU/CSU.
152
Chapter 9: Quick reference
T1 alarms and signal processing
This section describes how the M-PATH transitions into and out of an alarm state. It also describes in detail the alarms that can occur at the network and terminal T1 interfaces and the signal conditions that cause them.
NOTE
For a complete listing of all alarms generated by the M-PATH and appropriate troubleshooting procedures, refer to
What happens when alarms occur
How alarms are generated
When the M-PATH transitions to an alarm state, it performs various actions:
■
■
It illuminates appropriate LEDs on the front panel.
It updates the System Status display with status information about the alarms and signal conditions at the network interface, terminal interface, and data ports.
■
It outputs an SNMP trap or an alarm message to the control device (if traps or messages are enabled) and logs the alarm message in the Alarm History report.
■
It transmits yellow alarms and idle code out the interfaces and data ports as appropriate.
■
It switches the clock source to internal master timing, if the condition obstructs the clocking source.
The M-PATH generates alarms based on error events that occur in an input signal. Error events are also referred to as signal conditions. For instance, a loss of signal event (LOS) is also referred to as an LOS signal condition. A signal condition is a current, instantaneous status of the received signal at the interface. The signal condition may persist, may be intermittent, or may disappear immediately.
If a signal condition persists or is intermittent but frequent, the M-PATH transitions into an alarm state, a process called “alarm integration.” The algorithm that controls alarm integration is designed to prevent alarms from being raised every time a signal condition occurs briefly, and to prevent the alarm from being deactivated every time the signal condition temporarily flickers off.
The alarm integration algorithm
The alarm integration algorithm uses two values: the alarm integration time and the decay rate. (On the M-PATH the alarm integration time is set to 2.5 seconds and the decay rate is 1/5.)
The algorithm maintains a count for each signal condition. Whenever a signal condition exists, time accrues to the count for that signal condition. For instance, if the OOF signal condition exists for 1 second, 1 second is accrued to the OOF count. Time spent out of the signal condition is multiplied by 1/5 (the decay rate) and subtracted from the count, which has a minimum value of 0. When the count exceeds 2.5 (the alarm integration time), the transition to an alarm state occurs.
The alarm integration algorithm is defined in detail in AT&T 62411.
T1 alarms and signal processing
153
154
Chapter 9: Quick reference
Transitioning out of the alarm state
When a signal condition that has produced an alarm goes away, the alarm persists until the condition has been absent for a period of time referred to as the alarm deactivation time.
The alarm deactivation time is user-configurable and by default is 15 seconds. (See
“Setting the alarm deactivation time” on page 43
for more information.)
Alarm reporting
The M-PATH produces an alarm message each time a line transitions to a new alarm state.
The “CLR” message is not sent until all alarms on a particular interface clear. All alarm messages are output to the device connected to the control port and are logged in the
Alarm History report. To see the Alarm History report, type AHR at the command line.
You can examine the current status and track the changing conditions on an interface using the System Status report (type S at the command line). This report shows the current alarm state of the M-PATH as well as the signal condition of the input and output signal at all interfaces. The status report is updated once a second upon any changes to the alarm state or signal conditions. You can also track system status from the LCD display on the
front panel of the M-PATH. See “Examining system status” on page 101
for more information.
A received T1 signal is classified as being in one and only one alarm state at a time. Alarm states have a priority. If the signal satisfies more than one of the requirements for an alarm state, the higher priority alarm applies. Because of this, and because of the delay of deactivation of an alarm, the System Status report could contain an entry in which an interface is in an alarm state that does not match the signal condition.
For example, suppose the alarm deactivation time period is set to 15 seconds, and suppose the signal condition for the NI received signal is AIS. After the alarm integration requirements are met, the line is declared to be in the AIS alarm state. Now suppose that the signal condition changes from AIS to OOF. At this point the M-PATH will add a new entry to the status report to show the change in the signal condition. However, in that same entry, the alarm condition will be shown as AIS because the alarm deactivation time period has not passed.
Now assume the OOF condition persists for 2.5 seconds, and thus has satisfied the conditions for alarm integration. Because the OOF has a lower priority, and because of the
15-second deactivation period for alarms, the alarm state will still be AIS. However, once the 15 seconds have passed, the alarm state will transition from AIS to OOF, and the
M-PATH will add a new entry to the status report.
Signal conditions
The table below lists the signal conditions for the M-PATH in priority order, highest priority first. A received T1 signal can be in one and only one of the signal conditions at a time.
Condition
LOS
AIS
OOF
EER
YELLOW
Good Signal
Definition
Loss of Signal. No pulses are being received. The LOS signal condition starts upon receipt of 192 consecutive spaces or zeros. The
LOS signal condition clears when a the signal contains 32 consecutive bits with at least 4 ones and no more than 15 consecutive zeros.
Alarm Indication Signal. A signal with a 99.9% ones density for a minimum of 3 milliseconds and no framing detected is being received.
The AIS condition is detected in the presence of a 1 x 10
-3 bit error rate. An AIS condition is declared when both out-of-frame and all 1s conditions are present at the interface. The AIS condition clears when either the OOF, all 1s, or both conditions clear.
Out of Frame. The received signal does not contain a T1 framing pattern. The OOF signal condition is declared when two out of four frame bits are in error (SF and Ericsson framing) or when two out of six frame bits are in error (ESF framing). The OOF signal condition clears when a reframe occurs.
Excessive Error Rate. A framed T1 signal with a event error rate exceeding the user-supplied threshold is being received. This condition clears when the next time interval’s error count is less than the threshold.
The received signal contains the yellow alarm pattern in bit two of each DS0 (SF framing) or a yellow alarm code word in the ESF Data
Link (ESF framing). The condition clears when the yellow alarm pattern is no longer detected in the received signal.
A framed T1 signal with none of the above listed signal conditions.
T1 alarms and signal processing
155
Alarms
For each of the signal conditions described in the previous table there is an alarm state.
The table below lists the alarms for the M-PATH in priority order, highest priority first.
Note that, as shown in the table, not all alarms use the alarm integration algorithm described on
.
Alarm
LOS
AIS
OOF
Yellow
Alarm
EER
Clear
Definition
The LOS alarm starts upon a total of 2.5 seconds of alarm integration time spent in the LOS signal condition (the alarm integration time has a decay rate of 1/5 in case of an intermittent LOS signal condition). The
LOS alarm clears after a continuous time period of n seconds with no
LOS signal condition, where n is the alarm deactivation time period set by the user via the DACT command.
The AIS alarm starts upon a total of 2.5 seconds of alarm integration time spent in the AIS signal condition (the alarm integration time has a decay rate of 1/5 in case of an intermittent AIS signal condition). The
AIS alarm clears after a continuous time period of n seconds with no AIS signal condition, where n is the alarm deactivation time period set by the user via the DACT command.
The OOF alarm starts upon a total of 2.5 seconds of alarm integration time spent in the OOF signal condition (the alarm integration time has a decay rate of 1/5 in case of an intermittent OOF signal condition). The
OOF alarm clears after a continuous time period of n seconds with no
OOF signal condition, where n is the alarm deactivation time period set by the user via the DACT command.
The yellow signal alarm is declared after receiving the yellow signal for
1 second. Once declared, the alarm stays active for a minimum of one second. It is cleared upon detection of an input signal without the yellow alarm pattern present.
The EER alarm starts immediately upon entering the EER signal condition. The EER alarm clears after a continuous time period of n seconds with no EER signal condition, where n is the alarm deactivation time period set by the user via the DACT command.
None of the above listed alarms is active.
156
Chapter 9: Quick reference
Specifications
Table 9—Environmental specifications
Temperature
Powering
Parameter
Storage
Operating
AC input range
DC input range
Power interruptions
Specification
-20°C to 66°C (5% to 65% RH)
-20°C to 60°C (5% to 90% RH, non-condensing)
120 to 240 VAC, 47 to 63 Hz (when optioned with AC power)
24 to 48 VDC (when optioned with DC power)
Loss of power does not damage the plug-in.
Loss of power for less than five years does not change the configuration settings which may have been set by the user. Loss of power for less than ten hours (nominal) does not affect the real-time clock setting.
Table 10—Electrical interface specifications - network interface
Parameter Specification
Common
Input Only
Output Only
Line rate
Line Code
Line Impedance
Lightning Protection
Framing Format
Input Level
Input Jitter Tolerance
Output Level
Output Signal
Line Build Out
Output Jitter
Jitter Transfer
Pulse Density
Internal or external clock; 1.544 Mb/s + 50 bps
When timing is derived from input signal: 1.544 Mb/s + 200 bps
Output line rate follows input line rate.
AMI or B8ZS (selectable).
100 ohms + 10 ohms at 772 kHz
100 ohms + 20% over the frequency band 100 kHz to 1Mhz
Lightning surges defined per FCC Part 68 shall not damage the plug-in.
SF or ESF per ANSI T1.403-1989, and TR-54016-1989;
Ericsson Framing (defined as valid F
T
bits only)
DSX-1 to -27.5 dB
Per TR 62411-1990 (p. 4.7.1)
Per ANSI T1.403-1989
3.0 Volt peak + 10% into 100 ohms at output connector
Tolerant to impedance mismatches
0, 7.5, 15.0 selectable
TR 62411-1990 (p 4.7.2)
DSU: TR 62411-1990 (p 4.7.3)
ADD/DROP: PUB 43802
(When enabled) shall be > 12.5%
Specifications
157
Table 11—Electrical interface specifications - terminal interface
Parameter Specification
Common
Input Only
Output Only
Line rate
Line Code
Line Impedance
Framing Format
Input Level
Input Jitter Tolerance
Input Jitter Transfer
Output Level
Equalization
Internal; 1.544 Mb/s + 32 ppm
When timing is derived from input signal: 1.544 Mb/s + 200 bps
Output line rate follows input line rate.
AMI or B8ZS (selectable)
100 ohms + 10 ohms at 772 kHz
100 ohms + 20% over the frequency band 100 kHz to 1Mhz
SF or ESF per ANSI T1.403-1989, and TR-54016-1989;
Ericsson Framing (defined as valid F
T
bits only)
Idle ESF Data Link is set to 1s.
DSX-1 to -10.0 dB
Per TR 62411-1990 (p. 4.7.1)
Per TR 62411-1990 (p. 4.7.2)
DSX-1 at connector (no equalization enabled)
Up to 655 feet selectable, 5 steps
Table 12—Serial control port specification
Connector
Parameter
Baud Rate
Electrical Interface
DCE
DTE
Specification
2400, 9600, 19200, 38400
EIA-574
DE9S
DE9P
158
Chapter 9: Quick reference
.
Table 13—9-pin DE-9S (DCE) front panel and shelf rear control port pinout
Signal
Rec Sig Det
Received Data
Transmit Data
DTE Ready (DTR)
Signal Ground 5
Data Set Ready (DSR) 6
Request to Send (RTS) 7
Clear to Send (CTS) 8
RI 9
3
4
1
2
DE-9 Pin
Number
DB-25
Equivalent
4
5
7
6
8
3
2
20
22
Direction
OUTPUT
OUTPUT
INPUT
INPUT
—
Not supported
INPUT
OUTPUT
Not used
Table 14—9-pin DE-9P (DTE) shelf rear-panel connector control port pinout
Signal
Rec Sig Det
Received Data
Transmit Data
DTE Ready (DTR)
Signal Ground 5
Data Set Ready (DSR) 6
Request to Send (RTS) 7
Clear to Send (CTS) 8
RI 9
3
4
1
2
DE-9 Pin
Number
DB-25
Equivalent
4
5
7
6
8
3
2
20
22
Direction
INPUT
INPUT
OUTPUT
OUTPUT
—
Not supported
OUTPUT
INPUT
Not used
Specifications
159
160
Chapter 9: Quick reference
Table 15—DB25 connector pin assignments for V.35 and terminal interface
Shelf
Pin
34-Pin
Conn.
ITU
5
6
16
4
1
2
14
3
20
8
7
24
11 (23) W
17 V
9 (19) X
15 Y
B
U
H
F
12 (13) AA
10, 13, 19, 23
D
E
T
C
S
R
A
P
Shelf
Pin
15-Pin
Conn.
T1
22
25
21
18
3
11
1
9
T
R
T1
R1
109
102
(a) 113
(b) 113
(a) 115
(b) 115
(a) 114
(b) 114
(a) 103
(b) 103
(a) 104
(b) 104
105
106
107
108.2
Circuit name
Protective GND
Tx Data A
Tx Data B
Rx Data A
Rx Data B
RTS
CTS
DSR
DTR
Rec Line Sig Det (DCD)
Signal GND
External Clk A
External Clk B
Rx Signal Timing A
Rx Signal Timing B
Tx Signal Timing A
Tx Signal Timing B
Not used by V.35
Circuit name
Terminal Interface transmit side
Terminal Interface transmit side
Terminal Interface receive side
Terminal Interface receive side
Source
DTE
DCE
DCE
DTE
DCE
DTE
DTE
DCE
DCE
DTE
DTE
DCE
DCE
DCE
DCE
Source
Term. I/F
Term. I/F
External
External
This table applies to Kentrox cables 95xx090 and 95xx091. The V.35-specific information
(top section) also applies to adapter 78900 and cable 95xx074.
This table is valid when the data port is configured for V.35, DataSMART 72000 series cable compatibility (the default).
The following table applies to Kentrox cables 95xx088 and 95xx089.
Table 16—DB25 connector pin assignments for EIA-530, terminal interface
Shelf
Pin
ITU/EIA Circuit name
16
4
19
5
1
2
14
3
— Shield
(a) 103/BA BA (A), Transmitted Data
(b) 103/BA BA (B), Transmitted Data
(a) 104/BB BB (A), Received Data A
(b) 104/BB BB (B), Received Data
(a) 105/CA CA (A), Request To Send A (RTS)
(b) 105/CA CA (B), Request To Send
(a) 106/CB CB (A), Clear To Send A (CTS)
7
8
10
17
13
6
22
1
(b) 106/CB
(a) 107/CC
(b) 107/CC
CB (B), Clear To Send
CC (A), DCE Ready (DSR)
CC (B), DCE Ready
9
24
11
15
102/AB AB, Signal Ground
(a) 109/CF CF (A), Received Line Signal Detector
(b) 109/CF CF (B), Received Line Signal Detector
(a) 115/DD DD (A), Receiver Signal Element Timing
(b) 115/DD
(a)113/DA
(b) 113/DA
(a) 114/DB
DD (B), Receiver Signal Element Timing
DA (A), Transmit Signal Element Timing
DA (B), Transmit Signal Element Timing
DB (A), Transmit Signal Element Timing
12
20
(b) 114/DB DB (B), Transmit Signal Element Timing
(a) 108.2/CD CD (A), DTE Ready
23 (b) 108.2/CD CD (B), DTE Ready
18, 21, 25 Not supported for EIA-530
Source
—
DTE
DTE
DCE
DCE
DTE
DTE
DCE
DCE
DCE
DCE
—
DCE
DCE
DCE
DCE
DTE
DTE
DCE
DCE
DTE
DTE
Shelf
Pin
T1/15-Pin
Conn.
Circuit name Source
22
25
21
18
T (Pin 3)
R (Pin 11)
T1 (Pin 1)
R1 (Pin 9)
Terminal Interface transmit side
Terminal Interface transmit side
Terminal Interface receive side
Terminal Interface receive side
Term. I/F
Term. I/F
External
External
1
Cables 950xx088 and 950xx089 connect pin 22 at the shelf end to pin 7 at the DTE end.
Specifications
161
162
Chapter 9: Quick reference
Table 17—DB25S connector to RS449, 37-pin connector adapter cable
RS449
DB37 Pins
30
19
13
31
27
11
29
12
24
7
25
9
—
4
22
6
17
35
10
14
18
5
23
8
26
Circuit name
Protective ground
Tx data A
Tx data B
Rx data A
Rx data B
RTS
RTS
CTS
CTS
DSR
DSR
DTR
DTR
Signal GND
Rec line sig det (DCD)
Rec line sig det (DCD)
Tx signal timing A
Tx signal timing B
Rx signal timing A
Rx signal timing B
External clk A (DTE source)
External clk B (DTE source)
Not Supported
Not Supported
Not Supported
Table 18—Data port interface specification
Parameter Specification
Bit Rates
Connector
Electrical Interfaces
Interface Type
56 kHz to 1536 kHz
25-pin D connector - adaptable to V-35 or EIA-449 (subset) with cable adapters
EIA-530: Per ANSI/EIA-530A-1992
V.35: Compatible
DCE
Table 19—Ethernet 10Base-T pinout
Pin Number
7
8
4
5
3
6
1
2
Signal
TD+
TD-
RD+
RD-
Unused
Unused
Unused
Unused
Table 20—Compatibility
Standard
AT&T TR54016 Issue 2, (TR62411/1990)
AT&T TR54019 Appendix A (Fractional T1)
EIA T1.403/1994
TIA-547
Specifications
163
164
Chapter 9: Quick reference
Table 21—Supported loopbacks
Loopback Definition
LLB
Line loopback
PLB
Payload loopback
DPLB
Data Port loopback
DTLB
Data Terminal loopback
LOC
Local loopback
TILB
Terminal Interface loopback
A minimum penetration loopback at the
NI interface.
An interior loopback, looping the payload back to the NI.
Looping the bit stream assigned to the designated data port back towards the NI.
Looping the bit stream back to the data terminal equipment connected to the data port.
An interior loopback, looping only the payload back to the Terminal Interface or data ports.
A minimum penetration loopback at the
TI interface.
Glossary
2047
A test code pattern used for fractional T1 line testing.
3 in 24
A test code pattern used for testing a full T1 line.
511
A test code pattern used for fractional T1 line testing.
add/drop
A device in which channels from the T1 line at the network interface can be assigned to either a data port or a T1 line at the terminal interface.
AIS
Alarm Indication Signal. A signal condition and alarm indicating that the signal has been lost somewhere upstream. When a device experiences a loss of signal, it transmits an AIS signal to the next device downstream.
TI Loss Of Signal
TI NI
Send AIS
NI
!
TI
Receive NI AIS
alarm
An unsolicited message from a device that typically indicates a problem with a line.
all 0s
A test code pattern used for testing a full T1 line.
all 1s
A test code pattern used for testing a full T1 line.
auto-logout
A feature that automatically logs out a user if there has been inactivity for a specified length of time.
BERT
Bit Error Rate Test. A utility that is used to isolate faulty lines. To troubleshoot a line, the first step is to send a test pattern (often utilizing a loopback to return the code to the device that initiated the test). BERT analyzes the signal to see if the line has caused errors in the pattern. By progressively testing segments of the circuit, the tester can discover which portion of the line is causing the problem.
BES
Bursty Errored Second. Any second that is not a UAS that contains no LOS, AIS, or OOF conditions, and between 2 and 319 (inclusive) error events.
BPV
Bipolar Violation. An error event on a line in which the normal pattern of alternating high and low signals is disrupted. A bipolar violation is when two high signals occur without an intervening low signal, or vice versa.
165
carrier
A company, such as any of the “baby Bell” companies, that provide network communications services, either within a local area or between local areas.
CCS
Common channel signaling.
channel
A single communication path created, in the case of a T1 line, by multiplexing. A T1 line carries 24 channels, each with a bandwidth of 64 Kbps.
cold-start trap
An SNMP trap that is sent when the unit has been power-cycled. See also trap.
command line interface
One method for accessing the management functions of the M-PATH unit, characterized by typing commands at a video display terminal. See also front-panel interface.
control port
A port, either DTE or DCE, on the M-PATH unit to which you can connect a terminal, modem, or SLIP device, and that provides access to the M-PATH management functions. Control ports are also used to daisy-chain M-PATH units.
controlled slip
A situation in which one frame’s worth of data is either lost or replicated. Controlled slips are an indication of network timing problems. A controlled slip typically occurs when an
M-PATH unit is not using the same clock as the unit that generated the received signal.
CPE
Customer Premise Equipment. Equipment on the customer side of the point of demarcation, as opposed to equipment that is on a carrier side. See also point of demarcation.
CRC
Cyclic Redundancy Check.
CSS
Controlled Slip Second. Any second that contains one or more controlled slips (see also the definition for ES). CSSs are accumulated during unavailable seconds (UASs).
CSU
See DSU/CSU.
CTS
Clear To Send. Hardware flow-control on a control port or data port. An M-PATH unit can be set to monitor the data port for assertion of CTS. In this mode, if CTS is not asserted, a data port loss of signal alarm is generated.
daisy-chain
A string of M-PATH units that have been interconnected so that they can all be managed from one terminal.
data link
An IP management path that can be used to manage an M-PATH unit. A data link can be established over a T1 channel (time slot) or the FDL. See also FDL.
data port
A port on a DSU to which some or all of the channels of a DS1 line can be routed.
datagram
A packet of information used in a connectionless network service that is routed to its destination using an address included in the datagram’s header.
166
Glossary
DCE
Data Communications Equipment. A definition in the RS232C standard that describes the functions of the signals and the physical characteristics of an interface for a communication device such as a modem.
DM
Degraded Minute. A non-UAS and non-SES sixty-second period that contains 49 or more
CRC4 errors or 49 or more bipolar violations.
DS1
A standard that specifies an interface operating at 1.544 mbps (million bits per second) and 24 discrete data channels that runs on a T1 line. In common usage, DS1 is synonymous with T1.
DSU/CSU
Data Service Unit/Channel Service Unit. A DSU is a device that makes the link between a T1 line and a line that is carrying packetized data streams such as those produced by a router. A CSU is a device that makes the link between a T1 line and a line that is carrying raw data streams such those produced by a PBX. A DSU/CSU combines the two functionalities.
DTE
Data Terminal Equipment. A definition in the RS-232C standard that describes the functions of the signals and the physical characteristics of an interface for a terminal device such as a terminal.
DTR
Data Terminal Ready. Hardware flow-control on a control port or data port. An M-PATH unit can be set to monitor the data port for assertion of DTR. In this mode, if DTR is not asserted, a data port loss of signal alarm is generated.
ECF
External Clock Input Failure. An alarm generated by an M-PATH unit that is configured for external clocking and has lost the clocking signal.
EER
Excessive Error Rate. An alarm which indicates that a threshold for the number of errored seconds or unavailable seconds has been exceeded.
embedded SNMP agent
An SNMP agent can come in two forms: embedded or proxy. An embedded SNMP agent is one that is integrated into the physical hardware and software of the unit. M-PATH has an internal, integrated SNMP agent. Advantages to this approach are time-accuracy of data and fast response time. See also proxy SNMP agent.
EQF
Internal Equipment Failure. Something has happened to cause the internal hardware of the M-PATH unit to fail. The unit needs to be serviced.
ES
Errored Second. A measurement of the quality of the signal on a T1 line defined as any second that is not an unavailable second and that contains one or more CRC6 errors.
ESF
Extended Super Frame.
167
far-end
In a relationship between two devices in a circuit, the far-end device is the one that is remote.
You are here
TI
Near-end device
Far-end device
FDL
Facility Data Link. A link embedded in the ESF framing bits that is used for such things as accessing performance data on remote units, remote log in, and carrier access to the
M-PATH unit.
fractional T1
A service in which the carrier provides only a subset of the full 24 channels of a T1 line.
Frame Relay
A packet-oriented communication protocol.
frame slip
See controlled slip.
ICMP
Internet Control Message Protocol. ICMP is a protocol in the TCP/IP suite of protocols that is used to determine if a host is alive and responding. An ICMP query is referred to as a Ping. The response is either an “I can hear you” message, or simply no response. M-
PATH will respond to Ping requests, but does not generate them.
IP
Internet Protocol. A suite of protocols for packetizing data for shipment across LANs and
WANs. Protocols exist above the IP protocol for transmitting and receiving IP packets.
M-PATH uses the IP protocol to provide SNMP and Telnet access.
IP address
A unique 32-bit integer used to identify a device in an IP network. You will most commonly see IP addresses written in “dot” notation; for instance, 192.228.32.14. See also
IP netmask.
IP netmask
A pattern of 32 bits that is combined with an IP address to determine which bits of an IP address denote the network number and which denote the host number. Netmasks are useful for subdividing IP networks. IP netmasks are written in “dot” notation; for instance, 255.255.255.0. See also IP address.
link-down trap
An SNMP trap that signifies that the T1 line has transitioned from a normal state to an error state, or that a data port has been disconnected.
link-up trap
An SNMP trap that signifies that the T1 line or a data port has transitioned from an error condition to a normal state.
168
Glossary
LOFC
Loss of Frame Count. An LOFC is the accumulation of the number of times a Loss of
Frame is declared. On detection of an LOS or OOF, a rise-slope type integration process starts that declares a Loss of Frame after 2.5 (±0.5) seconds of continuous LOS or OOF.
If the LOS or OOF is intermittent, the integration process decays at a slope of 1/5 the rise slope during the period when the signal is normal. Thus, if the ratio of an LOS or OOF to a normal signal is greater than 1/5, a Loss of Frame is declared. If during a one-second interval, but no more than 15 contiguous one-second intervals, no LOS or OOF conditions occur, the Loss of Frame condition is cleared.
loopback
A troubleshooting technique that returns a transmitted signal to its source so that the signal can be analyzed for errors. Typically, a loopback is set at various points in a line until the section of the line that is causing the problem is discovered.
LOS
Loss Of Signal. A signal condition and alarm in which the received signal at the network interface or the terminal interface is lost.
TI NI NI
!
TI
NI LOS
TI NI NI
!
TI
TI LOS
MIB
Management Information Base. The information that SNMP can access, structured as a hierarchy. In common usage of the term, MIB is in reference to a sub-branch of the entire
MIB. M-PATH uses MIB II, the DS1 MIB and a product-specific enterprise MIB.
modem
Modulator/demodulator. A device for converting a digital signal to analog (and vice versa) so that it can be transmitted over phone lines.
near-end
In a relationship between two devices in a circuit, the near-end device is the one that is local.
You are here
TI
Near-end device
Far-end device
NI
Network interface. The interface between the M-PATH unit and the T1 line supplied by the carrier.
NMS
Network Management System. A tool for configuring network devices and monitoring network performance, typically an SNMP-based tool.
OID
Object Identifier. The address of a MIB variable.
169
ones (1s) density
A characteristic of a T1 line that refers to the rate at which 1s occur on the line. Because devices such as M-PATH cannot track a bit pattern using 0s, it loses synchronization if the 1s density is not high enough.
OOF
Out of frame. An signal condition and alarm in which some or all of DS1 framing bits are lost.
TI NI NI
!
TI
DS1 framing bits have been lost
NI OOF
PBX
Private Branch Exchange. A private telephone switch-bank. A company will generally have a few numbers that dial into a PBX and from there the switchboard operator can direct the call to a particular extension. Phone calls within the company do not need to go outside of the PBX to be switched. Larger PBXs often have T1 interfaces to connect to one or more CSUs.
ping
A protocol that is part of the TCP/IP suite, used to test the connectivity of the network.
Ping sends a signal to a host or gateway, then listens for an echo response.
point of demarcation
The dividing line between a carrier and the customer premise that is governed by strict standards that define the characteristics of the equipment on each side of the demarcation. Equipment on one side of the point of demarcation is the responsibility of the customer. Equipment on the other side of the point of demarcation is the responsibility of the carrier.
PPP
Point-to-Point Protocol. A protocol that allows the Internet Protocol (IP) to run on lowspeed serial lines. Unlike SLIP, it includes error correction. See also SLIP.
PRM
Performance Report Message. Messages that are received once per second from a far-end device that report information about the condition of the far-end device.
proxy SNMP agent
SNMP agents come in two forms: embedded and proxy. A proxy agent is physically outside of the device being managed. The proxy is a translator between the device’s native command language and SNMP. Advantages of proxy agents are management of legacy equipment which cannot support embedded SNMP agents, and management of large numbers of devices where network connections may be limited. See also embedded
SNMP agent.
QRS
Quasi-Random Signal. A test code pattern used for testing a full T1 line.
real-time clock
A clock that maintains the time of day in distinction to a clock that is used to time the electrical pulses on a circuit.
router
A device that connects various links in a network matrix, directing packets along the most economical or efficient routes to the packet’s destination; a packet switch.
170
Glossary
RxD
Received Data. The control ports and data ports on M-PATH units have an RxD line.
This line is defined from the DTE perspective, so RxD for a DCE port is actually TxD.
Each data port has a pair of RxD and TxD LEDs on the front panel. See also TxD.
SES
Severely Errored Second. Any second that is not a UAS that contains an LOS condition, an AIS condition, an OOF condition, or 320 or more error events.
SF
Super Frame.
signal condition
Characteristics of the electronic pulses on a line, categorized into groups of various error types. When errored signal conditions persist they cause M-PATH to raise an alarm.
SLIP
Serial Line Internet Protocol. A protocol that allows the Internet Protocol (IP) to run on low-speed serial lines.
SMDS
Switched Multi-Megabit Digital Service. A public, high-speed, connectionless, packetswitched data transfer service that provides LAN-like performance and features over an entire metropolitan area.
SNMP
Simple Network Management Protocol. The accepted industry-standard network management protocol that uses a system of agents and managers. Each agent is responsible for interacting with a certain MIB. The manager can ask the agent for data, or it can ask the agent to set the value of some data.
super-user
A login ID that allows unlimited access to the full range of a device’s functionality, especially including the ability to reconfigure the device and set passwords.
T1
A specification for a transmission line. The specification details the input and output characteristics and the bandwidth. T1 lines run at 1.544 Mbps and provide for 24 data channels. In common usage, the term “T1” is used interchangeable with “DS1.”
TCP
Transport Control Protocol. TCP is one of the two transport protocols in the TCP/IP protocol suite. TCP is a complex, connection-based protocol that guarantees reliable delivery of packets. Telnet uses TCP.
TCP/IP
A suite of protocols that includes IP, UDP, TCP, SNMP, TELNET, ICMP, and PING.
TCP/IP is the networking protocol of choice of the Internet and many private networks as well. Kentrox SNMP and Telnet products operate in TCP/IP networks.
Telnet
Telnet is a TCP/IP protocol that defines a client/server mechanism for emulating directlyconnected terminal connections. M-PATH implements a Telnet Server, allowing other devices to establish connections with it. M-PATH does not implement a Telnet Client
(which would allow M-PATH to connect to other devices).
terminal server
In the simplest terms, a terminal server is an IP network port and a collection of serial ports. Most terminal servers allow the serial ports to be configured for SLIP. If an
M-PATH unit is using SLIP for its IP network connection, a terminal server could be used to make the connection from serial to Ethernet.
171
TI
Terminal Interface. The interface between the M-PATH unit and the T1 line on the customer premise.
trap
A trap is an unsolicited alert generated by SNMP. There are five standard trap types: link up, link down, warm start, cold start, and enterprise-specific.
TxD
Transmit Data. The control ports and data ports on M-PATH have a TxD line. This line is defined from the DTE perspective, so TxD for a DCE port is actually RxD. Each data port has a pair of RxD and TxD LEDs on the front panel. See also RxD.
UAS
Unavailable Second. A measurement of the signal quality of a T1 line. Unavailable seconds start accruing when ten consecutive severely errored seconds occur.
UDP
User Datagram Protocol. One of the two transport protocols in the TCP/IP protocol suite.
UDP is a send and forget protocol, which means there is no guarantee that the datagram will reach its destination.
V.35
An interface specification for serial communications that can handle data at higher speed than the RS232 interface.
VDT
Video Display Terminal.
warm-start trap
One of the five SNMP trap types. For Kentrox equipment, warm start traps indicate that
SNMP alarm messages or agents have been enabled.
Xon/Xoff
This is software flow control for the control ports. When an M-PATH unit has too much data coming in, it will transmit an Xoff (stop transmitting) character. If the device on the other end understands flow control, it will stop transmitting until it receives an Xon
(resume transmitting) character. If the M-PATH unit receives an Xoff, it stops transmitting data until it receives an Xon. Xon/Xoff flow control is not available when SLIP is enabled.
yellow alarm
An alarm that occurs on a device when the signal from the device is not received at the far-end.
NI Loss Of Signal
TI NI
Send Yellow
NI
!
TI
NI Yellow Alarm
172
Glossary
Index
Symbols
%AS percentage of available seconds,
%BES percentage of bursty errored seconds, 89
%CSS percentage of controlled slip seconds, 89
%DM percentage of degraded minutes,
%EFS percentage of error-free seconds, 89
%ES percentage of errored seconds, 89
%SES percentage of severely errored seconds, 89
Numerics
A
Advanced Management Configuration
alarm conditions and traps, 144
Alarm Configuration menu, 39, 147
Alarm History report, 79, 92, 154 alarm history report command, 154
alarm list
alarm messages
alarms
enabling/disabling on incoming yellow, 41
ARC command, 19, 110, 117, 151
B
BERT test codes
BERT test codes using, 119, 122
BES bursty errored seconds, 82, 85
bipolar violations at a port, 109
C
channel assignment configuration tables, 63
clearing stored information, 35, 36
CLK command, 33 clock source, 33
command line interface
commands
Index
173
174
Index
compatible NI channel assignments,
configuration privilege level, 22
configuration tables
configuring for SNMP traps, 140
configuring IP addresses, 132 configuring IP netmasks, 132
configuring network interface, 46
configuring terminal interface, 52
control port
Control Port Configuration menu, 147
conventions used in the manual, 6
copying NI configuration tables, 76
CSS controlled slip seconds, 82, 85
D
data link for IP management, 63
data port
loss of signal (DPLOS) processing,
Data Port Configuration menu, 57, 148
data port/terminal loopback, 116
downloading system software, 35
DP LOS alarm at a data port, 107
E
equalization TI specifying, 55
Ericsson-modified super frame, 48, 54
error counts
error threshold evaluation window, 43
errored seconds (ES)
extended super frame (ESF), 48, 54
K
keep alive signal for the NI, 49
F
Fractional T1 Configuration menu,
front panel
H
I
IDL command, 61 idle character, 61
incompatible NI channel assignments,
IP address default router, 134
IP address screening list, 135 adding to, 135
IP management
L
logging in, 18 through control port, 18
through Telnet, 19 through the facility data link, 19
login remote command, 110, 151
loopback
setting and resetting locally, 117
loopback commands
set data port loopback on data port,
set remote line loopback, 118 set remote loopback on data port,
118 set remote payload loopback, 118
setting and resetting remotely, 118
loss of signal (LOS) processing, 62
Index
175
M
maintenance privilege level, 22
Management Configuration menu,
MCV view management configuration command, 126
N
network input status codes, 102
network interface
network interface alarms
network interface channel assignments
Network Interface Configuration menu, 149
network interface set command, 130,
network output status codes, 103
P
page break, 79 page length, 79
Password Entry and Configuration
passwords
performance data
performance report commands, 84
performance report messages (PRMs),
pinouts
DB25S connector to RS449 adapter,
Ethernet 10BaseT connector, 163
planning the channel assignment, 63
product version information, 36
R
receive clock inversion
report
clearing stored information, 35
reset test code generation command,
rules for assigning channels, 71
S
securing the command-line interface,
Security History report, 79, 93
self-test diagnostics
running, 110 self-test error messages, 110
176
Index
SES severely errored seconds, 82, 85
SNMP
SNMP agent
SNMP trap hosts
SNMP traps
requirements for using, 140 types, 140
Source Screening Address list, 93
specifications
electrical interface, 157, 158 environmental, 157
status codes loopback, 102 status codes network input, 102
status codes network output, 103
status codes terminal input, 104
system clock
System Configuration menu, 26, 150 system parameters, 26–36
system software
system status
System Status and Remote menu, 146
T
TE0,1,2,3,4 signal equalization command, 55
terminal input status codes, 104
terminal interface
terminal interface alarms
Terminal Interface Configuration menu, 150
terminal interface loopback, 115
test code
all 0s, 119, 122 all 1s, 119, 122
QRS, 119, 122 test code reset command, 122
test codes
TI channel type (voice/data), 71
TI Configuration menu display command, 52
transmit clock inversion
traps and alarm conditions, 144
Trivial File Transfer Protocol (TFTP),
troubleshooting
TI YEL alarm, 107
typical NI channel assignments, 65
Index
177
U
UAS unavailable seconds, 82, 85
unavailable seconds (UAS)
V
View Alarm Configuration screen, 40
View Control Port Configuration screen, 38
View Data Port Configuration screen,
View Network Configuration screen,
View System Configuration screen, 26
View TI Configuration screen, 53
viewing current settings
W
Y
yellow alarm output
Z
ZALL command, 34, 79 zeroing counters, 34
178
Index
advertisement
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Related manuals
advertisement