Synchrony IAN-150/IPP Maintenance and Troubleshooting Manual

Transcription

Synchrony IAN-150/IPP
Maintenance and
Troubleshooting Manual
MC15860
June 1997
TimePlex Group
Worldwide Headquarters
400 Chestnut Ridge Road
Woodcliff Lake, NJ 07675
USA
(888) 777-0929 • (201) 391-1111
Americas Division
400 Chestnut Ridge Road
Woodcliff Lake, NJ 07675
USA
(888) 777-0929 • (201) 391-1111
CANADA
30 Fulton Way
Richmond Hill, ON
Canada L4B-1E6
(905) 886-6100
Americas Customer Support
16255 Bay Vista Drive
Clearwater, FL 34620
USA
(727) 530-9475
Timeplex Federal Systems, Inc.
Far East Division
12150 Monument Drive
Suite 750
Fairfax, VA 22033
USA
(703) 385-3366
30th Floor, Windsor House
311 Gloucester Road
Causeway Bay
Hong Kong
(852) 2830 9889
Europe/Middle East/Africa
Division
Australia/New Zealand
Division
Langley Business Centre
Station Road, Langley
Slough, Berkshire, SL3 8DT
United Kingdom
(44) 0 1753 601000
Level 21
1 York Street
Sydney, NSW 2000
Australia
(612) 9 247 1422
EUROPE/AFRICA DISTRIBUTORS
10 Rue de Genéve, Bte 17
B-1140 Brussels
Belgium
(32) 2 745.02.30
FRANCE
39 Avenue des Trois Peuples
F-78180 Montigny-le-Bretonneux
France
(33.1) 30.64.81.00
GERMANY
Edisonstrasse 11-13
D-60388 Frankfurt
Germany
(49) 610-973-8505
4/98
NO WARRANTIES ARE EXTENDED BY THIS DOCUMENT. The technical information in this document
is proprietary to Timeplex, Inc. and the recipient has a personal, non-exclusive and non-transferable
license to use this information solely with the use of Timeplex products. The only product warranties
made by Timeplex, Inc., if any, are set forth in the agreed terms and conditions for purchase of a
Timeplex product. Timeplex, Inc. disclaims liability for any and all damages that may result from
publication or use of this document and/or its contents except for infringement of third party copyright or
misappropriation of third party trade secrets. No part of this document may be reproduced in any manner
without the prior written consent of Timeplex, Inc.
U.S. GOVERNMENT RESTRICTED AND LIMITED RIGHTS
All software and related software documentation supplied by Timeplex, Inc. to the United States
Government are provided with Restricted Rights. Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013 or subparagraph (c)(2) of the Commercial Computer Software–
Restricted Rights at CFR 52.227-19, as applicable.
All documentation, other than software documentation which are provided with Restricted Rights, are
provided with Limited Rights. U.S. Government rights to use, duplicate, or disclose documentation, other
than software documentation, are governed by the restrictions defined in paragraph (a)(15) of the Rights
in Technical Data and Computer Software clause at DFARS 252.227-7013.
“DFARS” is the Department of Defense Supplement to the Federal Acquisition Regulation.
Contractor/manufacturer is Timeplex, Inc., 400 Chestnut Ridge Road, Woodcliff Lake, NJ 07675.
The information in this document is subject to change without notice. Revisions may be issued at such
time.
Timeplex, Express Switching, LINK/2+, TIMEPAC and Synchrony are registered trademarks of Timeplex,
Inc.
Ethernet is a registered trademark of Xerox Corporation.
IBM is a registered trademark of International Business Machines Corporation.
MS-DOS is a registered trademark of Microsoft Corporation.
Netscape, Netscape Navigator, and the Netscape N logo are registered trademarks of
NetscapeCommunications Corporation in the United States and other countries. Netscape’s logos
and Netscape product and service namaes are also trademarks of Netscape Communications
Corporation, which may be registred in other countries.
Novell and NetWare are registered trademarks, and Internetwork Packet Exchange is a
trademark of Novell, Incorporated.
Sun is a registered trademark of Sun Microsystems, Inc.
UNIX is a registered trademark in the United States and other countries, licensed exclusively
through X/Open Company Limited.
NOTICE
Telecommunications products must be installed and operated in compliance with the relevant
National Regulatory requirements summarized in the REGULATORY section of the Synchrony
IAN-150/IPP Maintenance and Troubleshooting Manual.
READ IN FULL, PRIOR TO
INSTALLATION, any product-specific National Regulatory requirements applicable to the country
of installation.
©1997, 1998 Timeplex, Inc.
ii
IAN150/IPP MT
6/30/97
DISCLAIMER
Ascom Timeplex is now Timeplex, Inc. The new company logo is
. Please disregard any references to the company’s former
name in this manual.
Thank you.
1998 Timeplex, Inc.
01/01/98
IAN150/IPP MT
6/30/97
WARNING
NO OPERATOR SERVICEABLE PARTS ARE
INSIDE THIS EQUIPMENT. SERVICE MUST BE
PERFORMED BY QUALIFIED SERVICE
PERSONNEL.
VORSICHT
NICHT VOM BENUTZER REPARIERBARE TEILE IM
GEHÄUSE. BITTE WENDEN SIE SICH AN
QUALIFIZIERTES WARTUNGSPERSONAL.
ATTENTION
CET APPAREIL NE CONTIENT AUCUN ELÉMENT
QUE L'UTILISATEUR PUISSE RÉPARER. CONFIER
LA MAINTENANCE À UN PERSONNEL
TECHNIQUE QUALIFIÉ.
WARNING:
DISCONNECT ALL POWER SUPPLY CORDS
BEFORE SERVICING TO AVOID ELECTRICAL
SHOCK.
VORSICHT:
ZUR WARTUNG ALLE NETZKABEL TRENNEN UM
ELEKTRISCHEN SCHLAG ZU VERHINDERN.
ATTENTION:
DÉBRANCER TOUS LES CORDONS
D'ALIMENTATION AVANT LA MAINTENANCE.
iii
WARNING
Any site construction, whether new construction or renovation work, that
allows traceable amounts of dust (from gypsum products, sheetrock, cement,
etc.) or airborne corrosives (chlorine-based solvents used in preparation of
ceilings, walls, and floors, such as muriatic acid) to enter or contact any
Ascom Timeplex equipment can lead to catastrophic damage to electronic
components and circuitry.
Unless appropriate steps are taken to secure the construction area to prevent
these materials from coming in contact with the equipment, short-term failure
can occur and/or long-term reliability can be adversely affected.
References that can be used to define normal and acceptable environmental
conditions:
• Bellcore Technical Reference TR-NWT-000063
• International Electromechanical Commission (IEC) Standard Publication 721
Any customer installing Ascom Timeplex equipment in unfinished premises
or contemplating construction or renovation (or storage of corrosives) at or
near an Ascom Timeplex equipment installation should be aware of the
potential damage and impact to warranties that can be caused if such
equipment is not properly protected. Airflow generated by the cooling fans in
the equipment will tend to combine contaminants present in the air and
deposit a coating over the printed circuit boards inside the chassis.
Steps that should be taken to protect Ascom Timeplex equipment, if exposure
to airborne contamination is likely, include, but are not limited to:
1. Equipment cabinets should be covered with plastic sheeting from floor to
ceiling (or sufficient to isolate it from the source of contamination), allowing
sufficient surrounding airspace for proper equipment cooling.
2. Fresh external (clean) air should be piped in to the enclosed area via a
temporary duct.
3. Positive internal air pressure should be maintained inside the enclosure.
4. Corrosive-type materials used for etching should NOT BE USED OR
STORED IN THE VICINITY OF THE ASCOM TIMEPLEX EQUIPMENT. This type
of activity should be completed in advance of installation or equipment
already in place must be de-installed and removed from the area until the
process is completed.
iv
IAN150/IPP MT
6/30/97
Products Covered by This Manual
This manual applies to the Ascom Timeplex Synchrony IAN-150 and the ST-1000/ER-5
Independent Packet Processor (IPP), using software Release 1.1 or higher. The ER-15 has been
replaced by the ST-1000.
How to Use This Manual
This manual provides the information required to install, maintain, and troubleshoot the IAN-150
network node. Unless otherwise indicated, the information in this manual applies to the
Synchrony ST-1000/ER-5 IPP module as well as to the Synchrony IAN-150. All references to the
IAN-150 apply to the IPP unless otherwise noted.
•
Install the IAN-150 in your network using the information provided in Chapters 1 and 2.
•
Configure the IAN-150 using the information provided in Chapter 3 and 4 of this manual,
with supplemental help from the Synchrony IAN-150/IPP Planning Manual and the
Synchrony IAN-150/IPP Reference Manual.
•
Refer to Chapter 4 for Network Management configuration information.
•
Refer to Chapter 5 for Utilities and Diagnostics information.
•
Use the information provided in Chapter 6 to isolate faults and perform corrective
maintenance.
•
For day-to-day operation of the IAN-150, refer to the monitoring information in Chapters 7
through 19.
Organization of This Manual
This manual provides IAN-150 installation, maintenance, and troubleshooting information. The
information is organized as outlined below.
Introduction (Chapters 1 and 2)
•
Chapter 1, Product Description, describes the key features and functional specifications of
the IAN-150.
•
Chapter 2, Getting Started, provides step-by-step instructions to install the IAN-150 and to
operate the user interface.
System Configuration (Chapters 3 and 4)
•
Chapter 3, Basic Configuration and Monitoring, discusses the default configuration of the
IAN-150. Basic configuration and monitoring information is also provided.
•
Chapter 4, Network Management, discusses the Simple Network Management Protocol
(SNMP) supported by the IAN-150 as the preferred method for network management
communications.
IAN150/IPP MT
6/30/97
v
Diagnostics and Troubleshooting (Chapters 5 and 6)
•
Chapter 5, Utilities and Diagnostics, provides information about the internal utilities and
diagnostics that are available with the IAN-150. The chapter describes the Ping utility, the
Table Flush utility, the SNMP trap display, the Pseudoport utility, and the Download/Upload
utility.
•
Chapter 6, Troubleshooting, provides troubleshooting techniques designed to help
determine the cause of a malfunction.
Monitoring (Chapters 7 through 19)
vi
•
Chapter 7, Ethernet Monitoring, describes the capability of the IAN-150 to provide
information to monitor and troubleshoot Ethernet operations.
•
Chapter 8, Token Ring Monitoring, describes the capability of the IAN-150 to provide
information to monitor and troubleshoot Token Ring operations.
•
Chapter 9, Bridge Monitoring, describes the capability of the IAN-150 to provide
information to monitor bridging operations (which include Bridge Relay Element (BRE)
Virtual and Physical Port Bridging, General (Transparent) Bridging, Spanning Tree
Bridging, and Source Route Bridging).
•
Chapter 10, DLSw Monitoring, describes the capability of the IAN-150 to provide routing
information to monitor and troubleshoot Data Link Switching operations.
•
Chapter 11, TCP/IP Monitoring, describes the capability of the IAN-150 to provide
routing information to monitor TCP/IP operations.
•
Chapter 12, IPX Monitoring, describes the capability of the IAN-150 to provide routing
information to monitor IPX operations.
•
Chapter 13, Bisync Monitoring, describes the capability of the IAN-150 to provide
information to monitor Bisync operations. The IAN-150 provides displays to monitor the
status of Binary Synchronous Communication (BSC) ports and circuits, the flow state and
transmission of BSC packets, and the status of BSC calls.
•
Chapter 14, BPS Monitoring, describes the capability of the IAN-150 to provide
information to monitor Burroughs Poll Select (BPS) operations. The IAN-150 provides
displays to monitor the status of BPS ports and circuits, the flow state and transmission of
BPS packets, and the status of BPS calls.
•
Chapter 15, SDLC Monitoring, describes the capability of the IAN-150 to provide
information to monitor Synchronous Data Link Control (SDLC) operations. The IAN-150
provides displays to monitor the status of SDLC ports and circuits, the flow state and
transmission of SDLC packets, and the status of SDLC calls.
•
Chapter 16, X.25 Monitoring, describes the capability of the IAN-150 to provide
information to monitor X.25 operations. The IAN-150 provides displays to monitor the status
of X.25 ports and circuits, the flow state and transmission of X.25 packets, and the status of
X.25 calls.
•
Chapter 17, Frame Relay Monitoring, describes the capability of the IAN-150 to provide
information to monitor frame relay operations.
IAN150/IPP MT
6/30/97
•
Chapter 18, ISDN Monitoring, describes the capability of the IAN-150 to provide
information to monitor ISDN Basic Rate Interface (BRI) operations.
•
Chapter 19, Backup Monitoring, describes the capability of the IAN-150 to provide
information to monitor the performance and status of a backup port.
Appendixes
•
Appendix A, Replacement and Upgrade Procedures, provides procedures to remove and
install IAN-150 expansion modules and WAN Personality Modules (WPMs). The appendix
also includes procedures to upgrade buffer memory and system memory in the IAN-150.
•
Appendix B, Cables, provides a list of cables used with the IAN-150. Cable wiring
diagrams are also included.
•
Appendix C, Trap Messages, provides a list of trap messages that can be displayed on a
terminal or PC attached to the IAN-150.
•
Appendix D, User Interface Screen Index, provides a list of IAN-150 user interface
screens.
Service
For service in the U.S. and Canada, contact Customer Support at 1-800-237-6670.
For service outside the U.S. and Canada, contact your local sales representative.
Information required for service is:
Model No._______________________
(For Model No. information, refer to Table 1-1 and
to Table 1-2 in Chapter 1, Product Description.)
Serial No._______________________
Warnings, Cautions, and Notes
Be sure that you understand all directions, warnings, and limitations before using this product.
In this manual:
•
WARNINGS present information or describe conditions which, if not observed, could result
in personal injury.
•
CAUTIONS reflect conditions which could cause product damage or data loss.
•
NOTES describe limitations on the use of the equipment or procedure.
IAN150/IPP MT
6/30/97
vii
If Product Is Received Damaged
Forward an immediate request to the delivering carrier to perform an inspection and prepare a
damage report. SAVE container and packing material until contents are verified.
Concurrently, report the nature and extent of damage to Customer Support so that action can be
initiated to repair or replace damaged items, or instructions issued for returning items.
The responsibility of the manufacturer ends with delivery to the first carrier. ALL CLAIMS for
loss, damage, or nondelivery must be made against the delivering CARRIER WITHIN 10 DAYS
OF RECEIPT of shipment.
To Return Product
Please obtain instructions from Customer Support before returning any item(s). Report the fault
or deficiency along with the model, type, and serial number of the item(s) to Customer Support.
Upon receipt of this information, Customer Support will provide service instructions or a Return
Authorization Number and other shipping information. All items returned under this warranty
must be sent to the manufacturer with charges prepaid.
viii
IAN150/IPP MT
6/30/97
Contents
Chapter 1. Product Description
Hardware Configuration Options ........................................................................................... 1-2
Expansion Module Slot .................................................................................................... 1-3
Sample Hardware Configurations ..................................................................................... 1-4
Physical Ports................................................................................................................... 1-6
LED Indicators................................................................................................................. 1-7
AC Power Connections .................................................................................................... 1-7
WAN Personality Modules (WPMs)................................................................................. 1-8
System Software Features................................................................................................. 1-9
Hardware Specifications........................................................................................................ 1-9
Physical Specifications..................................................................................................... 1-9
System Architecture Block Diagram............................................................................... 1-10
System Processor and System Memory .......................................................................... 1-11
Access Switching and Routing Specifications................................................................. 1-12
Environmental Requirements.......................................................................................... 1-13
Electrical Specifications ................................................................................................. 1-13
Chapter 2. Getting Started
Installation Procedures .......................................................................................................... 2-2
Mounting the IAN-150 .......................................................................................................... 2-3
Powering Up the IAN-150................................................................................................... 2-11
System Software Description............................................................................................... 2-16
Boot PROM ................................................................................................................... 2-16
User Interface Description ................................................................................................... 2-17
User Access Levels ........................................................................................................ 2-19
User Interface Menu Structure ........................................................................................ 2-20
User Interface Main Menu Options................................................................................. 2-22
Entering Data ................................................................................................................. 2-27
User Interface Commands .............................................................................................. 2-28
Chapter 3. Basic Configuration and Monitoring
Unit Default Configuration.................................................................................................... 3-1
Physical Setup.................................................................................................................. 3-2
Port Configuration............................................................................................................ 3-2
Configuration Basics ............................................................................................................. 3-6
Configuring Node Parameters........................................................................................... 3-6
Configuring Port Parameters .......................................................................................... 3-10
Configuring Fast Path Parameters................................................................................... 3-11
X.28 Basics ......................................................................................................................... 3-12
Assigning an IP Address ................................................................................................ 3-13
IP and TCP Minimum Configuration................................................................................... 3-15
Monitoring Basics ............................................................................................................... 3-15
IAN150/IPP MT
6/30/97
ix
Node Monitoring............................................................................................................ 3-15
Port Monitoring.............................................................................................................. 3-18
Hardware Monitoring ..................................................................................................... 3-19
SNMP Trap Monitoring ................................................................................................. 3-24
Chapter 4. Network Management
IP Command ......................................................................................................................... 4-2
Simple Network Management Protocol (SNMP) ................................................................... 4-2
SNMP Configuration............................................................................................................. 4-3
SNMP Configuration Tips................................................................................................ 4-3
System Group Configuration ............................................................................................ 4-4
Community Names Configuration .................................................................................... 4-6
Trap Output Configuration ............................................................................................... 4-7
Element Management System Configuration .................................................................... 4-8
Trap Filtering ................................................................................................................... 4-9
SNMP Monitoring.......................................................................................................... 4-10
Chapter 5. Utilities and Diagnostics
Ping Utility ........................................................................................................................... 5-2
ICMP Ping ....................................................................................................................... 5-2
IPX Ping ....................................................................................................................... ... 5-4
Table Flush Utility ................................................................................................................ 5-5
IP Table Flush.................................................................................................................. 5-5
IPX Table Flush ............................................................................................................... 5-6
SNMP Trap Display .............................................................................................................. 5-6
Pseudoport Utility ................................................................................................................. 5-7
Pseudoport User Interface................................................................................................. 5-8
Traffic Generator Function ............................................................................................... 5-8
Echo Function .................................................................................................................. 5-9
Sink Function................................................................................................................... 5-9
Pseudoport Configuration.................................................................................................... 5-10
Pseudoport Operation ..................................................................................................... 5-13
Loader Utility...................................................................................................................... 5-15
TELNET Utility .................................................................................................................. 5-19
Diagnostics ......................................................................................................................... 5-21
Power-Up Self-Tests ...................................................................................................... 5-21
Node Monitoring............................................................................................................ 5-21
Port Diagnostics ............................................................................................................. 5-24
Chapter 6. Troubleshooting
Initial Problem Analysis ........................................................................................................ 6-1
SNMP Alarm Log ............................................................................................................ 6-2
Crash Dump Procedure..................................................................................................... 6-3
Port Diagnostics ............................................................................................................... 6-3
Line Trace Procedure........................................................................................................ 6-4
Preventive Maintenance......................................................................................................... 6-5
Factory Diagnostics............................................................................................................... 6-6
x
IAN150/IPP MT
6/30/97
Chapter 7. Ethernet Monitoring
Ethernet Monitoring Tips ...................................................................................................... 7-1
Ethernet Port Status............................................................................................................... 7-2
Chapter 8. Token Ring Monitoring
Token Ring Monitoring Tips ................................................................................................. 8-1
Token Ring Port Status ......................................................................................................... 8-2
Chapter 9. Bridge Monitoring
Bridge Monitoring Tips......................................................................................................... 9-1
Bridging Status Menu............................................................................................................ 9-2
General Bridging Status ........................................................................................................ 9-3
Spanning Tree (STA/P) Status Menu..................................................................................... 9-5
Spanning Tree Protocol Status............................................................................................... 9-6
Spanning Tree Port Status ..................................................................................................... 9-8
Source Route Bridging Status.............................................................................................. 9-10
Bridge Relay Element (BRE) Statistics................................................................................ 9-12
BRE Port Statistics......................................................................................................... 9-13
BRE Physical Port Statistics........................................................................................... 9-17
BRE Forwarding Table................................................................................................... 9-18
BRE Routing Table ........................................................................................................ 9-20
BRE Adjacency Table .................................................................................................... 9-22
Bridging Tables Menu......................................................................................................... 9-24
Bridge Forwarding Table..................................................................................................... 9-25
Source Route Encapsulation Table ...................................................................................... 9-26
SR-TB Translation Table..................................................................................................... 9-28
Chapter 10. DLSw Monitoring
DLSw Status and Control Menu .......................................................................................... 10-1
DLSw Monitoring Tips ....................................................................................................... 10-2
DLSw Port Statistics ........................................................................................................... 10-2
DLSw Connection Summary ............................................................................................... 10-5
DLSw NetBios Name Caching Table .................................................................................. 10-7
LLC Status.......................................................................................................................... 10-8
Chapter 11. TCP/IP Monitoring
TCP/IP Monitoring Tips...................................................................................................... 11-1
IP Control and Status .......................................................................................................... 11-2
IP Status...................................................................................................................... ........ 11-3
IP Status Screen .................................................................................................................. 11-4
IP Common Routing Table.................................................................................................. 11-6
Address Resolution Protocol (ARP) Table........................................................................... 11-8
IP Address Table ................................................................................................................. 11-9
ICMP Status...................................................................................................................... 11-10
UDP Status ....................................................................................................................... 11-12
UDP Statistics ................................................................................................................... 11-12
IAN150/IPP MT
6/30/97
xi
UDP Listen Table.............................................................................................................. 11-13
HTTP Status...................................................................................................................... 11-14
HTTP Protocol Statistics ................................................................................................... 11-15
HTTP Connections............................................................................................................ 11-16
HTTP Users ...................................................................................................................... 11-17
TCP Status and Control Menu........................................................................................... 11-18
TCP Standard Statistics ..................................................................................................... 11-19
TCP Connection Table ...................................................................................................... 11-21
TCP Connection Statistics................................................................................................. 11-23
TCP Receive Statistics ...................................................................................................... 11-25
TCP Transmit Statistics..................................................................................................... 11-27
RIP Status ......................................................................................................................... 11-29
OSPF Status.................................................................................................................... .. 11-30
OSPF Protocol Status........................................................................................................ 11-31
OSPF Interface Data Table ................................................................................................ 11-35
OSPF Link State Database Status ...................................................................................... 11-37
OSPF Link State Database Table - STUB Type................................................................. 11-38
OSPF Link State Database Table - RTR Type ................................................................... 11-39
OSPF Link State Database Table - NET Type ................................................................... 11-40
OSPF Link State Database Table - NET SUM Type .......................................................... 11-41
OSPF Link State Database Table - AS SUM Type ............................................................ 11-43
OSPF Link State Database Table - EXT Type ................................................................... 11-44
OSPF Neighbor Data Table ............................................................................................... 11-45
OSPF Virtual Link Data Table .......................................................................................... 11-47
OSPF Virtual Neighbor Data Table ................................................................................... 11-49
EGP Status........................................................................................................................ 11-51
EGP Statistics ................................................................................................................... 11-52
EGP Neighbor Table ......................................................................................................... 11-53
BOOTP Protocol ............................................................................................................... 11-55
Chapter 12. IPX Monitoring
IPX Monitoring Tips ........................................................................................................... 12-1
IPX Status ........................................................................................................................... 12-2
IPX Protocol Status ............................................................................................................. 12-3
IPX Service Advertising Protocol Status ............................................................................. 12-6
IPX Routing Table .............................................................................................................. 12-8
IPX Service Advertising Protocol Table .............................................................................. 12-9
Chapter 13. Bisync Monitoring
Bisync Monitoring Tips....................................................................................................... 13-1
Bisync Port Status and Control............................................................................................ 13-2
Bisync Status ...................................................................................................................... 13-3
Bisync Circuit Status........................................................................................................... 13-5
Bisync Cleared Circuit Status .............................................................................................. 13-9
xii
IAN150/IPP MT
6/30/97
Chapter 14. BPS Monitoring
BPS Monitoring Tips .......................................................................................................... 14-1
BPS Port Status and Control................................................................................................ 14-2
BPS Status .......................................................................................................................... 14-3
BPS Circuit Status............................................................................................................... 14-5
BPS Cleared Circuit Status.................................................................................................. 14-9
Chapter 15. SDLC Packet Switch Monitoring
SDLC Monitoring Tips ....................................................................................................... 15-1
SDLC Port Status and Control............................................................................................. 15-2
SDLC Station Status ........................................................................................................... 15-3
SDLC Circuit Status............................................................................................................ 15-7
SDLC Cleared Circuit Status............................................................................................. 15-11
Chapter 16. X.25 Monitoring
X.25 Monitoring Tips.......................................................................................................... 16-1
X.25 Port Status and Control............................................................................................... 16-2
X.25 Status.......................................................................................................................... 16-4
X.25 Circuit Status.............................................................................................................. 16-7
X.25 Cleared Circuit Status ............................................................................................... 16-11
Chapter 17. Frame Relay Monitoring
Frame Relay Monitoring Tips.............................................................................................. 17-1
Frame Relay Port Status ...................................................................................................... 17-2
Frame Relay Virtual Trunk Status ....................................................................................... 17-4
Frame Relay PVC Status ..................................................................................................... 17-7
Frame Relay Route Topology Status ................................................................................. 17-10
Chapter 18. ISDN Monitoring
ISDN Monitoring Tips ........................................................................................................ 18-1
ISDN Status ........................................................................................................................ 18-2
ISDN D-Channel Status ...................................................................................................... 18-3
ISDN B-Channel Status....................................................................................................... 18-7
ISDN Destination Status.................................................................................................... 18-10
ISDN Call History................................................................................................ ............. 18-16
Chapter 19. Backup Monitoring
Backup Monitoring Tips...................................................................................................... 19-1
Backup Statistics ................................................................................................................. 19-2
IAN150/IPP MT
6/30/97
xiii
Appendixes
Appendix A. Replacement and Upgrade Procedures
Appendix B. Cables
Appendix C. Trap Messages
Appendix D. User Interface Screen Index
Index
Regulatory Requirements
xiv
IAN150/IPP MT
6/30/97
Figures
1-1
1-2
1-2
1-3
1-4
1-5
1-6
Typical IAN-150 Networking Application .................................................... 1-1
Sample IAN-150 Hardware Configurations (Sheet 1 of 2)............................. 1-4
Sample IAN-150 Hardware Configurations (Sheet 2 of 2)............................. 1-5
IAN-150 AC Power Connections .................................................................. 1-8
IAN-150 System Architecture Block Diagram..............................................1-10
IAN-150 Motherboard.................................................................................1-11
IAN-150 Power Cord Set for the United States and Canada .........................1-14
2-1
2-5
2-6
2-7
2-8
2-9
2-10
2-11
2-12
2-13
IAN-150 Rack Mounting Brackets for Models IAN-150-001, IAN-150-002,
IAN-150-003, IAN-150-004, IAN-150-005, and IAN-150-006 ................ 2-5
IAN-150-013, IAN-150-014, IAN-150-015, and IAN-150-016
(Sheet 1 of 2) .......................................................................................... 2-6
IAN-150-013, IAN-150-014, IAN-150-015, and IAN-150-016
(Sheet 2 of 2) .......................................................................................... 2-7
IAN-150 Rack-Mounted Chassis .................................................................. 2-8
Removing IAN-150 Tray from Rack-Mounted Cover (Models IAN-150-011,
IAN-150-012, IAN-150-013, IAN-150-014, IAN-150-015, and
IAN-150-016) ........................................................................................2-10
IAN-150 IEEE 802.3/Ethernet II Connection ...............................................2-13
IAN-150 IEEE 802.5 Token Ring Connection..............................................2-14
IAN-150 Browser Title Screen ....................................................................2-18
IAN-150 User Interface Main Menu (Browser) ............................................2-19
IAN-150 User Interface Main Menu ............................................................2-20
IAN-150 Time Screen .................................................................................2-23
IAN-150 Help Screen ..................................................................................2-24
IAN-150 X.28 Help Screen .........................................................................2-26
Typical IAN-150 X.28 Status Display.........................................................2-26
3-1
3-2
3-3
3-4
3-5
3-6
3-7
3-8
Node Parameter Configuration Screen .......................................................... 3-7
Node Fast Path Configuration Screen ..........................................................3-11
IP Port Configuration Screen .......................................................................3-13
Typical Node Status Monitoring Screen.......................................................3-16
Typical Port Status Display.........................................................................3-18
Typical Hardware Type Display ..................................................................3-20
Typical EIA Modem Lead Display Screen ...................................................3-22
Sample SNMP Trap Display .......................................................................3-24
4-1
4-2
4-3
4-4
4-5
Network Management Configuration Screen ................................................. 4-3
System Group Configuration Screen ............................................................. 4-4
Community Name Configuration Screen ....................................................... 4-6
Trap Output Configuration Screen................................................................ 4-7
Element Management System Configuration Screen ...................................... 4-8
2-2
2-2
2-3
2-4
IAN150/IPP MT
6/30/97
xv
xvi
4-6
4-7
Trap Filtering Screen.................................................................................... 4-9
Sample SNMP Trap Display .......................................................................4-10
5-1
5-2
5-3
5-4
5-5
5-6
5-7
5-8
5-9
5-10
5-11
5-12
5-13
5-14
5-15
Utilities Menu .............................................................................................. 5-1
ICMP Ping Parameters Screen...................................................................... 5-2
IPX Ping Parameters Screen ......................................................................... 5-4
Table Flush Utilities Menu ........................................................................... 5-5
IP Table Flush Menu.................................................................................... 5-5
IPX Table Flush Menu ................................................................................. 5-6
Sample SNMP Trap Display ........................................................................ 5-6
Pseudoport Port Configuration Screen .........................................................5-10
Pseudoport Circuit Configuration Screen .....................................................5-10
Pseudoport Operation Screen.......................................................................5-13
Loader Screen .............................................................................................5-15
Port Status and Control Screen ....................................................................5-20
Telnet Help Menu........................................................................................5-21
Typical Node Status Monitoring Screen.......................................................5-22
Typical Port Diagnostics Display.................................................................5-25
6-1
6-2
Loader Menu................................................................................................ 6-6
Factory Test Menu ....................................................................................... 6-7
7-1
Ethernet Port Status Screen .......................................................................... 7-2
8-1
Token Ring Port Status Screen ..................................................................... 8-2
9-1
9-2
9-3
9-4
9-5
9-6
9-7
9-8
9-9
9-10
9-11
9-12
9-13
9-14
9-15
9-16
Bridging Status Menu................................................................................... 9-2
General Bridging Status Display................................................................... 9-3
Spanning Tree Status Menu.......................................................................... 9-5
Spanning Tree Protocol Status Display ......................................................... 9-6
Spanning Tree Port Status Display ............................................................... 9-8
Source Routing Bridging Status Display ......................................................9-10
Bridge Relay Element Statistics Menu .........................................................9-12
BRE Port Statistics Display.........................................................................9-13
BRE Physical Port Statistics Screen ............................................................9-17
BRE Forwarding Table Screen ....................................................................9-18
BRE Routing Table.....................................................................................9-20
BRE Adjacency Table Screen......................................................................9-22
Bridging Tables Menu .................................................................................9-24
Bridge Forwarding Table Screen..................................................................9-25
Source Route Encapsulation Table Screen ...................................................9-26
SR-TB Translation Table Screen.................................................................9-28
10-1
10-2
10-3
10-4
10-5
DLSw Status and Control Menu..................................................................10-1
DLSw Port Statistics Screen........................................................................10-2
DLSw Connection Summary Screen ............................................................10-5
DLSw NetBios Name Caching Table Screen................................................10-7
LLC Status Screen ......................................................................................10-8
IAN150/IPP MT
6/30/97
11-1
11-2
11-3
11-4
11-5
11-6
11-7
11-8
11-9
11-10
11-11
11-12
11-13
11-14
11-15
11-16
11-17
11-18
11-19
11-20
11-21
11-22
11-23
11-24
11-25
11-26
11-27
11-28
11-29
11-30
11-31
11-32
11-33
11-34
11-35
11-36
11-37
11-38
IP Control and Status Menu ........................................................................11-2
IP Status Menu ...........................................................................................11-3
IP Status Screen ..........................................................................................11-4
IP Common Routing Table Screen...............................................................11-6
Address Resolution Protocol (ARP) Table Screen ........................................11-8
IP Address Table Screen..............................................................................11-9
ICMP Status Screen..................................................................................11-10
UDP Status Menu .....................................................................................11-12
UDP Statistics Screen ...............................................................................11-12
UDP Listen Table Screen ..........................................................................11-13
HTTP Status Menu ...................................................................................11-14
HTTP Protocol Statistics Screen................................................................11-15
HTTP Connections Screen.........................................................................11-16
HTTP Users screen ...................................................................................11-17
TCP Status and Control Menu...................................................................11-18
TCP Standard Statistics Screen .................................................................11-19
TCP Connection Table Screen ...................................................................11-21
TCP Connection Statistics Screen..............................................................11-23
TCP Receive Statistics Screen ...................................................................11-25
TCP Transmit Statistics Screen .................................................................11-27
RIP Status Screen .....................................................................................11-29
OSPF Status Menu....................................................................................11-30
OSPF Protocol Status Screen ....................................................................11-31
OSPF Interface Data Table Screen ............................................................11-35
OSPF Link State Database Status Menu....................................................11-37
OSPF Link State Database Table - STUB Type Screen .............................11-38
OSPF Link State Database Table - RTR Type Screen................................11-39
OSPF Link State Database Table - NET Type Screen................................11-40
OSPF Link State Database Table - NET SUM Type Screen ......................11-41
OSPF Link State Database Table - AS SUM Type Screen .........................11-43
OSPF Link State Database Table - EXT Type Screen................................11-44
OSPF Neighbor Data Table Screen............................................................11-45
OSPF Virtual Link Data Table Screen.......................................................11-47
OSPF Virtual Neighbor Data Table Screen................................................11-49
EGP Control and Status Menu...................................................................11-51
EGP Statistics Screen................................................................................11-52
EGP Neighbor Table Screen......................................................................11-53
BOOTP Status Screen...............................................................................11-55
12-1
12-2
12-3
12-4
12-5
IPX Status Menu.........................................................................................12-2
IPX Protocol Status Screen .........................................................................12-3
IPX SAP Status Screen ...............................................................................12-6
IPX Routing Table Screen ...........................................................................12-8
IPX Service Advertising Protocol Table Screen............................................12-9
13-1
13-2
13-3
Bisync Status Screen ...................................................................................13-3
Typical Circuit Status Screen ......................................................................13-5
Cleared Circuit Status Screen ......................................................................13-9
IAN150/IPP MT
6/30/97
xvii
xviii
14-1
14-2
14-3
Burroughs Poll Select Status Screen ............................................................14-3
Typical Circuit Status screen.......................................................................14-5
Clear Circuit Status Screen..........................................................................14-9
15-1
15-2
15-3
SDLC Station Status Screen........................................................................15-3
Typical SDLC Circuit Status Screen ...........................................................15-7
Cleared Circuit Status Screen ....................................................................15-11
16-1
16-2
16-3
16-4
Typical X.25 Port Status and Control Screen...............................................16-2
Typical X.25 Status Screen .........................................................................16-4
Typical X.25 Circuit Status Screen..............................................................16-7
X.25 Cleared Circuit Status Screen............................................................16-11
17-1
17-2
17-3
17-4
Frame Relay Port Status Screen...................................................................17-2
Frame Relay Virtual Trunk Status Screen....................................................17-4
Frame Relay PVC Status Screen..................................................................17-7
Frame Relay Route Topology Status Screen ..............................................17-10
18-1
18-2
18-3
18-4
18-5
ISDN Status Menu......................................................................................18-2
ISDN D-Channel Status and Statistics Screen..............................................18-3
ISDN B-Channel Status and Statistics Screen..............................................18-7
ISDN Destination Status and Statistics Screen...........................................18-10
ISDN Call History Screen .........................................................................18-16
19-1
Backup Statistics Screen .............................................................................19-2
A-1
A-2
A-3
A-4
A-5
A-6
A-7
A-8
A-9
A-10
A-11
A-12
A-13
A-14
IAN-150 AC Power Connections ..................................................................A-2
IAN-150 Tray Removal from Chassis...........................................................A-4
WAN Personality Module Replacement on IAN-150 Expansion Module .......A-6
WAN Personality Module Replacement on the IAN-150 Motherboard...........A-8
Buffer Memory (DRAM) Upgrade in the IAN-150......................................A-10
Buffer Memory (DRAM) Upgrade in the IPP..............................................A-11
TALK Program Banner ..............................................................................A-12
IAN-150 Loader Menu ...............................................................................A-12
TALK Baud Rate Configuration Screen......................................................A-13
IAN-150 Loader Menu ...............................................................................A-14
IAN-150 Loader Menu ...............................................................................A-15
IAN-150 Operating System Files (Flash Files) ............................................A-16
Edit Board Information Menu for the IAN-150 ...........................................A-16
Edit Port MAC Address Screen ..................................................................A-17
B-1
B-1
B-2
B-3
B-4
B-5
B-6
B-6
Console Port Cable Wiring (Sheet 1 of 2) .....................................................B-5
Console Port Cable Wiring (Sheet 2 of 2) .....................................................B-6
IEEE 802.3 Ethernet II Cable Wiring............................................................B-7
IEEE 802.5 Token Ring Cable Wiring..........................................................B-8
IAN-150 to V.11 DCE Cable Wiring............................................................B-9
IAN-150 to V.11 DTE Cable Wiring .......................................................... B-10
IAN-150 to V.35 DCE Cable Wiring (Sheet 1 of 2) .................................... B-11
IAN-150 to V.35 DCE Cable Wiring (Sheet 2 of 2) .................................... B-12
IAN150/IPP MT
6/30/97
B-7
B-8
B-9
B-10
B-11
B-11
B-11
B-12
B-13
IAN-150 to V.35 DTE Cable Wiring .......................................................... B-13
IAN-150 to V.35 Nodal Processor DTE/DCE Cable Wiring ....................... B-14
IAN-150 to X.21 DCE Cable Wiring.......................................................... B-15
IAN-150 to V.28 DCE Cable Wiring.......................................................... B-16
IAN-150 to V.28 DTE Cable Wiring (Sheet 1 of 3) .................................... B-17
IAN-150 to ISDN Cable Wiring ................................................................. B-20
IAN-150 to EIA RS-449 (MIL-STD-188-114A) Cable Wiring ................... B-21
Tables
1-1
1-2
1-3
1-4
1-5
1-6
1-7
1-8
1-9
1-10
IAN-150 Base Unit Configuration Options ................................................... 1-2
IAN-150 Expansion Modules ....................................................................... 1-3
Console Port Pinouts .................................................................................... 1-6
IAN-150 WAN Personality Modules (WPMs) .............................................. 1-8
IAN-150 Physical Specifications .................................................................1-10
IAN-150 System Processor and Memory Specifications ...............................1-12
IAN-150 Key Processor and Controller Components....................................1-12
IAN-150 Access Switching and Routing Specifications ................................1-12
IAN-150 Environmental Requirements.........................................................1-13
IAN-150 Power Cord Selection ...................................................................1-14
2-1
User Access Levels......................................................................................2-19
5-1
5-2
5-3
5-4
5-5
Data Patterns ............................................................................................... 5-9
TFTP Error Codes ......................................................................................5-17
IAN-150 Loopback Connectors ...................................................................5-26
IPP Loopback Connectors ...........................................................................5-26
Input/Output Signal Diagnostic Failure Types .............................................5-29
10-1
TCP Connection Failure Reasons ................................................................10-3
13-1
13-2
13-3
CU Address Values .....................................................................................13-4
Circuit Clearing Causes.............................................................................13-10
IAN-150 Bisync Diagnostic Codes ............................................................13-11
14-1
14-2
IAN-150 Diagnostic Codes........................................................................14-12
15-1
15-2
16-1
16-2
IAN150/IPP MT
6/30/97
xix
xx
A-1
A-2
IAN-150 Expansion Modules .......................................................................A-3
IAN-150 WAN Personality Modules (WPMs) ..............................................A-7
B-1
IAN-150 Cable Index ...................................................................................B-1
C-1
C-2
C-3
C-4
C-5
C-6
C-7
C-8
C-9
C-10
C-11
C-12
C-13
System Trap Messages .................................................................................C-2
Port Trap Messages......................................................................................C-2
BRE Trap Messages.....................................................................................C-4
DLSw Trap Messages ..................................................................................C-4
X.25 Trap Messages ....................................................................................C-5
SDLC Trap Messages ..................................................................................C-5
BSC Trap Messages.....................................................................................C-5
BPS Trap Messages .....................................................................................C-6
Frame Relay Trap Messages.........................................................................C-6
Chassis Manager Trap Messages (IPP Only) ................................................C-7
ISDN Trap Messages ...................................................................................C-7
OSPF Trap Messages...................................................................................C-8
IP Trap Messages....................................................................................... C-13
D-1
IAN-150 Screen Index..................................................................................D-2
IAN150/IPP MT
6/30/97
Chapter
1
Product Description
NOTE:
This chapter provides Synchrony-IAN-150 product description
information. For Synchrony ST-1000/ER-5 Independent Packet
Processor (IPP) product description information, refer to the
Synchrony ST-1000/ER-5 Internetworking Installation and
Maintenance Manual.
The Synchrony IAN-150 is designed for applications that require integration of LAN branch site
protocols and legacy traffic streams into distributed networks of any size. Figure 1-1 illustrates
an IAN-150 configuration that supports a variety of networking applications.
PUBLIC/PRIVATE
FRAME RELAY OR X.25
NETWORK
ATMs
CONSOLE
PORT
BISYNC
INTERFACE 7
INTERFACE 5
INTERFACE 6
INTERFACE 4
Synchrony
IAN-150
TM
INTERFACE 3
ETHERNET
INTERFACE 2
TOKEN RING
INTERFACE 1
CONSOLE
ETHERNET
SDLC
TOKEN
RING
Figure 1-1. Typical IAN-150 Networking Application
The IAN-150 is a standalone microprocessor-based multiport access node that provides up to
seven connections to the network. The IAN-150 performs bridging, multiprotocol routing, frame
switching, and X.25 packet switching functions between local area networks (LANs) connected
by wide area network (WAN) links.
IAN150/IPP MT
6/30/97
1-1
Chapter 1, Product Description
Maintenance and Troubleshooting Manual
The IAN-150 provides well-integrated, low-cost solutions for branch offices that need LAN and
legacy protocol integration over a WAN via leased line, Frame Relay, X.25, or ISDN backup.
The IAN-150 is available in a variety of hardware configurations that offer integration capability
for up to two LANs and five serial traffic streams or up to three LANs and three serial traffic
streams. The IAN-150 processes packets at high speed and can be configured to support a variety
of LAN and WAN protocols and physical interfaces.
Hardware Configuration Options
The IAN-150 system motherboard is shipped with either two, three, four, or five interface
connections. In its maximum configuration, the motherboard has two LAN interface connections
(one Ethernet and one Token Ring) and three serial WAN interface connections that can be preconfigured for MIL-STD-188-114A, V.11 DTE, V.28 DCE, V.28 DTE, V.35 DTE, or X.21 in
any combination. In its minimum configuration, the IAN-150 comes with a single LAN interface,
either Ethernet or Token Ring, and a single serial WAN interface. The following table lists the
IAN-150 base unit configuration interface options identified by model and part number,
associated physical interface connections, motherboard assembly number, and base configuration
number.
Table 1-1. IAN-150 Base Unit Configuration Options
Model No.
Part No.
Port Description*
Board No.
BASE No.✝
IAN-150-001
116107-1
1 Ethernet, 1 Serial port
116231-1
BASE 1
IAN-150-002
116107-2
1 Token Ring, 1 Serial port
116231-2
BASE 2
IAN-150-003
116107-8
3 Serial ports
116231-8
BASE 8
IAN-150-004
116107-4
1 Ethernet, 3 Serial ports
116231-4
BASE 4
IAN-150-005
116107-5
1 Token Ring, 3 Serial ports
116231-5
BASE 5
IAN-150-006
116107-6
1 Ethernet, 1 Token Ring, 3 Serial ports
116231-6
BASE 6
IAN-150-011
116107-11
1 Ethernet, 1 Serial port
116231-11
BASE 11
IAN-150-012
116107-12
1 Token Ring, 1 Serial port
116231-12
BASE 12
IAN-150-013
116107-13
3 Serial ports
116231-13
BASE 13
IAN-150-014
116107-14
1 Ethernet, 3 Serial ports
116231-14
BASE 14
IAN-150-015
116107-15
1 Token Ring, 3 Serial ports
116231-15
BASE 15
IAN-150-016
116107-16
1 Ethernet, 1 Token Ring, 3 Serial ports
116231-16
BASE 16
* On models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150-004, IAN-150-005, and IAN-150-006,
physical ports are located on the rear panel of the unit. On models IAN-150-011, IAN-150-012, IAN150-013, IAN-150-014, IAN-150-015, and IAN-150-016, physical ports are located on the front panel
of the unit.
✝ The BASE number identifies the motherboard installed in the IAN-150. On models IAN-150-001, IAN150-002, IAN-150-003, IAN-150-004, IAN-150-005, and IAN-150-006, the BASE number appears on a
label on the rear panel of the unit and is preceded by the serial number. On models IAN-150-011, IAN150-012, IAN-150-013, IAN-150-014, IAN-150-015, and IAN-150-016, the BASE number appears on a
label on the front panel of the unit and is preceded by the serial number.
1-2
IAN150/IPP MT
6/30/97
Additional capabilities can be provided to the IAN-150 by one of a series of optional modules
installed into the expansion module slot. A discussion of the expansion module slot and optional
expansion modules is provided below.
Expansion Module Slot
An expansion module slot provides mounting capability for an additional interface module. Table
1-2 lists optional expansion modules identified by model, printed circuit board (PCB) part
number, associated physical interface connections, module assembly part number, and expansion
slot cover plate part number. Table 1-2 also provides interoperability information between the
various expansion modules and the base unit configuration models.
Table 1-2. IAN-150 Expansion Modules
Model No.
PCB
Part No.
Module Description
Assembly
Part No.✤
Expansion Slot
Cover Plate Part No.✦
IAN-EXP-01*
116230-1
2 Serial ports
116223-1

IAN-EXP-02*
116229-2
1 ISDN-BRI port
116223-2

IAN-EXP-03*
116227-1
1 Ethernet port
116223-3

IAN-EXP-04*
116228-1
1 Token Ring port
116223-4

IAN-EXP-11✝
116230-1
2 Serial ports
116223-11
XC116978A
IAN-EXP-12✝
116229-2
1 ISDN-BRI port
116223-12
XC116979A
IAN-EXP-13✝
116227-1
1 Ethernet port
116223-13
XC116977A
IAN-EXP-14✝
116228-1
1 Token Ring port
116223-14
XC116977B
* Interoperable with base unit configuration models IAN-150-001, IAN-150-002, IAN-150-003,
IAN-150-004, IAN-150-005, and IAN-150-006.
✝ Interoperable with base unit configuration models IAN-150-011, IAN-150-012, IAN-150-013,
IAN-150-014, IAN-150-015, and IAN-150-016.
✤ The assembly number includes the PCB and the expansion module slot cover plate.
✦ The expansion module slot cover plate is separately orderable for expansion modules IAN-EXP-11,
IAN-EXP-12, IAN-EXP-13, and IAN-EXP-14.
CAUTION:
IAN150/IPP MT
6/30/97
When the chassis does not contain an expansion module, the
expansion slot must be covered by the blank cover plate to
ensure proper ventilation.
1-3
Sample Hardware Configurations
Figure 1-2 shows examples of IAN-150 hardware configurations. Note that the expansion
modules in some examples that show Ports 6 and 7 are not part of the basic configuration
options.
PORT 0
CONSOLE
INTERFACE
LABELS
MODEL:
INTERFACE 5
AC POWER
SWITCH
TM
Synchrony IAN-150
CAUTION: DISCONNECT POWER
BEFORE SERVICING.
ATTENTION: COUPER LE COURANT
AVANT L'ENTRETIEN.
SER NO.
OP
TX
RX
ETHERNET
INTERFACE 6
OP
TX
RX
INTERFACE 4
OP
TX
RX
PORT 6
INTERFACE 3
OP
TX
RX
COVER
PLATES
OP
TX
RX
ETHERNET
INTERFACE 2
OP
TX
RX
TOKEN RING
INTERFACE 1
100-240VAC 1.5A
50-60Hz
EXPANSION
MODULE
CONSOLE
PORT 3
PORT 2
MAC
COVER
(SERIAL) (ETHERNET) ADDRESS PLATE
LABEL
AC POWER
INLET
A. REAR PANEL, MODEL NO. IAN-150-001 WITH IAN-EXP-03 (2 ETHERNET, 1 SERIAL)
PORT 0
CONSOLE
INTERFACE
LABELS
MODEL:
INTERFACE 5
AC POWER
SWITCH
TM
Synchrony IAN-150
BEFORE SERVICING.
AVANT L'ENTRETIEN.
SER NO.
OP
TX
RX
ETHERNET
INTERFACE 6
OP
TX
RX
INTERFACE 4
OP
TX
RX
PORT 6
COVER
PLATES
INTERFACE 3
OP
TX
RX
PORT 3
(SERIAL)
OP
TX
RX
ETHERNET
INTERFACE 2
OP
TX
RX
TOKEN RING
INTERFACE 1
100-240VAC 1.5A
50-60Hz
EXPANSION
MODULE
CONSOLE
COVER
PORT 1
MAC
PLATE (TOKEN RING) ADDRESS
LABEL
AC POWER
INLET
B. REAR PANEL, MODEL NO. IAN-150-002 WITH IAN-EXP-03 (1 TOKEN RING, 1 ETHERNET, 1 SERIAL)
EXPANSION SLOT
COVER PLATE
PORT 5
(SERIAL)
POWER
INTERFACE
LABELS
MAC ADDRESS
LABELS
SERIAL NO./BASE
INTERFACE 5
Synchrony
IAN-150
RUN
OP
TX
RX
OP
TX
RX
INTERFACE 4
PORT 4
(SERIAL)
OP
TX
RX
TM
TM
INTERFACE 3
PORT 3
(SERIAL)
OP
TX
RX
ETHERNET
INTERFACE 2
OP
TX
RX
TOKEN RING
INTERFACE 1
COVER
PLATES
CONSOLE
PORT 0
CONSOLE
C. FRONT PANEL, MODEL NO. IAN-150-013 (3 SERIAL)
Figure 1-2. Sample IAN-150 Hardware Configurations (Sheet 1 of 2)
1-4
IAN150/IPP MT
6/30/97
INTERFACE
EXPANSION
LABEL
MODULE PORT 7
PORT 5
(SERIAL)
INTERFACE 7
POWER
INTERFACE
LABELS
MAC ADDRESS
LABEL
SERIAL NO./BASE
INTERFACE 5
Synchrony
IAN-150
RUN
OP
TX
RX
INTERFACE 6
OP
TX
RX
INTERFACE
LABEL
OP
TX
RX
OP
TX
RX
INTERFACE 4
TM
INTERFACE 3
OP
TX
RX
PORT 4
(SERIAL)
PORT 6
TM
PORT 3
(SERIAL)
OP
TX
RX
ETHERNET
INTERFACE 2
OP
TX
RX
TOKEN RING
INTERFACE 1
PORT 2
COVER
(ETHERNET) PLATE
CONSOLE
PORT 0
CONSOLE
D. FRONT PANEL, MODEL NO. IAN-150-014 WITH IAN-EXP-11 (1 ETHERNET, 5 SERIAL)
PORT 5
(SERIAL)
EXPANSION
MODULE
POWER
OP
TX
RX
ISDN
INTERFACE 6
INTERFACE
LABELS
MAC ADDRESS
LABEL
SERIAL NO./BASE
INTERFACE 5
Synchrony
IAN-150
RUN
OP
TX
RX
OP
TX
RX
PORT 6
INTERFACE 4
TM
TM
INTERFACE 3
OP
TX
RX
PORT 4
(SERIAL)
OP
TX
RX
ETHERNET
INTERFACE 2
OP
TX
RX
TOKEN RING
INTERFACE 1
PORT 1
COVER
PLATE (TOKEN RING)
PORT 3
(SERIAL)
CONSOLE
PORT 0
CONSOLE
E. FRONT PANEL, MODEL NO. IAN-150-015 WITH IAN-EXP-12 (1 TOKEN RING, 1 ISDN, 3 SERIAL)
EXPANSION SLOT
COVER PLATE
PORT 5
(SERIAL)
POWER
INTERFACE
LABELS
MAC ADDRESS
LABELS
SERIAL NO./BASE
INTERFACE 5
Synchrony
IAN-150
RUN
OP
TX
RX
OP
TX
RX
INTERFACE 4
PORT 4
(SERIAL)
OP
TX
RX
TM
TM
INTERFACE 3
PORT 3
(SERIAL)
OP
TX
RX
ETHERNET
INTERFACE 2
OP
TX
RX
TOKEN RING
INTERFACE 1
PORT 2
PORT 1
(ETHERNET) (TOKEN RING)
CONSOLE
PORT 0
CONSOLE
F. FRONT PANEL, MODEL NO. IAN-150-016 (1 ETHERNET, 1 TOKEN RING, 3 SERIAL)
Figure 1-2. Sample IAN-150 Hardware Configurations (Sheet 2 of 2)
IAN150/IPP MT
6/30/97
1-5
Physical Ports
IAN-150 physical ports consist of the following:
•
Console Port: An 8-pin RJ45 female connector that accepts cable(s) from a terminal or
computer. Table 1-3 provides a listing of Console port pinouts.
Table 1-3. Console Port Pinouts
Pin No.
1
Signal
DTR (Data Terminal Ready)
2
TXD (Transmitted Data)
3
RXD (Received Data)
4
RTS (Request to Send)
5
CTS (Clear to Send)
6
DSR (Data Set Ready)
7
GND (Chassis Ground)
8
Not used
For Console port cable and adapter information, refer to Appendix B, “Cables,” in this
manual.
•
Token Ring Port: IEEE 802.5 Token Ring connector.
•
Ethernet Port: IEEE 802.3 Ethernet connector.
•
Three Serial WAN Ports: MIL-STD-188-114A, V.11, V.28 (DCE and DTE), V.35, or
X.21 electrical interfaces.
•
Optional Expansion Modules: Two serial, one ISDN-BRI, one Ethernet, or one Token
Ring connector.
The Console port is physical Port 0. In Figure 1-2, note that ports are counted even if not
installed. Therefore, Port 1 is always Token Ring, Port 2 is always Ethernet, Port 3 is the first
serial port, and so on. Ports 6 and 7 are connected to the expansion module.
NOTE:
1-6
On models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150004, IAN-150-005, and IAN-150-006, physical ports are located
on the rear panel of the unit. On models IAN-150-011, IAN-150012, IAN-150-013, IAN-150-014, IAN-150-015, and IAN-150-016,
physical ports are located on the front panel of the unit.
IAN150/IPP MT
6/30/97
LED Indicators
The IAN-150 contains the following light-emitting-diode (LED) indicators:
•
Power LED: The Power indicator is a green LED located on the front panel of the IAN-150.
The Power LED goes on when AC power is applied to the unit and goes out when power is
removed.
•
Run LED: The Run indicator is a green LED located on the front panel of the IAN-150. The
Run LED functions during online operation (refer to Chapter 2 of this manual for additional
information).
•
OP, TX, and RX LEDs: Each port has its own set of three green LED indicator lamps:
−
OP: Operational indicator that lights when the port is configured with Admin Status set
to UP.
−
TX: Transmit indicator that lights when frames are being transmitted.
−
RX: Receive indicator that lights when frames are being received by the port.
NOTE:
On models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150004, IAN-150-005, and IAN-150-006, the OP, TX, and RX LEDs
are located on the rear panel of the unit to the left of the physical
ports. On models IAN-150-011, IAN-150-012, IAN-150-013, IAN150-014, IAN-150-015, and IAN-150-016, the OP, TX, and RX
LEDs are located on the front panel of the unit to the left of the
physical ports.
AC Power Connections
The IAN-150 is equipped with the following power connections on the rear panel:
•
AC power switch: Rocker-type switch that connects AC power to the unit or disconnects AC
power from the unit.
•
AC power inlet: A three-prong connector that supplies AC power to the unit. The power inlet
accepts international connector IEC 320 C13.
•
AC power outlet (Models IAN-150-011, IAN-150-012, IAN-150-013, IAN-150-014, IAN150-015, and IAN-150-016 only): An outlet (IEC-320 female receptacle) that can be used for
power line monitoring equipment.
Refer to Figure 1-3 for the location of the AC power connections on the rear panel of the IAN150.
IAN150/IPP MT
6/30/97
1-7
AC POWER
SWITCH
MODEL:
INTERFACE 5
TM
Synchrony IAN-150
BEFORE SERVICING.
AVANT L'ENTRETIEN.
SER NO.
OP
TX
RX
OP
TX
RX
INTERFACE 6
OP
TX
RX
INTERFACE 4
OP
TX
RX
OP
TX
RX
INTERFACE 3
OP
TX
RX
ETHERNET
INTERFACE 2
OP
TX
RX
TOKEN RING
INTERFACE 1
100-240VAC 1.5A
50-60Hz
INTERFACE 7
CONSOLE
AC POWER
INLET
A. AC POWER CONNECTIONS - MODELS IAN-150-001, IAN-150-002, IAN-150-003,
IAN-150-004, IAN-150-005, AND IAN-150-006
AC POWER
OUTLET
AC POWER AC POWER
SWITCH
INLET
B. AC POWER CONNECTIONS - MODELS IAN-150-011, IAN-150-012, IAN-150-013,
IAN-150-014, IAN-150-015, AND IAN-150-016
Figure 1-3. IAN-150 AC Power Connections
For information on power requirements of the IAN-150, refer to the section titled “Electrical
Specifications” later in this chapter.
WAN Personality Modules (WPMs)
The WPM is a small plug-in card that configures the serial DB25 port for MIL-STD-188-114A,
V.11, V.28 (DCE or DTE), V.35, or X.21. The MIL-STD-188-114A, V.28 (DCE), V.28 (DTE),
and V.35 WPMs support the associated electrical interface; the V.11 WPM supports V.11 and
X.21. The IAN-150 is shipped with one, two, or three serial interface WPMs installed, as
ordered. However, if an expansion module containing dual serial ports is installed, two additional
WPMs will be required. Table 1-4 lists the IAN-150 WPMs and their part numbers.
Table 1-4. IAN-150 WAN Personality Modules (WPMs)
Description
1-8
Electrical Interface
Part No.
MIL-STD-188-114A
MIL-STD-188-114A
100258-2
V.11
V.11 or X.21
100268-1
V.28 DTE
V.28 DTE
100255-1
V.28 DCE
V.28 DCE
100267-1
V.35
V.35
100257-1
IAN150/IPP MT
6/30/97
NOTE:
See Appendix A, “Replacement and Upgrade Procedures,” in this
manual for information on how to install or replace WPMs.
System Software Features
The IAN-150 supports Frame Relay and X.25 access switching and routing. The IAN-150 also
supports Internet Protocol (IP), Internetwork Packet Exchange (IPX) protocol, and legacy routing
protocols as well as protocol conversion (encapsulation) and IEEE bridging standards.
The IAN-150 supports dynamic reconfiguration, which allows you to change port configuration
parameters without having to reset the device.
You can use TALK to download system software from a PC. You can use Trivial File Transfer
Protocol (TFTP) to download from an IAN-150 or UNIX workstation server.
Diagnostics
The IAN-150 provides diagnostic software that performs loopback testing through the serial,
Ethernet or Token Ring interface connectors, with the ability to display the results of such tests.
Security
System management security provides five different levels of access, restricting access for
specific functions to authorized users only.
Hardware Specifications
The IAN-150 is a fully integrated multiprotocol network access device that performs routing and
switching operations. The unit is based on the Intel 80960 RISC microprocessor. The system
contains one central processing unit (CPU) motherboard capable of supporting several
tabulations of LAN and WAN interfaces and can also contain one optional expansion module to
support additional network interfaces.
Physical Specifications
The IAN-150 has a reduced-height chassis and an internal power supply. Because of its compact
size and minimal environmental operating requirements, the IAN-150 can be placed either on a
desktop in a normal commercial environment or rack mounted in an equipment cabinet. Table 15 contains the physical specifications of the IAN-150.
IAN150/IPP MT
6/30/97
1-9
Table 1-5. IAN-150 Physical Specifications
Specification
Description
Physical configuration
Single chassis, free-standing (desktop) or rack-mounted.
One CPU motherboard and one optional expansion module.
LAN interfaces: Ethernet (10 Mbps), Token Ring (4/16 Mbps).
WAN interfaces: Serial (MIL-STD-188A, V.28, V.35, X.21, V.11).
Console interface: RJ45, 8-pin.
Size
Height: 3.5 in. (8.9 cm) EIA rack; 1.93 in. (4.9 cm) ETSI rack
Width: without mounting brackets: 17.44 in. (44.2 cm)
with mounting brackets: 19.00 in. (48.3 cm)
Depth: 13.3 in. (33.8 cm)
Maximum weight
11 lb. (5 kg)
Heat dissipation
256 BTU/hour maximum
Internal hardware
modules
Power Supply, System Fan, CPU motherboard.
Ethernet interface hardware: integral to motherboard and/or expansion module.
Token Ring interface hardware: integral to motherboard and/or expansion
module.
WAN Personality Module(s): Serial types MIL-STD-188-114A, V.11, V.28 DCE,
V.28 DTE, V.35.
Optional expansion modules: Token Ring, Ethernet, ISDN, dual serial.
System Architecture Block Diagram
The IAN-150 uses advanced system architecture to obtain faster processing time. A buffer
separates Dynamic Random Access Memory (DRAM) from the system processor to allow
interface ports to access DRAM memory while the processor executes code. Both tasks are
accomplished in parallel, which eliminates bottlenecks and results in better system performance.
See Figure 1-4.
Instruction
Flash
UART
i960
Processor
DRAM
BBRAM
EPROM
>
<
>
<
Control
& Status
Console
EXP
Serial
Serial
Serial
Ethernet
Token
Ring
Figure 1-4. IAN-150 System Architecture Block Diagram
1-10
IAN150/IPP MT
6/30/97
System Processor and System Memory
The IAN-150 uses the Intel 80960 RISC processor as its CPU. System software is stored in and
executed from 5 MB of Flash memory. The motherboard has 2 MB of DRAM soldered to the
board. A 4, 8, or 16 MB DRAM SIMM can be installed to increase total addressable DRAM to
6, 10, or 16 MB. (If a 16 MB SIMM is installed, the 2 MB of base DRAM on the motherboard is
disabled.)
The following figure shows the location of DRAM chips and SIMM expansion slot; see
Appendix A of this manual for DRAM specifications.
DRAM
CHIPS
1
FLASH
MEMORY
1
EXPANSION DRAM SIMM
P1
FAN
PWR
i960
PORT
4
PORT
5
CR6 CR7 CR8
PORT 3
WAN PERSONALITY
MODULE (WPM)
NMI BUTTON
Figure 1-5. IAN-150 Motherboard
The IAN-150 motherboard also contains 128 KB of Programmable Read-Only Memory (PROM)
and 128 KB of battery backed-up System RAM (SRAM) for non-volatile storage. System
configuration is stored in the battery backed-up SRAM using lithium batteries. With this method,
configuration information may be stored for over seven years without external power applied.
The operating system of the IAN-150 monitors CPU and memory use. If the operating system
detects the processor is CPU bound or in memory regulation for over 5 minutes, the unit resets
and generates an error code. The IAN-150 system processor and memory specifications are
shown in Table 1-6.
IAN150/IPP MT
6/30/97
1-11
Table 1-6. IAN-150 System Processor and Memory Specifications
Specification
Description
Central Processor Unit
Intel 80960 RISC processor
System Memory
Boot memory (PROM): 128 KB
Data Packet Buffering DRAM: 2 MB expandable to 16 MB
Non-volatile configuration SRAM: 128 KB, battery back-up
Program Instruction memory: 5 MB Flash Memory
IAN-150 key processor and controller components are listed in Table 1-7.
Table 1-7. IAN-150 Key Processor and Controller Components
Function
System Processor
Component Utilized
Intel 80960JA-25
Serial Controller
Zilog 16C32 IUSC
Ethernet Controller
AMD PCNet 79C965
Token Ring Controller
Texas Instruments 380C25
ISDN Controller
1 Siemens PEB2086 for the D-channel; 2 Zilog 16C32 IUSC for the two
B-channels
Access Switching and Routing Specifications
Table 1-8. IAN-150 Access Switching and Routing Specifications
Specification
1-12
Description
LANs supported
Ethernet II, IEEE 802.3; IEEE 802.5 Token Ring (4 and 16 Mbps using
twisted pair cable).
Network layer protocols
IP (Internet Protocol); IPX (Novell Internetwork Packet Exchange).
Routing protocols
OSPF (Open Shortest Path First); RIP (Routing Information Protocol);
EGP for IP; IPX RIP; Remote IPX and Remote SAP.
Conversions and
encapsulations
SDLC/LLC2; SDLC/QLLC; SDLC Local Polling; SDLC Logical
Multidrop; Source Route End Station; DLSw; NetBIOS caching.
IEEE bridging standards
Spanning Tree, 802.1d Source Routing; Source Routing/Transparent;
Translation Bridging.
Wide area network (WAN)
protocols
X.25 (Switching and Access); Frame Relay (Switching and Access);
BRE 2 (proprietary WAN bridging protocol); ISDN Basic Rate Interface.
Legacy protocols
SDLC, HDLC; DDN; Burroughs Poll/Select Logical Polling for
Burroughs Poll/Select; (Async and Sync); COP/BOP serial
encapsulations; Async; 3270 Bisync; SDLC to Frame Relay (FRF.3).
WAN interfaces
ITU-T V.11; ITU-T V.28; ITU-T V.35; ITU-T X.21; ISDN Basic Rate
Interface, MIL-STD-188-114A
Network management
SNMP (Simple Network Management Protocol); MIB II (Management
Information Base); Web Server Interface (HTTP/HTML), Telnet;
Remote download of system software; Remote upload/download and
storage of system configuration.
Security
X.25, Source Calling Address Validation (SCAV), Dial-Up connection
security includes Calling Line Identification (CLI), restricted operator
access levels.
IAN150/IPP MT
6/30/97
Environmental Requirements
The IAN-150 can operate in normal commercial office environments. Environmental
requirements are listed in the following table.
Table 1-9. IAN-150 Environmental Requirements
Characteristic
Requirement
Operating Environment
Ambient operating temperature
0° to +45° C
Relative humidity
10% to 90% (noncondensing)
Altitude
to 10,000 feet (3050 meters)
Ambient temperature
Storage Environment
-20° to +65° C (drybulb); -20° to +40° C (wetbulb)
Altitude
-1,000 feet (-305 m) to +30,000 feet (9150 m)
Electrical Specifications
Nominal power requirements for the IAN-150 are as follows:
•
Voltage:
100 - 230 VAC
•
Frequency:
50/60 Hz
•
Current:
0.6 - 0.3 amps
•
Power Consumption:
less than 75 watts depending on configuration
NOTE:
The power supply automatically adjusts to the proper voltage
range without user intervention.
Outlet and Power Cord Requirements
•
Outlet requirements: The IAN-150 requires a single outlet for primary power.
NOTE:
On models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150004, IAN-150-005, and IAN-150-006, an additional external AC
power outlet is required if a monitoring device is connected
through the Console port for configuration or diagnostics. The
rear panel, however, of models IAN-150-011, IAN-150-012, IAN150-013, IAN-150-014, IAN-150-015, and IAN-150-016 contains
a power outlet (IEC-320 female receptacle) that can be used for a
monitoring device.
For on-site service by Customer Support, an AC maintenance
outlet should also be available.
•
Power cord requirements: The power inlet on the rear panel of the IAN-150 accepts one AC
power cord with international connector, IEC 320 C13. The AC power cord is connected by
a three-conductor grounding-type plug that polarizes the connection. The ground conductor
must be properly grounded.
IAN150/IPP MT
6/30/97
1-13
CAUTION:
Use the following information to select the proper AC power
cord for your application.
The appropriate power cord is selected according to the requirements of the country of
installation and by the current rating of the unit:
•
In the United States and Canada, the required male plug on the cord is NEMA 5-15 (see
Figure 1-6A). The power cord is UL-listed and CSA-labeled. Either the SVT or SJT cord set
can be used with both the desk-mounted and rack-mounted unit. The female receptacle of the
cord set must meet IEC 320 C13 requirements (see Figure 1-6B). Power cords that may be
used with the IAN-150 are listed in Table 1-10.
Table 1-10. IAN-150 Power Cord Selection
Cord Type
Size of Conductors (AWG)
Maximum Current Rating (amps)
SJT
18
10
SJT
16
12
SJT
14
12
SVT
18
10
SVT
17
12
EARTH
GROUND
LINE
NEUTRAL
A. NEMA 5-15 STYLE MALE PLUG
LINE
NEUTRAL
EARTH
GROUND
B. FEMALE RECEPTACLE
Figure 1-6. IAN-150 Power Cord Set for the United States and Canada
1-14
•
In European countries, use power cords that are appropriate for the receptacles of the country
of installation. The cord set must be HAR-certified and have a minimum conductor size of
0.75 square millimeters (cross section). The symbol HAR is displayed either on the outer
sheath or on the insulation of one of the inner conductors.
•
For other international applications, the power cord must comply with the requirements of
the country where the unit is installed.
•
Any questions concerning proper power cord use should be directed to an Ascom Timeplex
Customer Support representative.
IAN150/IPP MT
6/30/97
WARNING: IMPROPER GROUNDING COULD RESULT IN A SHOCK
HAZARD. THE GROUND CIRCUIT FOR EACH POWER
OUTLET MUST BE CONTINUOUS TO THE MAIN POWER
PANEL, WHICH MUST BE GROUNDED DIRECTLY TO AN
ELECTRICAL EARTH GROUND.
THE ASCOM TIMEPLEX SYNCHRONY IAN-150 SYSTEM
SHOULD BE AT THE SAME ISOLATED GROUND
POTENTIAL AS ALL EQUIPMENT DIRECTLY ATTACHED
TO IT.
WARNUNG: BEI UNZUREICHENDER ERDUNG BESTEHT
STROMSCHLAGSGEFAHR. DEI ERDUNG MUSS EINE
DIREKTE VERBINDUNG MIT DER HAUPTSTROMVERSORGUNGSPLATTE HABEN, WELCHE AUCH EINE
DIREKTE VERBINDUNG ZU EINER ERDVERBINDUNG
HAT.
DIESES GERAET UND ALLE ANGESCHLOSSENEN
GERAETE SOLLTEN AUF DIESELBE ISOLIERTE
ERDSPANNUNG ANGESCHLOSSEN WERDEN.
AVERTISSEMENT: UNE MISE A LA TERRE INCORRECTE PEUT
PRESENTER UN RISQUE DE CHOC ELECTRIQUE.
LE CIRCUIT DE MISE A LA TERRE DE CHAQUE PRISE
DOIT ETRE RACCORDE DE FACON DIRECTE A UN
PANNEAU D’ALIMENTATION PRINCIPAL QUI DOIT
ETRE RELIE DIRECTEMENT A UNE PRISE DE TERRE.
CET APPAREIL NE CONTIENT AUCUN ELEMENT QUE
L’UTILISATEUR PUISSE REPARER. CONFIEZ LA
MAINTENANCE A UNE PERSONNE TECHNIQUE
QUALIFIEE.
IAN150/IPP MT
6/30/97
1-15
Chapter
2
Getting Started
NOTE:
The hardware installation information and procedures contained
in this chapter apply to the Synchrony IAN-150. For hardware
installion information and procedures relating to the Synchrony
ST-1000/ER-5 Independent Packet Processor (IPP) module, refer
to the Synchrony ST-1000/ER-5 Internetworking Installation and
Maintenance Manual.
The software and user interface information contained in the
“System Software Description” and “User Interface Description”
sections of this chapter apply to both the IAN-150 and the IPP
module. In those sections of this chapter, all references to the
IAN-150 also apply to the IPP.
Before you open the IAN-150 carton, examine it for damage. If damage is not visible, unpack the
carton and check the contents for damage. Save all packing materials. If damage is noted, follow
the instructions in the front of this manual in If Product Is Received Damaged.
The IAN-150 is shipped as a fully integrated unit in a single chassis. All interface modules are
already installed as ordered This chapter gives you the information you need to start using your
IAN-150. It describes site installation procedures, powering up the unit, login procedures and
access levels, and provides a comprehensive description of the user interface. The IAN-150 is
designed for either desktop or rack mount operation.
For additional information, refer to the following chapters and appendix in this manual:
•
To install additional modules, refer to Appendix A, “Replacement and Upgrade Procedures.”
•
For utilities and diagnostics, refer to Chapter 5, “Utilities and Diagnostics.”
•
For troubleshooting procedures, refer to Chapter 6, “Troubleshooting.”
IAN150/IPP MT
6/30/97
2-1
Chapter 2, Getting Started
Installation Procedures
The following procedures provide step-by-step instructions to install the IAN-150 and operate the
user interface.
NOTE:
2-2
Procedures 2-1 to 2-8 apply to the IAN-150. Procedures 2-9 to 215 apply to both the IAN-150 and the IPP module.
•
Procedure 2-1. Desktop Mounting
•
Procedure 2-2. Rack or Cabinet Mounting
•
Procedure 2-3. Removing a Rack-Mounted or Cabinet-Mounted Chassis
•
Procedure 2-4. Applying AC Power to Verify Operability
•
Procedure 2-5. Connecting a Terminal or Computer to the Console Port
•
Procedure 2-6. Connecting to the IEEE 802.3 Ethernet Interface
•
Procedure 2-7. Connecting to the IEEE 802.5 Token Ring Interface
•
Procedure 2-8. Connecting to the Serial WAN Interface
•
Procedure 2-9. Login Procedure for the IAN-150
•
Procedure 2-10. Setting Time and Date on the IAN-150
•
Procedure 2-11. Using the Read Command to Examine Current Settings
•
Procedure 2-12. Using the Write Command to Enter or Change Settings
•
Procedure 2-13. Deleting Current Settings
•
Procedure 2-14. Duplicating Configuration Settings
•
Procedure 2-15. Activating Configuration Settings
IAN150/IPP MT
6/30/97
Mounting the IAN-150
Procedure 2-1. Desktop Mounting
1. To install the IAN-150 for desktop operation, position the unit to allow at least 1 inch of
clearance on each side and 6 inches at the rear of the unit for proper ventilation and for cable
or power cord clearance. Make sure the rubber feet are installed on the bottom of the unit.
CAUTION:
On models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150004, IAN-150-005, and IAN-150-006, the IAN-150 cooling fan
vents are located on the bottom of the chassis. If the unit is
placed on a desktop without the rubber feet installed, the vents
will be blocked and the IAN-150 will overheat.
2. Verify that the LAN and WAN interface cables are free of any binding obstructions from
nearby office furniture and that cables are safely removed from office traffic lanes.
Procedure 2-2. Rack or Cabinet Mounting
The IAN-150 can be installed in a 19-inch EIA rack or cabinet or in an ETSI international rack
using a single pair of rack mount brackets. Ascom Timeplex equipment cabinets conform to the
EIA standard. Rack mount assembly parts are contained in a Rack Mount Bracket Kit. The
following Rack Mount Bracket Kits are available:
•
For models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150-004, IAN-150-005, and
IAN-150-006, Rack Mount Bracket Kit, P/N 116944-1, allows the IAN-150 chassis to be
mounted flush with the rack or cabinet (see Figure 2-1).
•
IAN-150-016:
-
Rack Mount Bracket Kit, P/N 116943-1, allows the IAN-150 chassis to be mounted flush
with the rack or cabinet (see Figures 2-2A and 2-2B).
-
Rack Mount Bracket Kit, P/N 116943-2, allows the IAN-150 chassis to be recessed from
the rack or cabinet approximately 5 inches (see Figures 2-2C and 2-2D).
When mounting the IAN-150 in a rack or cabinet, first determine whether the front panel or the
rear panel is to face out. For models IAN-150-011, IAN-150-012, IAN-150-013, IAN-150-014,
IAN-150-015, and IAN-150-016, also determine whether the IAN-150 is to be mounted flush
with the rack or cabinet or recessed from the rack or cabinet. Then perform the following steps.
IAN150/IPP MT
6/30/97
2-3
NOTE:
For models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150004, IAN-150-005, and IAN-150-006:
• For front panel mounting, remove and discard the two
front flat-head screws that attach the IAN-150 cover to
the motherboard tray. The bracket mounting screws
use those same two holes.
• For rear panel mounting, remove and discard the two
rear flat-head screws that attach the IAN-150 cover to
the motherboard tray. The bracket mounting screws
use those same two holes.
1. Remove rubber feet and discard them if mounting the IAN-150 directly above other
equipment.
2. Using the four flat-head screws provided with the brackets, attach the two mounting brackets
to the IAN-150 chassis as follows:
For front panel mounting:
Attach the two brackets to both sides of the front end of the
chassis.
For rear panel mounting:
Attach the two brackets to both sides of the rear end of the
chassis.
IAN-150-006, refer to Figure 2-1A for an illustration of flush front panel mounting and to
Figure 2-1B for flush rear panel mounting.
IAN-150-016, refer to Figure 2-2A for an illustration of flush front panel mounting and to
Figure 2-2B for an illustration of flush rear panel mounting. Refer to Figure 2-2C for an
illustration of recessed front panel mounting and to Figure 2-2D for an illustration of
recessed rear panel mounting.
The left bracket always attaches to the left side of the chassis, and the right bracket always
attaches to the right side of the chassis. To determine left from right, remember that the side
of the bracket which attaches to the rack flange has only one hole, which must always be on
the bottom.
3. While supporting the IAN-150 chassis in its intended operating position in the rack or
cabinet, secure it with the two No. 10 screws provided in the kit. The screws are inserted
through the bottom hole of each bracket and into the equipment rack flange.
2-4
NOTE:
In some cases the holes in the flange are not threaded; therefore,
two clip nuts are provided with the Rack Mount Bracket Kit.
CAUTION:
When mounting the IAN-150 in a cabinet with other equipment,
verify that the fan ventilation port(s) and the chassis side airflow
ventilation ports are not obstructed.
IAN150/IPP MT
6/30/97
FRONT
PANEL
UPPER
SCREW
(2 REQUIRED)
NOTE: BRACKETS USED
ON FRONT.
E
OL
NS
CO
ING
NR
E
OK
T
REAR
PANEL
CE
CE
2
OP
TX
RX
FA
ER
INT
OP
TX
RX
3
OP
TX
RX
FA
ER
INT
E2
AC
RF
E
INT
LOWER
SCREW
(2 REQUIRED)
ET
RN
HE
ET
OP
TX
RX
OP
TX
RX
N
ISD
OP
TX
RX
OP
TX
RX
A. BRACKETS FOR FRONT PANEL MOUNTING
G
N
KE
C
FA
ER
INT
E2
CE
3
OP
TX
RX
OP
TX
RX
AC
RF
E
INT
INT
E2
OP
TX
RX
FA
ER
OP
TX
RX
RIN
TO
ET
RN
HE
ET
UPPER
SCREW
(2 REQUIRED)
E
OL
NS
CO
REAR
PANEL
OP
TX
RX
N
ISD
OP
TX
RX
LOWER
SCREW
(2 REQUIRED)
OP
TX
RX
NOTE: BRACKETS USED
ON REAR.
B. BRACKETS FOR REAR PANEL MOUNTING
Figure 2-1. IAN-150 Rack Mounting Brackets for
Models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150-004, IAN-150-005, and IAN-150-006
IAN150/IPP MT
6/30/97
2-5
FRONT
PANEL
REAR
PANEL
NOTE: BRACKETS USED
ON FRONT.
SCREWS
(4 REQUIRED)
A. BRACKETS FOR FLUSH FRONT PANEL MOUNTING
REAR
PANEL
SCREWS
(4 REQUIRED)
NOTE: BRACKETS USED
ON REAR.
B. BRACKETS FOR FLUSH REAR PANEL MOUNTING
(Sheet 1 of 2)
2-6
IAN150/IPP MT
6/30/97
FRONT
PANEL
REAR
PANEL
NOTE: BRACKETS USED
ON FRONT.
SCREWS
(4 REQUIRED)
C. BRACKETS FOR RECESSED FRONT PANEL MOUNTING
REAR
PANEL
SCREWS
(4 REQUIRED)
NOTE: BRACKETS USED
ON REAR.
D. BRACKETS FOR RECESSED REAR PANEL MOUNTING
(Sheet 2 of 2)
IAN150/IPP MT
6/30/97
2-7
Refer to Figure 2-3 for illustrations of rack-mounted chassis.
REAR
PANEL
E
OL
NS
CO
ING
NR
KE
TO
ET
RN
HE
ET
CE
2
INT
3
OP
TX
RX
FA
ER
INT
OP
TX
RX
2
CE
FA
ER
CE
FA
ER
INT
OP
TX
RX
OP
TX
RX
OP
TX
RX
N
ISD
OP
TX
RX
OP
TX
RX
CLIP NUT
(IF REQ'D)
CABINET RACK
MOUNTING FLANGE
RACK MOUNTING
SCREW (2 REQ'D)
A. FLUSH REAR PANEL RACK MOUNTING FOR MODELS IAN-150-001, IAN-150-002, IAN-150-003,
IAN-150-004, IAN-150-005, AND IAN-150-006
FRONT
PANEL
TM
LE
NSO
CO
E
AS
O./B
LN
RIA
SE
NET2
HER CE
ET RFA
INTE
TM
ny
chro
Syn 50
-1
IAN
CE
RFA
3
ING
NR 1
KE CE
TO RFA
INTE
OP
TX
RX
OP
TX
RX
INTE
5
CE
RFA
INTE
CE
RFA
4
OP
TX
RX
INTE
WER
PO
N
RU
OP
TX
RX
OP
TX
RX
CLIP NUT
(IF REQ'D)
CABINET RACK
MOUNTING FLANGE
RACK MOUNTING
SCREW (2 REQ'D)
B. RECESSED FRONT PANEL RACK MOUNTING FOR MODELS IAN-150-011, IAN-150-012, IAN-150-013,
IAN-150-014, IAN-150-015, AND IAN-150-016
Figure 2-3. IAN-150 Rack-Mounted Chassis
2-8
IAN150/IPP MT
6/30/97
Procedure 2-3. Removing a Rack-Mounted or Cabinet-Mounted Chassis
This procedure provides instructions to do one of the following:
•
Remove a rack-mounted or cabinet-mounted IAN-150 chassis (applicable to all IAN-150
models)
•
Remove the IAN-150 tray without removing the rack-mounted or cabinet-mounted IAN-150
cover (applicable to models IAN-150-011, IAN-150-012, IAN-150-013, IAN-150-014, IAN150-015, and IAN-150-016 only)
To remove a rack-mounted or cabinet-mounted chassis (applicable to all IAN-150 models):
1. Disconnect all cables from the IAN-150 chassis and ensure that the unit is unplugged before
you remove it from the rack or cabinet.
2. Remove the IAN-150 from the rack or cabinet by unscrewing the two No. 10 rack-mounting
screws that attach the mounting brackets to the cabinet or rack mounting flange (see Figure
2-3).
3. Carefully slide the chassis out of the rack or cabinet.
To remove the IAN-150 tray without removing the rack-mounted or cabinet-mounted IAN-150
cover (applicable to models IAN-150-011, IAN-150-012, IAN-150-013, IAN-150-014, IAN-150015, and IAN-150-016 only):
1. Ensure that the unit is unplugged before you remove the tray from the rack-mounted or
cabinet-mounted IAN-150 cover.
2. Loosen and remove the three Phillips-head screws and washers on the IAN-150 rear panel:
the screw and washer located in the lower left corner, in the lower right corner, and in the
upper middle portion of the rear panel (see Figure 2-4).
3. Carefully slide the tray out of the IAN-150 cover. The IAN-150 cover remains attached to the
rack or cabinet.
IAN150/IPP MT
6/30/97
2-9
TRAY
REAR
PANEL
LOWER
RIGHT SCREW
UPPER
MIDDDLE SCREW
LOWER
LEFT SCREW
Figure 2-4. Removing IAN-150 Tray from Rack-Mounted Cover
(Models IAN-150-011, IAN-150-012, IAN-150-013, IAN-150-014, IAN-150-015, and IAN-150-016)
2-10
IAN150/IPP MT
6/30/97
Powering Up the IAN-150
Once you have completed the physical site installation, you are ready to power on the IAN-150.
Procedure 2-4. Applying AC Power to Verify Operability
This procedure verifies the basic functioning of the IAN-150.
1. Set the AC power switch, located on the rear panel of the IAN-150 chassis, to the OFF
position. The power switch is a two-position rocker-type switch. AC power is set to OFF
when the 0 rocker end is flush with the rear panel.
NOTE:
If a User Interface terminal is available, carry out steps 2 and 3;
if not, proceed to step 4.
2. Connect the user interface terminal to the console port of the IAN-150. The console port is an
8-pin RJ45 connector.
NOTE:
For models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150004, IAN-150-005, and IAN-150-006, the console port is located
on the far right side of the chassis rear panel. For models IAN150-011, IAN-150-012, IAN-150-013, IAN-150-014, IAN-150-015,
and IAN-150-016, the console port is located on the far right side
of the chassis front panel.
See Procedure 2-5 of this chapter for information on the user interface terminal setup
procedure.
3. Attach a power cord to the terminal and power up the unit. Check for normal operation of the
terminal.
4. Attach the power cord to the IAN-150 and set the power switch to the ON position. In the
ON position the side marked 1 is flush with the rear panel.
5. As the IAN-150 performs its bootup sequence, you can verify normal operation by observing
the LED indicators on the front panel.
•
When the AC power switch is set to the ON position, the POWER indicator (green LED)
is always lit (steady ON).
•
At the start of the bootup sequence, the RUN indicator (green LED) flashes momentarily
and then goes OFF.
•
At the end of the bootup sequence, the RUN indicator begins to flash at regular intervals
(approximately once per second). This indicates correct hardware operation.
•
If the RUN indicator does not flash, or remains unlit, see Chapter 6, “Troubleshooting.”
The IAN-150 system is now ready for configuration programming or programming verification.
See the Synchrony IAN-150/IPP Reference Manual for configuration programming details. Refer
to Chapter 6, “Troubleshooting,” for details on how to check system interface ports and perform
procedures that check hardware components.
IAN150/IPP MT
6/30/97
2-11
Procedure 2-5. Connecting a Terminal or Computer to the Console Port
NOTE:
For models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150004, IAN-150-005, and IAN-150-006, the console port is located
on the far right side of the chassis rear panel. For models IAN150-011, IAN-150-012, IAN-150-013, IAN-150-014, IAN-150-015,
and IAN-150-016, the console port is located on the far right side
of the chassis front panel.
The console port allows you to access the user interface to perform diagnostic routines and
change system interface parameters by using an asynchronous terminal or computer running in
terminal emulation mode. Once the IAN-150 has been configured for online operation, the
terminal or computer is not required for normal online operation.
WARNING: ALL PORTS ON THIS EQUIPMENT COMPLY WITH SELV
REQUIREMENTS OF EN 60950. CONNECT ONLY
EQUIPMENT COMPLYING WITH THE SELV
REQUIREMENTS OUTLINED IN THE LATEST REVISION
OF SAFETY STANDARD EN 60950.
1. Connect an asynchronous terminal or a computer to the IAN-150 console port using the
appropriate cable (standard 8-pin, RJ45) described above and in Appendix B, “Cables.” The
maximum recommended length of the cable between the console port and the terminal or
computer is 50 feet at 9600 bps.
2. Set the communication parameters:
•
•
For an asynchronous terminal, set the following parameters:
- Data rate:
9600 bps
- Data bits:
8
- Parity:
none
- Stop bits:
1
For a computer running the TALK terminal emulation program, all parameters except
baud rate are set automatically. To set the default baud rate for the IAN-150, apply
power to the unit and press Enter. The software will establish the default baud rate.
3. Log on to the IAN-150 user interface (see Procedure 2-9 in this chapter).
4. If your terminal or terminal emulation software does not emulate a VT100 or VT220, select
the appropriate terminal ID from the list of IDs and supported terminal types below:
TERMINAL ID
IBM 3101
IBM 3161
DEC
WYSE
ADDS
HZ
TTY
TERMINAL TYPE (NAME)
IBM-3101
IBM-3161, IBM-3163
VT-100, VT-220
TVI-910, TVI-920, TVI-925, WYSE-50
ADDS-VP
HZ-1500
TELETYPE MODE
The default terminal ID is DEC.
2-12
IAN150/IPP MT
6/30/97
5. Condition necessary, configure the IAN-150 for a non-default terminal ID by pressing the
period < . > key to access the command line. At the command line prompt, type TERM
followed by a space and the terminal ID as shown above. Press Enter.
Procedure 2-6. Connecting to the IEEE 802.3 Ethernet Interface
NOTE:
Before starting procedures 2−6, 2−7, and 2−8, refer to Appendix
B, “Cables,” to determine which cables are required for each
application.
1. Connect the appropriate RJ45 cable to the IEEE 802.3 Ethernet interface connector. The
connector is a 10BASE-T wired connector. The figure below illustrates the IEEE
802.3/Ethernet II interface connection.
2. Connect the other end of the cable to the installed wiring plant equipment. Typically, the
IAN-150 Ethernet cable is connected to an Ethernet hub or Ethernet LAN switch.
IAN-150
Interface #1
IEEE 802.3/
ETHERNET II
Interface #2
RJ45
UTP Connector
Interface #3
Unshielded Twisted Pair (UTP):
An 8-pin RJ45 modular jack for interfacing
to an Ethernet LAN.
Interface #4
&
Interface #5
Interface #6
and/or
Interface #7
Figure 2-5. IAN-150 IEEE 802.3/Ethernet II Connection
IAN150/IPP MT
6/30/97
2-13
Procedure 2-7. Connecting to the IEEE 802.5 Token Ring Interface
The IAN-150 provides an 8-pin RJ45 connector to connect to a Token Ring LAN. The
appropriate adapter cable connects the IAN-150 Token Ring interface to the installed Token Ring
wiring plant. (IBM Type 3 cabling installations call for an RJ45 connector on each end of the
twisted pair cable.)
1. Connect the RJ45 cable from the IAN-150 Token Ring port to a port of the Token Ring
twisted pair MAU or Token Ring LAN switch. The figure below illustrates the IEEE 802.5
Token Ring interface connection.
IAN-150
IEEE 802.5/
Token Ring
Interface #1
UTP
Connector
RJ45
RJ45
Connector
RI RO
Interface #2
Interface #3
4-PORT
TWISTED-PAIR
MAU
Unshielded Twisted Pair (UTP) connector:
An 8-pin RJ45 modular jack for interfacing IBM type 3
cable to IEEE 802.5 Token Ring LAN.
Interface #4
&
Interface #5
Interface #6
and/or
Interface #7
Figure 2-6. IAN-150 IEEE 802.5 Token Ring Connection
2-14
IAN150/IPP MT
6/30/97
Procedure 2-8. Connecting to the Serial WAN Interface
The IAN-150 provides up to three serial interfaces on the motherboard and up to two additional
serial interfaces on the optional expansion board. In all cases the chassis will have one standard
25-pin D-shell connector for each serial interface port. The electrical characteristics of each serial
interface are determined by a personality module that is installed and associated with the port.
All serial interfaces are clearly labeled by a printed tag just above the interface connector,
identifying the type of interface.
The IAN-150 supports the following serial interfaces:
•
ITU-T V.11
DTE
•
ITU-T V.28
DTE or DCE
•
ITU-T V.35
DTE
•
ITU-T X.21
DTE
•
MIL-STD-188-114A
DTE
All of the above serial interfaces are defined as DTE (except for V.28, which can be defined as
DTE or DCE) by ordering the appropriate WAN Personality Module (WPM). All of the above
interfaces with the exception of ITU-T X.21 will support V.54 Loopback testing. For each of the
serial interface types, select the appropriate serial interface adapter cable for your application.
NOTE:
Refer to Appendix B to determine the cables that are necessary for
your application. Fasteners on the serial WAN interface modules
are non-metric on the IAN-150. If a cable with metric fasteners is
used, replace the connector fasteners on the interface module with
the metric fasteners packaged with the IAN-150.
To connect IAN-150 serial interfaces:
1. Connect the male end of the DB25 connector of the appropriate cable to the chassis-mounted
female serial DB25 connector on the IAN-150.
2. Connect the other end of the cable to the DTE or DCE device. (All DTE devices can be
adapted for DCE with the substitution of an appropriate DTE/DCE cable.)
IAN150/IPP MT
6/30/97
2-15
System Software Description
NOTE:
This section applies to both the IAN-150 and the IPP module. All
references to the IAN-150 also apply to the IPP module.
The IAN-150 is shipped from the factory with system and utility software already installed in
Flash memory. Loading the system or utility software is normally not required. The IAN-150
system software and operating system updates are shipped from the factory on standard DOS
format, 3-1/2-inch, double-sided, high-density diskettes.
The IAN-150 software consists of two modules:
•
the operating system and configuration database
•
TALK terminal emulation program
You may use any standard terminal emulation program to access the IAN-150 user interface in
normal operation; however, the TALK program must be used during installation and loading of
the operating system software when performing a serial download from a DOS PC. TALK was
created by Ascom Timeplex specifically for this purpose.
The IAN-150 can be upgraded with a new version of system or utility software by either of the
following methods:
•
serial download using a DOS-based computer connected to the IAN-150 console port.
•
from any TFTP device, using the download features of the system software.
NOTE
This software release automatically converts your existing
databases to accommodate new system requirements. After your
system has been upgraded, reverting to the old software will
cause a database reset.
For instructions on how to load system software using these methods, see Appendix A,
“Replacement and Upgrade Procedures” in this manual.
Boot PROM
In addition to the system software contained on the diskettes (and loaded in Flash memory), there
is embedded boot software in a PROM on the IAN-150. This software is similar in function to
the BIOS program that resides within a DOS PC EPROM.
During the startup process of the IAN-150, the system software is executed from the Boot
PROM. The Boot PROM also contains utilities that are not available or required on a console
port terminal during normal online operation.
The Boot PROM may be accessed during startup by pressing Esc twice within approximately 10
seconds of power-up. For a complete description of the utilities available via the Boot PROM,
refer to Appendix A, “Replacement and Upgrade Procedures,” in this manual.
2-16
IAN150/IPP MT
6/30/97
User Interface Description
NOTE:
This section applies to both the IAN-150 and the IPP module. All
references to the IAN-150 also apply to the IPP module.
The IAN-150 contains a menu-driven user interface that provides access to configuration,
monitoring, management, and diagnostic functions. The user interface communicates with a
terminal attached to the IAN-150 console port, with a similarly connected PC running terminal
emulation software, with a remote terminal emulator via a TELNET session, or by using a web
browser. Up to four simultaneous user interface connections are supported.
Communication with the user interface is similar for console connection, a PC that runs terminal
emulation software, and using TELNET to connect to a remote terminal emulator. The following
paragraphs describe the login procedure if you use any of these three methods. If you use a web
browser to access the IAN-150, refer to Login Using Web Browser in Procedure 2-9.
When you press Enter at the initial IAN-150 title screen, you are prompted for a login name
followed by a password. Five different user access levels and passwords provide different levels
of functionality and authorization.
Procedure 2-9. Login Procedure for the IAN-150
Login Without Web Browser
This procedure assumes an asynchronous terminal or a PC running a terminal emulation software
program is connected to the console port of the IAN-150.
NOTE:
If you use a laptop PC, the Advanced Power Management (APM)
feature may cause problems for disk access initiated by TALK.
1. Power on the IAN-150 and the asynchronous terminal or PC. If you are using a PC running
terminal emulation software, launch the terminal emulation software and wait (approximately
45 seconds) for the IAN-150 title screen to appear.
•
For an asynchronous terminal, be sure that the data rate has been set to 9600 bps, data
bits to 8, parity to None, and stop bits to 1.
•
For a PC running TALK, Version 5.2 or greater is required. Be sure that the TALK
program banner is visible at the bottom of the screen. If you do not see an IAN-150 title
screen, press F6 to switch to another COM port. (To launch TALK, type talk and press
Enter at the C:\ prompt or from the directory in which the TALK program is located.)
NOTE:
•
TALK should not be initiated from your Windows program to
execute a load, save, or restore operations.
For a PC running PROCOMM, be sure the line settings are set to the following values:
baud rate: 9600; data bits: 8 bits; parity: None; stop bits: 1.
2. From the IAN-150 title screen, press Enter to get to the login prompt. Enter the appropriate
user name and press Enter. (Default user names are shown in Table 2-1.)
IAN150/IPP MT
6/30/97
2-17
3. The IAN-150 then displays the Password prompt. Enter the appropriate password and press
Enter. If the access name and password match, the IAN-150 displays the Main Menu.
NOTE:
If the login name and password do not match, the IAN-150 title
screen will redisplay and you will have to reenter both the user
name and password. After three unsuccessful login attempts, the
user interface will lock up and you will either have to wait 30
minutes or power cycle the IAN-150 before attempting to login
again.
Login Using Web Browser
This procedure assumes you are using a PC on which you have installed a web browser, such as
Netscape Navigator, or other browser software. Initiate your web browser, and at the
Address/Location/URL line, enter the IP of the IAN-150 you wish to access. For example, type
123.0.0.10 or http://123.0.0.10. The system displays the IAN-150 title screen and a login dialog
box similar to the screen shown in Figure 2-7. Enter your login name and password and press
Enter. If the access name and password match, the IAN-150 displays the Main Menu as shown
in Figure 2-8.
NOTE:
If the system displays the Main Menu, then almost immediately
returns to the Title Screen, there may be a problem with the time
setting. Exit the web browser and log onto the IAN-150 using
Async or TELNET. Verify appropriate time and offset from
UDT/GMT, and make any necessary corrections. Refer to Time
later in this chapter for additional information.
Figure 2-7. IAN-150 Browser Title Screen
2-18
IAN150/IPP MT
6/30/97
Figure 2-8. IAN-150 User Interface Main Menu (Browser)
User Access Levels
The IAN-150 user interface has five hierarchical levels of access. Each level has its own user
name, password, and associated privileges. The lowest priority level (Level 4), monitor, allows
you only to perform Read commands, which provide access to standard, configured parameter
information. Level 3, analyst, allows you to perform diagnostics, the Ping Utility, and Read
commands. The monitor and analyst access levels do not allow you to make configuration
changes, and do not display the more advanced configuration parameters, which can remain at
default settings for most applications. Level 2, user, allows you to view all configuration
parameters and write changes to the configuration database. Changes will take effect if the port is
cycled after a parameter is changed. Level 1, expert, allows you to perform all port operations
and configuration commands. Level 0, superuser, is the highest access level and allows all of the
privileges of Level 1 with added abilities to change the access class database and to access the
VxWorks operating system. Table 2-1 summarizes characteristics of each user access level.
Table 2-1. User Access Levels
Level
Username
Password
Privileges
Mode
4
monitor
view
Read only
Partial Access
3
analyst
diagnose
Read, Diagnostics, Ping
Partial Access
2
user
configure
Read, Write, Diagnostics, Ping
Standard
Access
1
expert
perform
Read, Write, Port Operations, Diagnostics, Ping
Full Access
0
superuser
root
Read, Write, Port Operations, Diagnostics, Ping,
Write to Access Class Database, access VxWorks
Full Access
IAN150/IPP MT
6/30/97
2-19
NOTE:
Your access level determines the type of commands you can issue,
and what information you may view. Refer to Appendix D, “User
Interface Screen Index” in this manual, to see which screens
display abbreviated information when viewed from partial access
mode.
User Interface Menu Structure
After you logon to the system, the User Interface Main Menu appears. At the top of the menu is a
banner that displays copyright and software version information and the IP address of the
IAN-150 that is currently being managed. An IP address of all zeros indicates that the IAN-150
to which you are directly connected is the node that is being managed. The Main Menu shown in
the following figure will display if you login by using a method other than using a web browser
to access the IAN-150 user interface.
======================================================================
Copyright(C) 1996,97 Ascom Timeplex Trading AG
All Rights Reserved
Version 1.1.0 June 30, 1997
======================================================================
000.000.000.000
1. Status and Control
2. Configuration
3. Utilities
4. Diagnostics
5. Time
6. Help
7. Exit
Figure 2-9. IAN-150 User Interface Main Menu
Menus and screens that the system displays when you access the IAN-150 using a web browser
are similar to those that display during a TELNET session. Differences are only in how you issue
a command or in how parameters are displayed; menus and screen parameters remain the same
regardless of how you access the user interface. Although this manual provides some explanation
of the differences in the user interface depending on the type of access method you choose, the
access procedures and screen illustrations presented in this manual represent a TELNET
session.Choose Help from the Main Menu to provide information about moving around the
various screens and menus.
The user interface is subdivided according to the selections on the Main Menu. Menus and
screens are arranged in a hierarchical tree structure, with lower level menus and screens
accessible from higher level menus. Each screen below the Main Menu is identified by a number,
by a hot-key sequence that consists of a series of capital letters enclosed in brackets, and by a
screen name. Appendix D in this manual lists the name of each IAN-150 screen, associated hotkey initials and screen number, and identifies which screens display abbreviated information
when viewed in partial access mode.
2-20
IAN150/IPP MT
6/30/97
If you are using TELNET access, to proceed to the next lower level of the menu tree, type the
number that corresponds to the option you desire. To go directly to a specific menu or screen,
press the period < . > key to display the command line. At the command line, enter the
appropriate screen number or hot-key initials associated with the menu or screen you want. For
example, to access the BRE Statistics menu, enter SBB or 131 from the command line of any
menu or screen. To access the BRE Adjacency Table screen, enter SBBA or 1315 from any
command line. If you are using a web browser, use the mouse to click on the menu item you
want to view. If you know the hot-key associated with the screen or menu you want to view, type
a slash < / > directly after the IP address of the IAN-150, followed by the hot-key letter or
combination of letters. You may type the hot-key in uppercase or lowercase letters. For example,
type 123.0.0.10/SPP; where 123.0.0.10 is the IP address of the IAN-150, and SPP is the hot-key
associated with the Port Status and Control screen. For further information, from the Main Menu
click your mouse on Help.
In TELNET, to suppress the display of all subsequent menus or screens, press the apostrophe < ‘
> key. To enable screen displays after they have been disabled, or to refresh the current display,
press the forward slash < / > key. The cursor will move to the first data entry field in the current
display. To proceed to the next data field in the display, press Tab or Enter. To go back to the
previous data field, press < - >. To access the command line to execute Read, Write, and other
commands, press the period < . > key. The prompt Enter Selection (000.000.000.000) ==> will
appear at the bottom of the screen. Not all commands are available for all screens. The database
commands that are available for each screen appear above the command line. To view a list of
keystroke commands and their functions, select Help from the Main Menu, or type H at any
command line prompt and press Enter. For more information, see User Interface Commands
later in this chapter.
If you use a web browser, commands that are available for each screen display at the top of the
screen, above the parameters. Use your mouse to click on the command you want to issue. A
black dot will appear in the circle to the left of the command to indicate the command you chose.
To have the IAN-150 execute the command, click your mouse on Send Command radio button.
As you navigate back and forth within the menu tree, the IAN-150 maintains a history of the
screens you selected. To go back to the previous screen selected, press Esc or the backslash
< \ > key. To return to the Main Menu, press the tilde < ~ > key. You do not have to be at the
command line of a screen to use Esc, backslash < \ >, or tilde < ~ >. If you use a web browser,
click the mouse on the To Top Menu link located at the bottom of the screen. This will return
you to the Main Menu. If you want to go backward to the previous menu or screen, click on the
Up One Menu link located at the bottom of the screen.
The user interface can store two screens of data at a time. This means if you have issued Read
commands to display port or circuit data or other data from the configuration database, you can
go back to the last two previous screens without having to execute another Read command.
IAN150/IPP MT
6/30/97
2-21
User Interface Main Menu Options
If you use TELNET access, to make selections from the Main Menu type the number or hot-key
that corresponds to the screen you want to view. If you use a web browser, to make selections
from the Main Menu use your mouse and click on the menu item that corresponds to the screen
you want to view. The paragraphs below give brief descriptions of the options on the Main
Menu.
Status and Control Menu
Menus and display screens that you can access from the Status and Control Menu enable you to:
•
Display and reset the current state and usage statistics of any node or port in the network
•
Change the operational state of individual ports
•
Clear individual virtual circuits or groups of virtual circuits
•
Display cluster controller station status and take stations online and offline
•
Display the status of electrical (EIA) input and output signals for any IAN-150 port in the
network
•
Display the current complement of modules installed at any node in the network.
For more information on status and control functions, see Chapter 3, “Basic Configuration and
Monitoring.”
Configuration Menu
Menus and display screens that you can access from the Configuration Menu enable you to
define the configuration of the network and set parameters that define how the network is
managed, including:
•
Local node identification
•
Memory usage and time-out
•
Date and time
•
Network addresses
•
Logical network names
•
Port and circuit configuration
•
Bridging, routing, packet switching, and frame switching configuration
•
Address translation/validation.
For more configuration information, see Chapter 3, “Basic Configuration and Monitoring.”
Utilities Menu
The Utilities Menu lets you perform single or multiple Ping tests, flush IP and/or IPX routing
tables, download the operating system or upload a configuration file, perform diagnostic
functions using the pseudoport feature, SNMP traps, and perform TELNET operations. For more
information on IAN-150 utilities, see Chapter 5, “Utilities and Diagnostics,” in this manual.
2-22
IAN150/IPP MT
6/30/97
Diagnostics Menu
The Diagnostics menu enables you to:
•
Test overall node hardware operation
•
Test hardware for specific port(s)
•
Test the effectiveness of the network routing.
For more IAN-150 diagnostic information, see Chapter 5, “Utilities and Diagnostics” in this
manual.
Time
The Time screen lets you set the time and date for the IAN-150 device. When you select Time
from the Main Menu, the system displays the following screen:
5. [T] Time
Time
UTC/GMT Delta
00:00:00
hh:mm:ss
+00:00
Day
SUNDAY
Date
JAN00-00
mmmdd-yy
Figure 2-10. IAN-150 Time Screen
Procedure 2-10. Setting Time and Date on the IAN-150
1. Using military time (24-hour clock), type the hours, minutes, and seconds in the appropriate
Time fields. Use the Tab or Enter key to move between fields. Press Enter.
2. Set the local offset to universal time. In the first (single character) field, press the spacebar
to select a positive (+) or negative (-) delta. Then enter the numerical hour and minute offset,
using the tab or enter key to move between fields. Press Enter.
3. From the Day field, press spacebar until you have selected the appropriate day. Press Enter.
4. Notice the mmmdd-yy format for the date. From the Month field, press spacebar until you
have selected the appropriate month. Type the day and year numerically in the appropriate
Date fields. Use the Tab or Enter key to move between fields. Press Enter.
5. Press the period < . > key to access the command line. From the command line prompt, type
W, then press Enter. The IAN-150 then displays the configured time and date.
The Time screen does not automatically display the correct time and date; instead it displays the
last time and date that was read. To see the current time and date, press < . > R to execute a Read
command; then press Enter.
IAN150/IPP MT
6/30/97
2-23
Help
When you access the IAN-150 by TELNET, the Help screen provides a summary of the
keyboard commands used for menu operation. When you select HELP from the Main Menu or
type H or HELP from the command line and press Enter, the system displays the following
screen:
6. [H] Help
KEY
=========
.
\ or ESC
/
'
SPACE
N or P
DELETE
TAB
RETURN
1 to 9
R or r
IP
MON
TERM
DEFAULT
L, H, D
ACTION
=======================================================
Escape to the Command menu for Reads, Writes, etc.
Return to the previous menu.
Refresh the current display.
Suppress all displays until a '/' is selected.
Select the next data field value in a select list.
Select the next or previous data field value in a select list.
Delete a character in a field.
Proceed to the next data field.
Return to the previous data field.
Confirm a command or data field.
Select an entry on a menu.
Reset to the first data field value in a select list.
Enter a new IP address to manage - IP xxx.xxx.xxx.xxx
Monitor a screen - MON xx (xx is # of seconds interval)
Set term type - TERM xxx - Valid values are DEC,
IBM 3101, IBM 3161, ADDS, WYSE, HZ, TTY
Set the current data screen back to the default values.
For Integer fields or select lists - select the Low, High,
or Default values.
Figure 2-11. IAN-150 Help Screen
The Help Screen commands and keystroke functions are described below.
NOTE:
2-24
Although indicated by upper case letters, the following commands
are not case sensitive.
. (Period Key)
Takes you to the command line where commands such as Read,
Write, and Reset are issued.
\ (Backslash) or ESC
Returns you to the previously selected screen or menu.
/ (Forward Slash)
Interrupts any data entry or parameter selection you are currently
performing, saves all of the new parameter information you have
entered, and returns you to the first entry of the current screen. If
you have previously selected the apostrophe key, the forward
slash reactivates the screen display.
‘ (Apostrophe)
Freezes your screen on the current display until you select the
forward slash < / > key.
SPACE (Spacebar)
Incrementally scrolls you through parameter values for those
fields having a predefined list of settings.
N or P
The N key performs the same function as the Spacebar in a data
field having a select list. The P key scrolls backwards through
the settings in a select list.
IAN150/IPP MT
6/30/97
DELETE (Delete Key)
Deletes the previous character in a parameter field after you have
typed data into that field.
TAB (Tab Key)
Saves your current field entry to the screen and moves your
cursor to the next data field.
- (Hyphen Key)
Moves the cursor to the previous data field on a screen.
RETURN (Enter Key)
Saves your current field entry to screen and moves your cursor to
the next data field.
1 to 9 (1...9)
Selects a submenu or menu option from a menu.
R or r
Resets a data field to the original value that was displayed before
you altered it.
IP
Used to change the node that is being monitored, configured or
managed via the user interface. The IP address is entered using
dotted decimal format: xxx.xxx.xxx.xxx
MON
Performs sequential Read commands and screen refreshes at
specified increments for any IAN-150 status screen. This
command lets you observe counter and screen information
changes in real time. The command syntax is MON or MON xx,
with xx being the number of seconds between Read commands.
The default monitor cycle time is 5 seconds.
TERM
Lets you select a specific terminal type. The command syntax is
TERM <TERM ID>, with the value <TERM ID>
corresponding to a particular terminal type. For a list of valid
terminal types, see Procedure 2−5 in this chapter.
DEFAULT
Resets the current screen data back to the default template values.
L, H, D
Sets preset parameter values (Low, High, and Default,
respectively) for integer fields or fields containing lists.
When you access Help from a web browser, the system displays information on procedures to
access various screens and menus.
Exit
When you select Exit from the Main Menu, the IAN-150 user interface session is terminated. If
the session was connected via the console port, an X.28 PAD> prompt appears. From this prompt
you can initiate a manual call to an X.121 resource and perform other PAD operations. If you
type h and press Enter, the following list of valid commands and functions is displayed.
IAN150/IPP MT
6/30/97
2-25
List of Extended Commands and their Functions
=============================================
A(TDT) address/resource Call X.121 address or named resource.
C(ALL) address/resource Call X.121 address or named resource.
CAM(P) ON/OFF
Turn camp facility on or off.
CL(EAR)
Clear the current call.
D(ATA)
Enter the data transfer state.
DI(RECTORY) S/P/N
Resource directory (Start, Previous, Next).
F(ACILITY) W,P,T,R,N
Enable selected CCITT call facilities.
L(OGOFF)
Log off of the X.28 user interface.
N(UI) x...x
Enter the NUI name and password (25 char).
P(ACKET) x
Set the packet size; range = 4 to 11.
PAR(AMETERS)
Display the current X.3 Parameters.
PR(OFILE) x
Set X.3 Parms to profile x; Reset if blank.
REV(ERSE) ON/OFF
Turn reverse charging facility on or off.
RP(AR)
Read the remote X.3 parameters.
RS(ET) xxx
Set remote X.3 parameters to profile x.
RSL ON/OFF
Turn reselect facility on or off.
S(ET) xx:yyy,...,xx:yyy Set parameter(s) x to value(s) y.
STA(TUS)
Display the complete X.28 status.
T(HROUGHPUT) x
Set the throughput class; range = 3 to 12.
U(SERDATA) x...x
Enter the call user data (22 char).
W(INDOW) xxx
Set the window size; range = 2 to 127.
Figure 2-12. IAN-150 X.28 Help Screen
To examine the status of the X.28 interface, type STA and press Enter. A sample X.28 status
display is shown in the figure below.
Ascom Timeplex Polaris System
Date: SEP23-96 Time: 13:01:41
============================================================================
DLCI-Port ==> 00001-000
Network ====> ALL
Name =======> SUPERUSER
Group ======> ALL
UI Access ==> SUPERUSER
User =======> ALL
============================================================================
Resource ===>
State ======> READY
Number =====> 63000
Cause ======> DTE ORIGIN
Netwk Dest => 00000-000(000)
Diag Code ==> 140
============================================================================
Facilities => xxx xxx xxx xxx xxx
Reverse ====> OFF
Reselect ===> OFF
Camp =======> OFF
============================================================================
Window =====>
5
User Data ==> SYSTEM
Modulo =====>
8
Timeout ====>
NO
Packet Size >
128
Throughput =>
9,600
============================================================================
Packets Out >
3
Packets In =>
12
Bytes Out ==>
5
Bytes In ===>
918
Duration ===>
0242:05:24
Call Usage =>
0%
Figure 2-13. Typical IAN-150 X.28 Status Display
For a user interface session, the X.28 status display shows the physical port number of the
connection, the user interface access level, and the virtual port number of the connection. For
descriptions of the parameters shown on this screen, see Configuring Async Circuit
Parameters in Chapter 2 of the Synchrony IAN-150/IPP Reference Manual.
2-26
IAN150/IPP MT
6/30/97
If no activity takes place at the PAD> prompt for approximately 60 seconds, the Autocall timer
will attempt to reestablish the connection to the user interface.
Entering Data
There are two ways to change parameter settings in the IAN-150 using the user interface and a
terminal keyboard:
•
Type the information into a blank field and press Enter.
•
Scroll through a set of available values by pressing spacebar, N, or P until the desired value
appears. Then press Enter to select that value.
If you try to make an illegal entry, the system will beep when you press the illegal key. The
cursor remains in the field, allowing you to enter another value or selection.
To move the cursor from one data field to another on a screen, press Tab or Enter. When the
cursor is at the last data field on the screen, press Tab or Enter to move the cursor back to the
first field. Both the Tab and Enter keys cause the current parameter value or data item to be
written or saved to the screen. For the IAN-150 to recognize the settings, you need to issue a
Write command and then cycle the appropriate port, or, for device parameters, power-cycle the
unit.
Entering Items Character-by-Character
Some data items are typed character-by-character. Alphanumeric characters can be typed, as
appropriate, when the cursor is in a character-by-character field.
To erase a typing mistake in a data field before pressing Enter for that item, press Backspace or
Delete to erase the characters, then retype. To correct a typing mistake after an item has been
entered and confirmed, press the slash < / > key to return the cursor to the top of the screen and
press Enter or Tab repeatedly to return to the desired item. You can also press the hyphen < - >
key to back up one field at a time until you reach the item that needs to be corrected.
Entering Data from Predetermined Choices
Some data entry items give you a list of predetermined values. To change a data item from one
predetermined value to another, press spacebar, N, or P. When the appropriate selection is
reached, press Enter to select the value.
Entering Preset High, Low, and Default Values for Data Items
Data entry fields have a high, low, and default value. To select the high value for a data field,
press H. To select the low value, press L. To select the default value for a data field, press D. To
reset all of the data fields to default template values, type DEFAULT from the command line
and press Enter.
IAN150/IPP MT
6/30/97
2-27
User Interface Commands
If you use a web browser to access the IAN-150 user interface, some of the user interface
operations are performed by selecting a command from a row of commands at the top of the user
interface screen, then clicking your mouse on Send Command. If you use TELNET access,
some of the IAN-150 user interface operations are performed by issuing commands from the
command line prompt. To access the command line, press the period < . > key from any field on
any menu or screen. Above the command line prompt you will see the commands that can be
used to manipulate the database information that corresponds to that screen. Other commands can
be issued from the command line prompt in addition to those that are listed. To issue a
command, type the command or the letter(s) that corresponds to the command, then press Enter.
All available user interface commands are listed and described below:
2-28
Abort [A]
Ends utilities and diagnostic test activities before the
IAN-150 has completed the requested number of cycles.
Build [B]
Allows you to add an entry in the Called Address
Translation (CAT) table.
Clear Circuit [CC]
Issues an X.25 Clear Request on the circuit specified.
Cycle [C]
Evacuates and then installs a selected port, using the
most recent configured parameters for that port. The
Cycle command is equivalent to issuing an Evacuation
command followed by an Install command.
Chassis Reset [CRS]
Applies only to IPP and is valid only on the Active
Master. Performs a reset on all boards in the chassis.
Delete [D]
Deletes a selected port’s configuration values from nonvolatile memory (NVM).
Evacuate [E]
Takes a selected port off-line and removes the driver.
(The configuration for the port is not removed.)
Install [I]
Reinstalls already configured parameters for a selected
port and brings that port on-line.
Main Menu [MAI]
Displays the Main menu.
Monitor [M]
This is a hidden command and does not display on the
screen above the command line. Performs a read of the
screen every N seconds until you press another key. The
command syntax is MON or MON xx, with xx being
the number of seconds between Read commands. The
default monitor cycle time is 5 seconds.
Read [R]
Refreshes the screen and shows you the currently
configured parameter values or status if there is an
existing configuration or status for the screen.
Read Next [N]
Refreshes the screen and shows you the next
configuration or statistic (lexigraphically).
Reload Cfg [RLC]
Reset node and load num config from flash memory
before startup
IAN150/IPP MT
6/30/97
Reload SW [RLS]
Reset node and load system software from compressed
flash memory before startup.
Reload SW & Cfg [RSC]
Reset node and load num config from flash and system
software from compressed flash before startup.
(Combination of RLC and RLS)
Reset [RES]
Resets counters on the selected screen to zero.
Restart [RST]
Resets the node.
Search [SE]
This is a hidden command and does not display on the
screen above the command line. It allows you to search
the IAN-150 to which you are connected for specified
parameters.
Setup Call [SC]
Sets up a call.
Shell [SH]
Accesses the VxWorks operating system. You must be
logged in at the highest access level [superuser] to
access VxWorks. To exit VxWorks, press Esc.
Station On (line) [STN]
For Bisync, Burroughs, and SDLC packet switching,
this command makes the specified station operable.
Station Off (line) [STF]
For Bisync, Burroughs, and SDLC packet switching,
this command makes the specified station inoperable.
Switch Active Master
[SAM]
Applies only to IPP and is valid only on a Master.
Switches the Active Master to Standby and makes the
Standby Master the Active Master.
Submit [SU]
Starts utilities and diagnostic test activities for a
designated number of cycles.
Translate [T]
For any address in the CAT screen, this command will
show you where that address will map to and what port
it will go to. If there is no entry in the CAT table, the
last three digits displayed designate the LCN or circuit,
the next two digits to the left designate the port, and the
remaining numbers designate the Node ID.
Validate [V]
Validates the CAT address.
Write [W]
Saves the new parameters in the section of non-volatile
RAM set aside for the configuration database.
Command Confirmation
When you enter a command from the command line, a confirmation message for that command
may appear on the screen. To confirm, press Enter. To reconsider or abort the command, press
backslash < \ >.
When a command is confirmed, the message [PROCESSING] appears in the middle of the
screen until the command has finished executing. If the screen displays an error message, it
means that the system cannot process the command. Press < \ > or Esc to return to the previous
menu.
IAN150/IPP MT
6/30/97
2-29
Procedure 2-11. Using the Read Command to Examine Current Settings
Using a Web Browser
Navigate through the menus by clicking the links that correspond to your menu choice. The
commands for the screen display at the top of the screen. Click the mouse on the small circle
next to the Read command, then click on Send Command. The current setting for the screen
will display. If there are no current settings for the screen, the system displays the message
[ERROR: DATA DOES NOT EXIST].
Using TELNET
1. To move to the screen where you want to see the current settings, navigate through the
menus by typing the indicated selection number or the appropriate hot-key initials.
2. Press period < . >. The commands for the screen appear at the bottom of the screen.
3. Type R (for Read) and press Enter. The current settings for the screen appear. If there are no
current settings for the screen, the message [ERROR:DATA DOES NOT EXIST]
appears. Press Esc or < \ > to redisplay the screen template.
Procedure 2-12. Using the Write Command to Enter or Change Settings
Using a Web Browser
1. Read the current settings (if any) by following Using the Read Command to Examine
Current Settings, for web browser.
2. Enter the new setting in each field by either selecting an option or typing a value.
3. Use the mouse to select Write, then click Send Command.
Using TELNET
1. Read the current settings (if any) by following Procedure 2-11.
2. Enter the new settings in each field by either selecting an option or typing a value.
4. Type W (for Write) and press Enter.
Procedure 2-13. Deleting Current Settings
Using a Web Browser
1. Read the current settings (if any) by following Using the Read Command to Examine
Current Settings, for web browser.
2. Verify the setting displayed are the ones you wish to delete.
3. Use the mouse to select Delete, then click Send Command.
Using TELNET
1. Read the current settings by following Procedure 2-11.
2. Verify that the settings displayed are the ones you wish to delete.
2-30
IAN150/IPP MT
6/30/97
4. Type D (for Delete) and press Enter.
5. When the message [CONFIRM DELETION] appears, press Enter to confirm, or press
< \ > to reconsider or abort the command.
NOTE:
If you delete a port configuration or overwrite an existing port
with a new port type, any circuits associated with the old port
type are also deleted. The effect is the same as if you had executed
a Clear Circuit command.
Procedure 2-14. Duplicating Configuration Settings
Using a Web Browser
1. Display the current settings (if any) for a node, port or circuit that has been correctly
configured by following Using the Read Command to Examine Current Settings, for
Web Browser.
2. Change only the keyfield or fields for the configuration screen. In the case of a port or
circuit configuration, the keyfield would be the port and/or circuit number. Do not change
other settings on the screen.
3. Use the mouse to select Write, then click Send Command.
Using TELNET
1. Follow Procedure 2-11 to display the current settings for a node, port or circuit that has been
correctly configured.
2. Change only the key field or fields for the configuration screen. (In the case of a port or
circuit configuration, the key field would be the port and/or circuit number.) Leave other
settings on the screen unchanged. To enter the parameter change(s), press Enter.
4. Type W (for Write) and press Enter.
Procedure 2-15. Activating Configuration Settings
Using a Web Browser
1. To activate configuration settings for ports and circuits, access the Port Status and Control
screen and select Cycle then Send Command.
2. To activate protocol or other device-wide configuration settings, power-cycle the IAN-150.
Using TELNET
1. To activate configuration settings for ports and circuits, access the Port Status and Control
screen (Screen 1.2.1) and execute a Cycle command by typing < . > C and pressing Enter.
2. To activate protocol or other device-wide configuration settings, power-cycle the IAN-150.
IAN150/IPP MT
6/30/97
2-31
Chapter
3
Basic Configuration
and Monitoring
NOTE:
Unless otherwise indicated, the information in this chapter
applies to the Synchrony ST-1000/ER-5 Independent Packet
Processor (IPP) module as well as to the Synchrony IAN-150. All
references to the IAN-150 apply to the IPP unless otherwise
noted.
There are three basic steps required to configure the IAN-150 for network operation:
1. Configure port handlers for each physical interface to be used.
2. If you have legacy-based traffic, configure circuits to connect the port handlers to each other
and to the external devices. Each port can support up to 999 circuits. Configure the
appropriate upper-layer protocol, if required by your application.
3. Activate the port and circuit configurations by issuing a Cycle command from the Port Status
and Control screen. Activate device-wide parameters by power-cycling the IAN-150.
In some cases you will also need to configure address translation parameters, and for some
applications you may need to configure network parameters. However, all applications supported
by the IAN-150 are implemented using the same basic configuration sequence.
NOTE:
The Synchrony IAN-150/IPP Reference Manual provides a
complete explanation of each protocol configuration. The
Synchrony IAN-150/IPP Planning Manual provides step-by-step
configuration procedures for various application scenarios.
Unit Default Configuration
As described in Chapter 1 of this manual, the IAN-150 system motherboard is equipped with up
to five physical interface connections (two LAN and three serial WAN), and one console port.
An optional expansion module is available that contains one of the following:
•
two additional serial WAN interface connections
•
one additional LAN interface connection (Token Ring or Ethernet)
•
one ISDN Basic Rate Interface connection
NOTE:
IAN150/IPP MT
6/30/97
This system motherboard description does not apply to IPP.
3-1
Chapter 3, Basic Configuration and Monitoring
The IAN-150 is shipped from the factory with a preconfigured set of default values to enable you
to use your system in a Frame Relay environment with no additional configuration. Most
applications, such as IP, SDLC/LLC, Async PAD (Packet Assembler/Disassembler) and others
can be started from the default setup with minimum additional configuration. The following
paragraphs summarize the IAN-150 default configuration.
Physical Setup
NOTE:
The following port information does not apply to IPP.
Port 3 Designated as WAN Port. Defaulted for Frame Relay Dedicated User Port (DUP).
Port 4 Designated as Access Port. Defaulted for TPAD/SDLC.
Port 5 Designated as Access Port. Defaulted for TPAD/3270 BSC.
Port Configuration
Port 0 - Console Port
Port 0 is preconfigured as an X.28 communication port to connect to a user interface device. A
default inactivity timer is set for 10 minutes. If during a user interface session there is no
keyboard input or command execution for 10 minutes, the session automatically terminates and
the IAN-150 title screen reappears. The timer is user-configurable and can be changed for the
entire device by modifying the Control Timeout parameter on the 2.1.1 screen, or it can be set for
a specific port using the Control Timer parameter on the 2.5.1.2 screen.
Port 1 - Token Ring (does not apply to IPP)
Port 1 is preconfigured for source-route transparent bridging with Spanning Tree turned OFF and
RIP disabled. If you configure IP for this port, RIP will be automatically enabled. Default values
for other parameters are as follows:
3-2
Configuration Screen
Token Ring Port
Number
2.2.2
Bridge Port
2.3.3
Spanning Tree
RIP Port
2.3.3
2.4.5.2
Parameter Name
Admin Status
MTU Size
Ring Speed
Early Token Release
Mac Address
Bridging Mode
LAN Identifier
Bridge Number
SR Frame Forward
SR-TB Translator
SR End Station
Broadcast Type
Port State
Operational Mode
Default Setting
DOWN
4472
16 Mbps
NO
(Assigned by factory)
SRT
4095
1
FORWARD
DISABLED
DISABLED
ARE
FORWARDING
ENABLED
IAN150/IPP MT
6/30/97
NOTE:
The Admin Status of Port 1 is defaulted to DOWN. If your
application includes Token Ring, you must set the Admin Status to
UP and cycle Port 1.
Port 2 - Ethernet (does not apply to IPP)
Port 2 is preconfigured for transparent bridging with Spanning Tree disabled and RIP enabled.
The Admin Status is set to UP. Default values for other parameters are as follows:
Ethernet Port
Number
2.2.1
Spanning Tree
RIP Port
2.3.3
2.4.5.2
Parameter Name
Port Type
Admin Status
Mac Address
Bridging Mode
Bridge Domain
Port State
Operational Mode
Advertise Static Routes
Broadcast Type
Hold-down Interval
Default Setting
Ethernet II
UP
(Assigned by factory)
TRANSPARENT
01
DISABLED
ENABLED
YES
LOCAL
60 seconds
Port 3 - Serial WAN (does not apply to IPP)
Port 3 is preconfigured as a physical DTE Frame Relay Dedicated User Port (DUP) with RIP
enabled, Admin Status = UP, and with a hard-coded LMI keep-alive timeout of 15 seconds.
Default values for specific configuration parameters are as follows:
Frame Relay Dedicated
User Port
IAN150/IPP MT
6/30/97
Number
2.6.4.1
Parameter Name
Admin Status
Default Setting
UP
IP Port
2.4.1.2
Data Rate
MTU Size
Clocking
LMI Polling Interval
LMI Protocol
Full Enquiry Interval
LMI Function
LMI Error Threshold
Inverse ARP
IP Address
RIP Port
2.4.5.2
Operational Mode
56,000 bps
1500
DTE
10 sec
ANSI T1-617-D
6
USER
3
ENABLED
192.168.10.10
(Factory assigned from
RFC 1597, Class C
subnet)
CAUTION: IP address
should be reconfigured
to match your network
environment.
ENABLED
3-3
Port 4 - Access Port/SDLC/TPAD (does not apply to IPP)
Port 4 is preconfigured for SDLC. Default values for specific configuration parameters are as
follows:
Number
Parameter Name
Default Setting
SDLC TPAD Port
2.5.6.1.1
Admin Status
DOWN
MTU Size
521
Data Rate
9600 bps
Clocking
DCE
Calls
OUTGOING
Function
SVC:AUTOCALL
Device Address
C1
XID Role Field
PASSTHRU
Port
24
Admin Status
DOWN
Bridge Domain
01
Host MAC Address
User-defined
MTU Size
521
Port
24
Calls
INCOMING
XID Role Field
PASSTHRU
Local/Remote SAP
04
Station MAC Adr
User-defined
Port
24
Port State
ENABLED
LAN Identifier
4094
Bridge Number
1
END STATION
Source Routing
ENABLED
SDLC TPAD Circuit
SDLC LLC Conversion
2.5.6.1.2
2.5.6.3.1
Port
SDLC LLC Conversion
2.5.6.3.2
Circuit
STAP
2.3.3
Bridge Port
NOTE:
3-4
2.3.3
The Admin Status of Port 4 is defaulted to DOWN. If your
application includes SDLC, you must set the Admin Status to UP
and cycle this port.
IAN150/IPP MT
6/30/97
Port 5 - Access Port/3270 BSC/TPAD (does not apply to IPP)
Port 5 is preconfigured for 3270 Bisync. Default values for specific configuration parameters are
as follows:
Number
Parameter Name
Default Setting
Bisync TPAD
2.5.2.1
Admin Status
DOWN
Buffer Count
008
MTU Size
128
Data Rate
9600 bps
Clocking
DCE
Max LCNs
10
Driver Type
EBCDIC
Calls
INCOMING
Controller Address
C1
Device Address
40
Bisync Circuit
2.5.2.3
Frame Relay LAP
A Frame Relay LAP Port is preconfigured on Port 11. Default values for specific configuration
parameters are as follows:
Number
Parameter Name
Default Setting
Node Parameter
2.1.1
Node ID
0999
Node Dispatch DLCI
0999
Trap Queue Depth
100
F/R Network ID
0999
Port
11
Admin Status
UP
Address DLCI
0999
MTU Size
1500
Max PVC Count
0100
Port
11
IP Address
192.168.1.1
(Factory assigned from
RFC 1597, Class C
subnet)
CAUTION:
Reconfigure IP address
to match your network
environment.
Operational Mode
ENABLED
Frame Relay LAP
IP Port
RIP Port
IAN150/IPP MT
6/30/97
2.6.6.1
2.4.1.2
2.4.5.2
3-5
Configuration Basics
The IAN-150 uses templates for each of its configuration screens. When you first access a screen,
the default template appears. If you have previously defined parameter values for this screen, you
must execute a Read command from the command line in order to view the values you have set.
To view these values, press the period < . > key to access the command line, then type R (Read)
and press Enter. The screen displays the last values that were saved to the configuration
database.
If you have not defined parameter values for a screen, enter data directly into the parameter fields
of the default template. Depending on the specific parameter field, you define a value by either
typing in the new value or by pressing N (Read Next) or spacebar to sequentially scroll through
the available values or settings. To view the high, low, or default values for integer fields or
fields that have selection lists, press H, L, or D respectively. To scroll backwards through the list
of available values, press P or Backspace. After you select a new value or setting, press Enter
to save the new value to the screen and move to the next field. To move to the next data field
without entering a new value in the current field, press Tab. To back up from the current data
field to the previous field, press < - >. To globally replace the screen values with those from the
default template, type DEF at the command line and press Enter. The IAN-150 displays the
default template for that screen, effectively replacing all previously configured parameters.
To save the new parameter values to the configuration database, issue a Write command by
pressing < . > W (for Write) and pressing Enter. Port-specific configuration parameters can be
activated by issuing a Cycle command for the applicable port. Device-specific configuration
parameters will take effect only after you power-cycle the IAN-150.
To issue a Cycle command, select the Port Status and Control screen (Screen 1.2.1) from the
Main Menu, or type SP or 12 from the command line of any menu or screen and press Enter. On
the Port Status and Control screen, enter the number of the port you wish to activate. Type < . >
C and press Enter to execute the cycle command. A confirmation prompt will appear. Press
Enter again. The port will be evacuated and then installed. When the process is complete, the
Port Status and Control screen will reappear.
To exit a configuration or status screen, press < \ > or Esc. To return to the Main Menu from
anywhere within the user interface, press < ~ >.
Configuring Node Parameters
In order to connect a serial WAN port to a Frame Relay or X.25 network environment, you must
configure a Node ID for Express Switching and a Dispatch DLCI for legacy applications.
Node parameters provide identification required to communicate over Frame Relay or X.25. To
access the Node Parameter Configuration screen from the Main Menu, follow the path:
2. Configuration
1. Node
1. Node Parameters
or type CNN or 211 from the command line of any menu or screen and press Enter. The system
displays the Node Parameter Configuration screen.
3-6
IAN150/IPP MT
6/30/97
2.1.1 [CNN] Node Parameter Configuration
Node ID
Trap Queue Depth
0001
0100
Node Dispatch DLCI
0001
FRAME RELAY
Network ID
LMI Spoof Control
0000
Disable
Route Manager Delay (sec)
LMI Spoof Delay (sec)
00600
00060
Call Pending (min)
Cleared Circuit Table
00001
016
Retransmit Delay (sec)
Default NUI
00010
Violation Delay (min)
00030
Control Timeout (min)
00010
10
20
Regulation Recovery (%)
Warning Recovery (%)
15
30
X25
X28
MEMORY
Regulation (%)
Warning (%)
Figure 3-1. Node Parameter Configuration Screen
The following paragraphs describe node configuration parameters. Corresponding MIB values,
where applicable, appear in brackets next to the parameter fields. If you have previously defined
parameters for this screen, you can execute a Read command to view the currently configured
settings. To activate node parameter configuration changes, you must execute a Write command
to save the new parameter values to the configuration database, then reboot the IAN-150. You
can reboot either by power-cycling the unit or by issuing the Restart (RST) command from the
command line on Node Status screen 1.1.1.
Node ID [polConfNodeNumber]
The internal Frame Relay network consists of a group of nodes that have Frame Relay switch
points enabled, interconnected by Frame Relay trunks and virtual trunks. The switch point is
enabled by setting a non-zero node ID that is usually assigned by the network. Valid values for
this parameter are from 1 to 1023. The default setting is 1.
NOTE:
Changing Node ID and Network ID requires a node reset.
Because these changes affect network topology, all the trunks
have to be reinitialized.
Node Dispatch DLCI [polConfNodeDispachdDLCI]
The Node Dispatch DLCI is a Data Link Connection Identifier assigned by the common carrier
that identifies a Frame Relay virtual circuit corresponding to the destination of the packet. This
value is contained in the Frame Relay header and is usually 10 bits long.
Trap Queue Depth [Local Parameter]
Determines the depth of the trap display database. The value in this field determines how many
SNMP traps will be held for display on the SNMP Trap Display screen (Screen 3.3). Valid
values range from 20 to 1023. The default is 100.
IAN150/IPP MT
6/30/97
3-7
FRAME RELAY
Network ID [polFRCFGNetworkId]
Contains a value assigned by the network administrator to identify the frame relay network in
which this node participates. Valid values range from 0 to 5535. The default setting is 0000.
NOTE:
Changing Node ID and Network ID requires a node reset.
Because these changes affect network topology, all the trunks
have to be reinitialized.
Route Manager Delay [polFRCFGRouteDelay]
The Route Manager controls the establishment and reestablishment of virtual circuit routes, and
implements the routing protocol. The routing protocol is a proprietary extension of the LMI
protocol and provides communication between route managers on adjacent nodes. The route
manager advertises whenever routing tables change at the node and periodically sends a full
status message of its routing table to all connected nodes.
This parameter specifies the interval in seconds between full status updates from the route
manager. Valid values are from 0 to 600 seconds. The default is 600, which results in the longest
interval between full status updates, and therefore the smallest increase in network overhead.
LMI Spoof Control [tI1frCfgSpoofEnable]
Controls the spoofing feature that delays notification of a PVC status change to the ‘down’ state.
For example, this prevents the temporary loss of a PVC until it is restored by bringing a backup
port online. Valid values: ENABLE and DISABLE. The default setting is DISABLE.
LMI Spoof Delay (sec) [tI1frCfgSpoofDelay]
Designates the number of seconds to wait until the internal system (and upper layer protocols)
are notified about the loss of a PVC. Valid values range from 0 to 999 seconds. The default
setting is 60.
X.25
Call Pending (min) [polConfNodeCallPend]
Determines the call request timeout, which is the number of minutes a call will wait in the DTE
WAITING state before it is forward cleared. Valid values are from 1 to 65535 minutes. The
default is 1 minute.
Retransmit Delay (sec) [polConfNodeRetrnsDly]
Determines the call response timeout, which is the number of seconds a call will wait for a
response before it is retransmitted. Valid values are from 1 to 65535 seconds. The default is 10
seconds.
Cleared Circuit Table [polConfNodeClearedCircuitEntries]
Each time a call is cleared, certain relevant information about that call is stored in the Cleared
Circuit Table. This field determines how many cleared circuits will be saved in the table. The
maximum number of table entries is 535; the default number is 16.
3-8
IAN150/IPP MT
6/30/97
Default NUI [polConfNodeDefaultNUI]
The Network User Identifier (NUI) is a user-defined string of up to 20 characters that provides
identification information to the network on a per-call basis for billing, security, or network
management purposes. The information may be provided by the DTE in the call request packet
and/or the call accept packet according to the default NUI Usage value.
X.28
Violation Delay (min) [polConfNodeWaitAccess]
Each time a user attempts to log in to the system and fails, a counter is set. After the third login
attempt, the user is locked out of the system for the period of time specified by this parameter.
Valid values are from 0 to 30000 minutes. The default value is 30 minutes.
Control Timeout (min) [polConfNodeWaitControl]
From the IAN-150 Main Menu, selecting Item 7 (EXIT) causes you to exit to the PAD prompt
immediately. However, if no action is performed by a user interface device for the number of
minutes specified by this parameter, the user interface session is terminated automatically and the
system returns to the IAN-150 title screen. The control timeout for inactivity can be from 1 to
30000 minutes. The default is 10 minutes.
MEMORY
Regulation (%) [polConfNodeMemReg]
Defines the point at which data packets being transmitted from a node will start being discarded
due to lack of memory capacity at the identified node. Memory Regulation is expressed as a
percent of available memory to total memory. For example, when the Memory Regulation field
is set at 10%, data packets will be discarded when the amount of available memory drops to 10%
of total memory. The default setting is 10%.
Regulation Recovery (%) [polConfNodeMemRegRec]
Defines the point at which data packets will stop being discarded. Memory Regulation Recovery
is expressed as an available percentage of total memory. For example, when Regulation
Recovery is set at 15%, discarding of data packets will cease when the amount of available
memory rises above 15% of the total memory. The default is 15%.
Warning (%) [polConfNodeMemWarn]
Defines the point at which a memory warning alarm is generated. Memory Warning is expressed
as a percentage. For example, when Warning is set at 30% and the amount of available memory
goes below 30%, a low memory warning alarm is generated. The default is 30%.
Warning Recovery (%) [polConfNodeMemWarnRec]
Defines the point at which a memory recovery warning alarm is generated. Memory Warning
Recovery is expressed as a percentage. For example, when Warning Recovery is set at 30%, and
the amount of available memory rises above 30%, a memory recovery warning alarm is
generated. The default is 30%.
IAN150/IPP MT
6/30/97
3-9
Configuring Port Parameters
Every protocol configured for use on the IAN-150 must be associated with a physical or virtual
port number. Configured ports must then be activated by issuing a Cycle command from the Port
Status and Control screen (Screen 1.2.1). Some limitations and restrictions apply when assigning
certain functions to virtual ports. For example, routing functions cannot be assigned to port
numbers higher than 24. The limitations and restrictions are summarized as follows:
IAN-150
IPP
•
Maximum port number for a physical port (num_phys):
7
9
•
Maximum port number for a virtual port (num_ports):
63
63
•
Maximum port number for routing (num_rt_ports):
24
24
•
Port number range for BRE bridging:
8-24
10-24
•
Preconfigured X.28 ports for TELNET sessions:
58-61
58-61
•
Pre-assigned virtual port for pseudoport operations:
62
62
•
Pre-assigned virtual port for user interface access:
63
63
When a port is installed either by restarting the IAN-150 or by issuing a Cycle command from
the Port Status and Control screen, the system checks the configuration that is being activated
and creates certain default records if they have not already been configured. For example, if
bridging is enabled on a port, the IAN-150:
•
verifies that there is a bridge record; if there is none, it creates a default bridge record.
•
verifies that there is a bridge domain; if there is none, it creates a default bridge domain.
•
sets the STAP state to FORWARDING if the port is configured for source routing.
If a port is configured for DLSw or QLLC2, the IAN-150:
3-10
•
forces the Bridging Mode parameter to SOURCE ROUTING
•
forces the SR Frame Forward parameter to FORWARD.
IAN150/IPP MT
6/30/97
Configuring Fast Path Parameters
Fast Path is a method used in the IAN-150 to increase performance by setting up dynamic cache
memory to handle the most frequently observed IP, IPX, BRE 2, and source route packets. The
Node Fast Path Configuration screen is used to configure this process. To access the Node Fast
Path Configuration screen from the Main Menu, follow the path:
2. Configuration
1. Node
2. Fast Path Parameters
or type CNF or 212 from the command line of any menu or screen and press Enter. The system
displays the Node Fast Path Configuration screen:
2.1.2 [CNF] Node Fast Path Configuration
Status
Cache Size
Aging (sec)
Aging Status
IP Fast Path
ENABLE
16
005
DISABLE
IPX Fast Path
ENABLE
16
005
DISABLE
BRE Fast Path
ENABLE
24
005
ENABLE
SR Fast Path
DISABLE
24
020
DISABLE
TB Fast Path
ENABLE
16
005
DISABLE
Figure 3-2. Node Fast Path Configuration Screen
Node Fast Path parameters are described in the following paragraphs. If you have previously
defined data for this screen, issue a Read command to view the currently configured settings. To
activate fast path configuration changes, issue a Write command to save the new parameter
values to the configuration database, then reboot the IAN-150. You can reboot either by powercycling the unit or by issuing the Restart (RST) command from command line of Node Status
screen 1.1.1.
Fast Path Status [Local Parameter]
Determines the operational status of each fast path cache table. If set to DISABLE, the
associated cache table is not operational and will not accept any entries. The default setting is
ENABLE for IP, IPX, and BRE fast path; the default is DISABLE for source route fast path.
Cache Size [Local Parameter]
Determines the maximum number of entries that will be saved in the cache table of each fast path
process. The range of this field is from 4 to 16 for IP and IPX fast path, and from 4 to 24 for
BRE and source route fast path. The default value for each cache table size is the maximum
possible value.
IAN150/IPP MT
6/30/97
3-11
Aging (sec) [Local Parameter]
Determines how long an unused fast path cache table entry remains in the table before it is
removed. The aging time can range from 1 to 300 seconds. Each time a table entry is accessed,
the aging timer for that entry is reset.
NOTE:
The aging timer operates only when the Aging Status parameter is
set to ENABLE.
Aging Status [Local Parameter]
Determines whether the Aging parameter is used to remove unused cache table entries. If set to
ENABLE, the aging time is used. If set to DISABLE, the aging time is ignored, and cache table
entries are removed on the basis of a Least Recently Used algorithm that is implemented when
the cache table becomes full and a new entry is received.
X.28 Basics
You use X.28 protocol to communicate with the IAN-150 user interface. The console port (Port
0) of the IAN-150 is preconfigured as an X.28 PAD. When it receives a login name and
password from a user interface device, it makes an X.25 call to virtual Port 63, which is
preconfigured as the user interface port.
Multiple user interface sessions can be established with a single IAN-150 by setting up multiple
TELNET sessions to virtual X.28 ports between Port 8 and Port 61, inclusive. For IPP, set up
multiple TELNET session to virtual X.28 ports between Port 10 and Port 61, inclusive. (Ports
58-61 are factory preconfigured specifically for TELNET sessions.) You must also have IP
running on at least one port of both IAN-150s.
The IAN-150 comes preconfigured with IP running on all physical ports (except Ports 6 and 7);
the IPP does not come with preconfigured physical ports. However, virtual ports 58-61 on both
the IAN-150 and the IPP are preconfigured for X.28. Therefore, the only user requirement is to
assign the appropriate IP address(es).
NOTE:
3-12
For a complete explanation of TELNET as a remote
communications utility, refer to Telnet Utility in Chapter 5,
“Utilities and Diagnostics,” in the Synchrony IAN-150/IPP
Maintenance and Troubleshooting Manual.
IAN150/IPP MT
6/30/97
Assigning an IP Address
IP addresses are identified in the IP Address field of the IP Port Configuration screen. To access
the IP Port Configuration screen from the Main Menu, follow the path:
2. Configuration
4. Routing
1. IP
2. Ports
or type CRIO or 2412 from the command line of any menu or screen and press Enter. The
system displays the IP Port Configuration screen:
2.4.1.2 [CRIO] IP Port Configuration
Port
001
ARP Reply Timeout (sec)
Encapsulation Type
Source Quench Sent
IP ADDRESS
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
010
STANDARD
000010
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
ARP Table Timeout (sec)
Proxy ARP
Logical Disconnected
SUBNET MASK
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
00300
DISABLED
FALSE
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
(0x00000000)
Figure 3-3. IP Port Configuration Screen
Each IAN-150 port that is configured to route IP packets must have at least one IP address. To
assign an IP address to a port, enter the port number in the Port field, then enter the IP address in
dotted decimal notation in the IP ADDRESS field. These two parameters are described in the
following paragraphs. The corresponding MIB values appear in brackets next to the parameter
names. If you have previously defined data for this screen, you must enter the port number and
execute a Read command to view the currently configured settings.
The remaining parameters on the IP Port Configuration screen are described in Chapter 11,
“TCP/IP Configuration,” of the Synchrony IAN-150/IPP Reference Manual.
IAN150/IPP MT
6/30/97
3-13
Port [polconfipPortNum]
The IAN-150 comes with a maximum of six physical ports and an expansion slot that can hold
up to two additional ports. The IPP comes with a maximum of 10 physical ports. The ports are
numbered as follows:
IAN-150
IPP
Port 0
Console port
Port 0
Console port
Port 1
Token Ring port
Port 1 - 8
WAN port
Port 2
Ethernet port
Port 9
PBUS port
Port 3-5
WAN port
Ports 10 - 63
Virtual ports
Ports 6 & 7
Expansion slot
Ports 8 - 63
Virtual ports
For information on limitations and restrictions about port number assignments, see Configuring
Port Parameters earlier in this chapter.
IP ADDRESS [polConfIPPortAddress1]
The first IP address listed is considered the primary IP address for this port and is required.
Additional IP addresses are considered to be secondary IP addresses. The IAN-150 allows you to
assign up to eight IP addresses per port, but no more than 20 IP addresses in total should be
configured for an IAN-150. Entries are made in dotted decimal notation and also displayed in
hexadecimal. Available values are any valid IP address. The default is 000.000.000.000
(0x00000000).
NOTE:
When an IP address is configured in an IAN-150, the subnet mask
is automatically entered by the system, based on the IP address
class. The subnet mask must be manually configured only when IP
host addresses are subnetted.
SUBNET MASK [polConfIPPortSubnetAddr1]
The subnet mask is a 32-bit pattern that is applied to the corresponding IP address to indicate
which bits are used for subnetting. A binary one at a given bit location in the mask indicates that
the bit location is part of the network or subnetwork address.
The subnet mask must always mask the network ID portion of the IP address. Therefore, for a
Class A address, the subnet mask always starts with 255. For a Class B address, the mask begins
with 255.255; for a Class C address, the mask begins with 255.255.255.
If the first four bits of the host ID portion of the IP address are used for subnetting, then these bit
locations must be filled with ones and the remaining locations filled with zeroes. For example:
11111111 11111111 11110000 00000000 (255.255.240.0).
The first mask entry listed is considered the primary subnet mask and is used to indicate which
bits of the corresponding primary IP address are used for subnetting. Additional masks are
secondary IP subnet masks and associated with corresponding secondary IP addresses. Subnet
masks are entered in dotted decimal notation and displayed in hexadecimal. The default is
000.000.000.000 (0x00000000).
3-14
IAN150/IPP MT
6/30/97
IP and TCP Minimum Configuration
The IAN-150 comes preconfigured for Transmission Control Protocol (TCP). However, a host
and network identification must be established. This is accomplished by configuring a port with
the appropriate IP address for the device. The procedure for accessing the IP Port Configuration
screen and an explanation of its relevant parameters is discussed above in X.28 Basics.
Monitoring Basics
The IAN-150 uses templates for each of its statistical displays and tables. When you first access a
table or status screen, the default template appears. To view current values, you must refresh the
screen by issuing either a Read or Read Next command from the command line. The screen
displays the statistics that applied when the command was executed. To view current values for
statistical displays, type < . > R (for Read) and press Enter. To view current values for tables,
type < . > N (for Read Next) and press Enter.
Each table can be sorted on the basis of key fields, which are usually located in the first line of
the table. To display information about a specific table entry, enter the appropriate identifying
data in the first line of the table after you have refreshed the screen, then execute a Read
command. The screen displays that table entry as the first table entry.
To automatically update and continuously display the most current statistics, execute a Monitor
command from the command line. The syntax for this command is MON x, where x represents
the number of seconds between screen updates. Press < . >, then type MON x and press Enter. If
you execute the Monitor command without entering the number of seconds between screen
updates, the default time interval of 5 seconds will apply. To end the Monitor function and
remain at the same screen, press any key. To end the Monitor function and exit the current
display, press < \ > or Esc.
Node Monitoring
You may monitor a node by observing the Node Status screen, which is accessed from the Status
and Control Menu. From the Main Menu, follow the path.
1. Node
1. Node Statistics
or type SNN or 111 from the command line of any menu or screen and press Enter. Figure 3-4
shows a typical node status monitoring screen.
IAN150/IPP MT
6/30/97
3-15
1.1.1 [SNN] Node Status
Description
Operational Since
Last Failure
Failure Reason
SEP23-96 17:48:20
SEP23-96 17:47:39
POWER FAILURE
MEMORY
NVM RAM
Buffer RAM
Flash
BYTES INSTALLED
122,368
5,516,560
5,120,000
CPU Utilization.
HARDWARE STATUS
Port Status
Port Install
Hardware Status
Hardware Install
BYTES AVAILABLE
102,024
4,511,456
Last 10 Secs
Last 1 Min
32
20
%
83
81
Last 5 Mins
10
31->0
00000000000000000000000000111111
00000000000000000000000000111111
00000000000000000000000000000000
00000000000000000000000000000000
Figure 3-4. Typical Node Status Monitoring Screen
Node status parameters are described in the following paragraphs. Corresponding MIB values,
where applicable, appear in brackets next to the parameter names. To view current values, issue a
Read command from the command line by typing < . > R and pressing Enter. The screen
displays the statistics that applied when the command was executed. To exit the display, press < \
> or Esc.
Description [polStatNodeSoftwareVersion]
Provides the following system software information: software version number, software builddate, target hardware platform, and the checksum value.
Operational Since [polStatNodeBootTime]
Contains the date (MMMDD-YY) and time (HH:MM:SS) that this device was last reset or
powered up.
Last Failure [polStatNodeLastFail]
Contains the date (MMMDD-YY) and time (HH:MM:SS) that this device last failed.
Failure Reason [polStatNodeFailCause]
Describes the reason for the last failure experienced by this device.
3-16
IAN150/IPP MT
6/30/97
MEMORY
NVM RAM [polStatNodeNvmTotal, polStatNodeNvmPercent]
The IAN-150 has 128 KB of non-volatile SRAM (NVM) available to store system configuration
information. The NVM is backed up by lithium batteries which can preserve the data for up to
seven years without external power. Some of the 128 KB of memory is reserved for internal
functions and is therefore not included in the numbers displayed on this screen. The BYTES
INSTALLED column displays the total amount of NVM that is available for allocation. The
BYTES AVAILABLE column displays the number of bytes currently unallocated. The %
column displays the percentage of the total available for allocation that is not currently allocated.
Buffer RAM [polStatNodeRamTotal, polStatNodeRamPercent]
The IAN-150 contains 2 MB of DRAM soldered to the motherboard. In addition, a 4, 8, or 16
MB DRAM SIMM can be installed in a SIMM socket, providing a total of 6, 10, or 16 MB of
buffer RAM. (A maximum of 16 MB of DRAM can be addressed by the CPU.) Some of this
memory is reserved for internal use and is therefore not included in the numbers displayed on
this screen. The BYTES INSTALLED column displays the total amount of DRAM that is
available for allocation. The BYTES AVAILABLE column displays the number of bytes that are
currently unallocated. The % column displays the percentage of the total available for allocation
that is not currently being used. The IPP has no base DRAM; a DRAM SIMM installed in a
SIMM socket provides 4, 8, or 16 MB of DRAM.
Flash [polStatNodeFlashTotal]
System software is stored in and executed from 5 MB of Flash memory. This field displays the
number of bytes of Flash RAM that is currently installed in the IAN-150.
CPU Utilization [polStatNodeCpuUtil10Sec, polStatNodeCpuUtil1Min,
polStatNodeCpuUtil5Min]
Indicates the percent of CPU bandwidth used over the specified time period of 10 seconds, 1
minute, or 5 minutes.
HARDWARE STATUS
Port Status [polStatNodePortStatus]
Indicates the results of the internal diagnostic test that has been run on the physical port. If the
internal diagnostic test has failed, the bit corresponding to the physical port number will be set to
0. If the diagnostic test has passed or has not been run, the bit will be set to 1. If the port is not
present in the IAN-150, the bit will be set to 0.
Port Install [polStatNodePortInstall]
Indicates the physical presence of ports in the IAN-150. Ports that are physically installed will be
indicated with the corresponding bit set to 1. Ports that are not physically present will be
indicated with the corresponding bit set to 0.
Hardware Status [polStatNodeHWStatus]
This parameter is not currently used in the IAN-150.
Hardware Install [polStatNodeHWInstall]
IAN150/IPP MT
6/30/97
3-17
Port Monitoring
After you configure the appropriate ports and activate them using the Cycle command, you can
check their status by issuing the Read and Read Next commands from the Port Status and
Control screen (Screen 1.2.1). To access the Port Status and Control screen, from the Main Enter,
follow the path:
2. Port
1. Port
After the system displays the screen, press < . > to access the command line, then type R and
press Enter. Figure 3-5 shows a typical port status display.
1.2.1 [SPP] Port Status and Control
Port
003
Port Type
Active Protocols
MTU Size
Speed
Admin State
Operational State
Operational Since
Address
X.25
Octets
Unicast Packets
Multicast Packets
Discards
Errors
Unknown Protos
Queue Length
128
9600
UP
UP
JUL08-96 12:54:19
00:00:00:00:00:00 (C)
IN
0
0
0
0
0
0
00:00:00:00:00:00 (N)
OUT
0
0
0
0
0
Line Util %:
Last Sec
15 Secs
IN
0
0
OUT
0
0
0
Figure 3-5. Typical Port Status Display
The top portion of the display shows the port type and active protocols in use on the port, the
MTU size and data rate for the port, the operational state of the port and the date and time when
the operational state changed to the current condition, and the canonical and non-canonical MAC
addresses for the port. The bottom portion of the display gives the following data transmission
information as of the time the Read command was executed. To receive automatic updates of
this information, access the command line, type MON followed by a space and the number of
seconds you want the screen to pause between updates; then press Enter. The default time
interval is 5 seconds. To stop the automatic updates, press < . >. To exit from this screen, press
< \ > or Esc.
Octets IN/OUT [IfInOctets] [IfOutOctets]
The total number of bytes received (IN) and transmitted (OUT) by this port, including Frame
Check Sequence (FCS) bytes.
Unicast Packets IN/OUT [IfInUcastPkts] [IfOutUcastPkts]
The number of packets with a unicast address that have been received from and transmitted to a
higher layer interface by this port.
3-18
IAN150/IPP MT
6/30/97
Multicast Packets IN/OUT [IfInNucastPkts] [IfOutNucastPkts]
The number of packets with a multicast address that were received and transmitted by this port.
Discards IN/OUT [IfInDiscards] [IfOutDiscards]
The number of received frames discarded, and the number of frames to be sent that have been
dropped due to internal conditions (such as lack of buffering).
Errors IN/OUT [IfInErrors] [IfOutErrors]
The number of invalid frames received, and the number of transmissions that failed because they
were considered invalid by the receiver. This number has no relationship to the number of REJ or
RNR frames sent or received.
Unknown Protos IN/OUT [IfInUnknownProtos]
The number of packets received by this port and discarded because they were unknown to the
protocol in use.
Queue Length [IfOutQLen]
The number of packets in the output packet queue awaiting transmission.
Line Util %
Indicates the percent of the data rate achieved, not including retransmissions. IN represents the
total number of frames and data bytes transmitted across the link. OUT represents the total
number of frames and data bytes received at the port error free.
Last Sec [polStatComnIfLineUtilInLastSecs]
[polStatComnIfLineUtilOutLastSecs]
Indicates the Line Util % achieved during the last second of communication across the link.
15 Secs [polStatComnIfLineUtilInLast15Secs]
[polStatComnIfLineUtilOutLast15Secs]
Indicates the Line Util % achieved during the last 15 second period of communication across the
link.
Hardware Monitoring
The IAN-150 provides two screens to verify and monitor the physical ports that are installed in
the unit that is being managed by the user interface.
Hardware Type Display
As previously described, the IAN-150 may be purchased with a variety of different hardware
configurations. The Hardware Type Display shows the type of hardware interface for each
installed physical port. To access this screen from the Main Menu, follow the path:
1. Node
2. Node Hardware
or type SNH or 112 from the command line of any menu or screen and press Enter. Figure 3-6
shows a typical Hardware Status screen.
IAN150/IPP MT
6/30/97
3-19
1.1.2 [SNH] Hardware Type Display
Node Type
IAN-150
Port
Port
Port
Port
Port
Port
Port
Port
TOKEN RING
10BASE-T
V.35 DTE
V.28 DTE
V.11 (268)
ABSENT
ABSENT
ABSENT
1
2
3
4
5
6
7
8
Board Revision
Serial Number
ROM version
116231-6:A2-4
1406331
Figure 3-6. Typical Hardware Type Display
Hardware Type parameters are described in the following paragraphs. Corresponding MIB
values, where applicable, appear in brackets next to the parameter names. The default template
for this screen shows a Node Type of UNKNOWN and displays ABSENT for each port. To view
current data, issue a Read command from the command line by typing < . > R and pressing
Enter. To exit the display, press < \ > or Esc.
Node Type [polStatBordNodetype]
Identifies the type of device being monitored in this user interface session. In the screen shown in
figure 3-6, the device is an IAN-150.
Board Revision [Local Parameter]
Displays the hardware part number and revision level of the system motherboard. For example,
using the board revision number, 116231-6:A2-4, in Figure 3-6:
•
116231-6 indicates the motherboard part number.
•
A2 indicates the printed circuit board (PCB) revision level.
•
-4 indicates the build level of the motherboard.
IAN-150 base units are numbered as shown below.
3-20
Model Name
Part Number
Description
IAN-150-001
IAN-150-002
IAN-150-003
IAN-150-004
IAN-150-005
IAN-150-006
116107-1
116107-2
116107-8
116107-4
116107-5
116107-6
IAN-150-011
IAN-150-012
IAN-150-013
IAN-150-014
IAN-150-015
IAN-150-016
116107-11
116107-12
116107-13
116107-14
116107-15
116107-16
1 Ethernet, 1 Serial Port
1 Token Ring, 1 Serial Port
3 Serial Ports
1 Ethernet, 3 Serial Ports
1 Token Ring, 3 Serial Ports
1 Ethernet, 1 Token Ring,
3 Serial Ports
1 Ethernet, 1 Serial Port
1 Token Ring, 1 Serial Port
3 Serial Ports
1 Ethernet, 3 Serial Ports
1 Token Ring, 3 Serial Ports
1 Ethernet, 1 Token Ring,
3 Serial Ports
Motherboard
Part No.
BASE No.
116231-1
116231-2
116231-8
116231-4
116231-5
116231-6
BASE 1
BASE 2
BASE 8
BASE 4
BASE 5
BASE 6
116231-11
116231-12
116231-13
116231-14
116231-15
116231-16
BASE 11
BASE 12
BASE 13
BASE 14
BASE 15
BASE 16
IAN150/IPP MT
6/30/97
NOTE:
Base unit models IAN-150-001, IAN-150-002, IAN-150-003, IAN150-004, IAN-150-005, and IAN-150-006 are interoperable with
expansion modules IAN-EXP-01, IAN-EXP-02, IAN-EXP-03, and
IAN-EXP-04. Base unit models IAN-150-011, IAN-150-012, IAN150-013, IAN-150-014, IAN-150-015, and IAN-150-016 are
interoperable with expansion modules IAN-EXP-11, IAN-EXP-12,
IAN-EXP-13, and IAN-EXP-14.
Serial Number [Local Parameter]
Displays the serial number of the system motherboard.
ROM version [polStatBordROMVersion]
Displays the version number of the Read Only Memory (ROM).
Port [polStatBordPort1Type] - [polStatBordPort8Type]
There are 8 port type fields. Each field identifies the physical configuration for that port. For
serial WAN ports, the status display identifies the WAN Personality Module (WPM) that is
installed for that port. The WPM is a small plug-in card that configures a serial DB25 port for
MIL-STD-188-114A, V.11, V.28 (DCE or DTE), V.35, or X.21.
NOTE:
0 is always the console port, for both the IAN-150 and the IPP.
9 is always the PIPE port (only applies to IPP).
EIA Modem Lead Status
The EIA Modem Lead Status screen displays the following information on each port installed in
the IAN-150:
•
Port type, interface status and port state
•
The type and number of the physical interface for each port
•
Status of electrical (EIA) input and output signals at the port.
To access the EIA Modem Lead Status screen from the Main Menu, follow the path:
2. Port
4. EIA Modem Leads
or type SPM or 124 from the command line of any menu or screen and press Enter. Figure 3-7
shows a typical EIA Modem Lead Status screen for port 0.
IAN150/IPP MT
6/30/97
3-21
1.2.4 [SPM] EIA Modem Lead Display
Port
000
Port Type
Level 1 Port
Device State
LIU Type
X28
DCE
ON LINE
V.28 DCE
INPUT SIGNALS
DSR
CTS
DCD
TI
RING
OFF
OFF
OFF
OFF
OFF
OUTPUT SIGNALS
DTR
RTS
LLB/OT1/SRS
RLB/OT2/DIAG2
Baud Rate
OFF
OFF
OFF
OFF
9,600
Figure 3-7. Typical EIA Modem Lead Display Screen
EIA Modem Lead parameters are described in the following paragraphs. Corresponding MIB
values, where applicable, appear in brackets next to the parameter names. To view current values
for a specific port, enter the port number, then issue a Read command from the command line by
typing < . > R and pressing Enter. The screen displays the statistics that applied when the
command was executed. To exit the display, press < \ > or Esc.
Port [polStatEiaMIntfNum]
This field identifies the physical port you are monitoring.
Port Type [polStatEiaMIntfType]
Displays one of the following port types for the port identified in the Port field:
UNDEFINED
INTERNAL
X25
X28
BOP
SDLC HPAD
SDLC TPAD
COP
FRAME RELAY
ISDN
BSC HPAD
BSC TPAD
QLLC2 HOST
BPS HPAD
BPS TPAD
PSEUDOPORT
VIRTUAL X28
ETHERNET II
IEEE 802.3
TOKEN RING
LAPB/HDLC
BRIDGE DOM
LAP
BRE
DLSW
DIAGNOSTIC
LLC
NETWORK
IPX
LMI
Level 1 Port [polStatEiaMIntfL1Cfg]
Indicates the Layer 1 interface type chosen for the identified port. Possible interfaces are DCE,
DTE, and BAL.
Device State [polStatEiaMDevState]
Indicates the operational state of the identified port. Possible device states are OFF LINE,
DISCONNECT, and ON LINE.
3-22
IAN150/IPP MT
6/30/97
LIU Type [polStatEiaMLiuType]
Indicates the type of physical interface installed in the selected port. If a port is not installed, or if
a WPM is not installed in a serial WAN port, ABSENT will appear in this field. The physical
interfaces supported in the IAN-150 are:
V.28 DTE
TOKEN RING
V.28 DCE
10BASE-T
V.11 (268)
ISDN BRI
V.35
X.21
MIL-STD-188-114A
INPUT SIGNALS
DSR [polStatEiaMDsr]
Indicates the state of the Data Set Ready signal.
CTS [polStatEiaMCts]
Indicates the state of the Clear-To-Send signal.
DCD [polStatEiaMDcd]
Indicates the state of the Data Carrier Detect signal.
TI [polStatEiaMT1]
Indicates the state of the Test Indicator signal.
RING [polStatEiaMRng]
Indicates the state of the Ring Indicator signal.
OUTPUT SIGNALS
DTR [polStatEiaMDtr]
Indicates the state of the Data Terminal Ready signal.
RTS [polStatEiaMRts]
Indicates the state of the Request-To-Send signal.
LLB/OT1/SRS [polStatEiaMOt1]
Indicates the state of the local loopback using Output 1 (OT1) signal.
RLB/OT2/DIAG2 [polStatEiaMOt2]
Indicates the state of the remote loopback using Output 2 (OT2) signal.
Baud Rate [polStatEiaMBaud]
The number of signal changes per second being transmitted through a typical voice telephone
channel. For example, a 9600 baud modem refers to a modem that transmits 2400 signals per
second, with each signal containing 4 bits (2400 x 4 = 9000).
IAN150/IPP MT
6/30/97
3-23
SNMP Trap Monitoring
The console port on the IAN-150 can act as a network manager by displaying traps in a userreadable form on an attached terminal or PC. The IAN-150’s local traps are sent to the SNMP
Trap Display after being filtered. Any other node in the network can also specify a destination IP
address on this node and its traps will also be displayed. To access this screen from the Main
Menu, follow the path:
3. Utilities
3. SNMP Trap Display
or enter US or 33 from the command line of any menu or screen and press Enter. Figure 3-8
shows a sample SNMP Trap Display.
3.3 [US] SNMP Trap Display
0
10
153
153
10
10
10
10
3
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:45
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
SYSTM
X28
SYSTM
SYSTM
X28
X28
X28
X28
X28
Node
Port
Port
Port
Port
Port
Port
Port
Port
Recovered Database initialized
0 Installing Task
1 Invalid Ind. MAC Address
47 Installing Task
48 Installing Task
49 Installing Task
50 Installing Task
0 Link Recovery
Figure 3-8. Sample SNMP Trap Display
Each trap contains an index number which is used for filtering purposes, the date and time of the
trap, the IP address of the node issuing the trap, and a description of the event that caused the
trap. Traps having an IP address of 000.000.000.000 are those that were issued by the local node.
The number of traps held for display can be configured between 20 and 1023 by adjusting the
Trap Queue Depth parameter on the Node Parameter Configuration screen (2.1.1). The default
number of traps stored is 100. When the number of traps generated exceeds the Trap Queue
Depth value, the earliest traps generated will be discarded.
NOTE:
Each SNMP trap displayed on screen 3.3 requires 480 bytes of
memory. This should be considered when configuring the
parameters for Trap Queue Depth on the Node Parameter
Configuration Screen 2.1.1.
The traps that are stored will scroll continuously until they have all been displayed. To pause the
screen, press Ctrl-s; to resume scrolling, press Ctrl-q. To exit the display, press < \ > or Esc.
3-24
IAN150/IPP MT
6/30/97
For additional information, refer to the following chapters in this manual:
•
For information on Trap Display, refer to SNMP Trap Display in Chapter 5.
•
For a complete list of IAN-150 traps and their descriptions, see Appendix C, “Trap
Messages.”
•
For information on how to configure the IAN-150 to filter certain traps or display traps from
another node, see Trap Output Configuration in Chapter 4.
IAN150/IPP MT
6/30/97
3-25
Chapter
4
Network Management
NOTE:
Processor (IPP) module well as to the Synchrony IAN-150. All
noted.
The IAN-150 supports Simple Network Management Protocol (SNMP) and can be managed
remotely in four different ways using SNMP functions:
1. You can connect an asynchronous terminal (or PC running a terminal emulation program
such as TALK) to the console port of a local IAN-150 and use the IP command to manage a
remote IAN-150.
2. You can use TELNET to access the user interface of a remote IAN-150 from a local PC or
other TELNET client, then manage the remote IAN-150 as if you were locally connected to
the console port.
3. You can use a network management station running an SNMP network manager such as the
Ascom Timeplex Element Management System (EMS 200, Release 3.0 or later).
4. You can use a web browser to access the user interface of a remote IAN-150 from a local PC,
then manage the remote IAN-150 as if you were locally connected to the console port.
This chapter describes how to configure the IAN-150 to communicate with a remote network
management station.
NOTE:
IAN150/IPP MT
6/30/97
TELNET is described in Chapter 5, “Utilities and Diagnostics.”
4-1
Chapter 4, Network Management
IP Command
The IP command is a user interface command that provides remote access to any other IAN-150
in the IP network, subject to the limitations described in Element Management System
Configuration later in this chapter. Using SNMP protocol, the IP command allows you to make
configuration changes and monitor ports on one unit from a remote location.
From any user interface menu or screen, type < . > to access the command line. Then type IP
followed by the IP address of the remote IAN-150 you wish to access. This will set up your IAN150 to send subsequent requests to the remote IP address. All subsequent tasks initiated at the
local IAN-150 will be acted upon by the remote IAN-150. To reset this function and free the
remote unit from the control of the local unit, type IP from the command line and press Enter.
Simple Network Management Protocol (SNMP)
SNMP is a TCP/IP application-layer protocol designed to monitor and control network elements.
In the IAN-150, SNMP runs over User Datagram Protocol (UDP), which in turn runs over IP. To
understand how SNMP is used to manage the IAN-150, it is important to understand the
following concepts:
4-2
•
Network Manager: For SNMP, the network manager is a software program that resides on a
network management station. The manager can query agents, process responses, and set
variables. An example of a network manager is the Ascom Timeplex EMS 200 program.
•
Agent: An agent is a software program that resides in any device and can communicate with
the network manager. The agent maintains a store of management data and responds to
requests from the network manager. The IAN-150 includes an SNMP agent in its system
software.
•
Management Information Base (MIB): The MIB is a database of objects that corresponds
to variables in agents in the internetwork. Typical variables include values in counters, states
of software flags, and threshold values. Both the network manager and the agent have a MIB,
but typically the MIB in the agent is limited to objects that apply only to that agent.
IAN150/IPP MT
6/30/97
SNMP Configuration
The SNMP configuration screens are accessed from the Network Management Configuration
Menu. To access this menu from the Main Menu, follow the path:
2. Configuration
1. Node
5. Network Management Parameters
or type CNM or 215 from the command line of any menu or screen and press Enter. The system
displays the following menu:
2.1.5 [CNM] Network Management Configuration
1. System Group
2. Community Name Configuration
3. Trap Output Configuration
4. Element Management System Configuration
5. Trap Filtering
Figure 4-1. Network Management Configuration Screen
SNMP Configuration Tips
The IAN-150 uses templates for each of its configuration screens.When you first access a
configuration screen, the system displays a default template. If you have previously defined
parameter values for this screen, issue a Read command from the command line to view the
values you have set. To issue a Read command, press < . > to access the command line, then
type R (Read) and press Enter. The screen then displays the last configured values that were
saved to the configuration database.
If you have not defined parameter values for a screen, enter data directly into the parameter fields
of the default template. Depending on the specific parameter field, you define a value by either
typing in the new value or by pressing N (Read Next) or spacebar to sequentially scroll through
the available values or settings. To view the high, low, or default values for integer fields or
fields having selection lists, press H, L, or D respectively. To scroll backwards through the list of
available values, press P (Previous) or Backspace. After you select a new value or setting, press
Enter to save the new value to the screen and move to the next field. To move to the next data
field without entering a new value in the current field, press Tab. To back up from the current
data field to the previous field, press < - >. To globally replace the screen values with those from
the default template, type DEF at the command line and press Enter. The IAN-150 displays the
default template for that screen, effectively replacing all previously configured parameters.
IAN150/IPP MT
6/30/97
4-3
To save new parameter values to the configuration database, you must issue a Write command
by typing < . > W and pressing Enter. Network management parameters—except Trap Output
and Trap Filtering parameters—take effect when you power-cycle the IAN-150. Note that
community names do not require a power cycle.
To exit a configuration screen, press < \ > or Esc. To return to the Main Menu from anywhere
within the user interface, press < ~ >.
System Group Configuration
System Group parameters refer to those device parameters that uniquely identify this IAN-150.
From the Main Menu, follow the path:
2. Configuration
1. Node
1. System Group
or type CNMS or 2151 from the command line of any menu or screen and press Enter. The
system displays the following screen:
2.1.5.1 [CNMS] System Group Configuration
Description
Contact
Name
Location
System Up Time
0000:00:00
Services Available
004
System Object ID
.1
.3
.6
.1
.0
.0
.0 .0
Figure 4-2. System Group Configuration Screen
The System Group Configuration parameters are described in the following paragraphs.
Corresponding MIB values, where applicable, appear in brackets next to the parameter fields.
Before you configure the parameters on this screen, issue a Read command to view the factoryconfigured read-only settings.
Description [SysDescr]
A read-only field that provides the default text description of the network device, including the
type and version of the operating system software.
Contact [SysContact]
Displays the name and telephone number of the locally assigned person to contact regarding the
device identified in the name field.
4-4
IAN150/IPP MT
6/30/97
Name [SysName]
Displays the assigned name for this managed IAN-150. By convention this is a qualified domain
name.
Location [SysLocation]
Displays the physical location of the IAN-150 identified in the name field.
System Up Time [SysUpTime]
Displays the length of time that the system has been running since it was last reset.
Services Available [SysServices]
A read-only field that numerically represents the layer of service offered by the device. A list of
valid values, associated layers of services, and examples of providing devices is shown below:
Value
001
002
003
004
007
Layer of Service
physical layer
logical link layer
network layer
transport layer
application layer
Examples
repeaters
bridges
IP gateway
IP hosts
mail relays
The IAN-150 supports SNMP network management protocol, which uses the TCP/IP protocol
suite. Layers 5 (Session) and 6 (Presentation) do not exist in the TCP/IP model.
Object ID [SysObjectId]
A read-only field that numerically identifies the nature of the entity being managed. This field
also contains the vendor’s identification of the network management subsystem contained in that
entity. The value shown below identifies the Synchrony IAN-150.
-> .1
IAN150/IPP MT
6/30/97
iso
-> .3
organization
-> .6 department of defense [dod]
-> .1 internet
-> .4 private
-> .1 enterprises
-> .16 timeplex (Ascom Timeplex)
-> .200 IAN-150
4-5
Community Names Configuration
Community Names parameters refer to security passwords that are used to receive (get) and send
(set) network communications. From the Main Menu, follow the path:
2. Configuration
1. Node
2. Community Names
or enter CNMC or 2152 from the command line of any menu or screen and press Enter. The
2.1.5.1 [CNMC] Community Name Configuration
Community Name (get)
Community Name (set)
Figure 4-3. Community Name Configuration Screen
The Community Name Configuration parameters are described in the following paragraphs.
Corresponding MIB values, where applicable, appear in brackets next to the parameter fields.
Community Name (get) [polSystemGetCommunityString]
Identifies the password assigned for incoming (read) network management packets.
Community Name (set) [polSystemSetCommunityString]
Identifies the password assigned for outgoing (read/write) network management packets.
4-6
IAN150/IPP MT
6/30/97
Trap Output Configuration
The Trap Output Configuration screen allows you to designate up to four IP addresses to receive
traps issued by this IAN-150. From the Main Menu, follow the path:
2. Configuration
1. Node
5. Network Managment Parameters
3. Trap Output Configuration
or enter CNMT or 2153 from the command line of any menu or screen and press Enter. The
2.1.5.3 [CMT] Trap Output Configuration
Trap Destination Address [1]
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
Trap Filter - Severity Level
NORMAL
Figure 4-4. Trap Output Configuration Screen
The Trap Output Configuration parameters are described in the following paragraphs.
Corresponding MIB values, where applicable, appear in brackets next to the parameter fields. If
you have previously defined IP addresses on this screen, issue a Read command to view the
currently configured settings.
Trap Destination Addresses (1-4)
[polTrapDestIpAddr1] - [polTrapDestIpAddr4]
Identifies the IP addresses of up to four network management site locations to which trap
messages from this IAN-150 will be sent.
Trap Filter - Severity Level [polTrapSeverityLevel]
Identifies the severity of traps that this node will generate. To change the severity level, press
spacebar to scroll through the available settings. Press Enter to select a setting. The valid
settings for this parameter are:
NORMAL
MINOR
MAJOR
CRITICAL
DISABLED
All levels of traps will be generated.
Normal traps are filtered; Minor, Major, and Critical traps are generated.
Normal and Minor traps are filtered; Major and Critical traps are generated.
Critical traps are generated; all other traps are filtered.
The node will not generate any traps.
In addition to filtering by severity level, traps can be filtered by index number range using
Screen 2.15.5 (Refer to Trap Filtering, below). Trap index numbers are included in the trap list
given in Appendix C of this manual.
IAN150/IPP MT
6/30/97
4-7
Element Management System Configuration
2. Configuration
1. Node
4. Element Management System Configuration
or type CNME or 2154 from the command line of any menu or screen and press Enter. The
2.1.5.4[CNME] Element Management System Configuration
EMS Well Known IP Address [1]
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
Figure 4-5. Element Management System Configuration Screen
If you have previously defined IP addresses on this screen, issue a Read command to view the
currently configured settings.
EMS Well Known IP Address [1] − EMS Well Known IP Address [4]
[polEmsIpAddr1] - [polEmsIpAddr4]
Designates by IP address which network management stations will be given access to manage
this IAN-150. Up to 4 nodes may be identified. If all four IP addresses remain set to
000.000.000.000, then any IAN-150 or SNMP workstation running EMS 200 can manage this
IAN-150. If one or more IP addresses are configured, then the ONLY SNMP workstaions that
can manage this IAN-150 are those whose IP addresses are listed here.
4-8
NOTE:
An EMS 200 platform can log into a physical or virtual X.28 port
using a login name of SNMP and, for the password, the current
Set Community Name. When accessing a remote IAN-150 in this
way, full superuser access will be granted.
NOTE:
The IPP only has four such addresses; the fifth is ignored.
IAN150/IPP MT
6/30/97
Trap Filtering
The Trap Filtering screen allows you to specify a range of traps by index number that you wish
to filter from the trap display. To access this screen from the Main Menu, follow the path:
2. Configuration
1. Node
5. Trap Filtering
or enter CNMF or 2155 from the command line of any menu or screen and press Enter. The
2.1.5.5 [CMF] Trap Filtering
Trap Range
000-000
Block Trap
NO
Block Display Trap..NO
Figure 4-6. Trap Filtering Screen
The Trap Filtering parameters are described in the following paragraphs. Corresponding MIB
values, where applicable, appear in brackets next to the parameter fields. If you have previously
defined data for this screen, issue a Read command to view the currently configured settings.
There are two categories of traps: Generic and Specific. Generic traps are accepted and supported
throughout the data communications industry. Specific traps are developed by manufacturers for
a specific device. The specific traps that have been developed for the IAN-150 are listed in
Appendix C of this manual.
Trap Range [polConfTrapFiltNumLow] - [polConfTrapFiltNumHi]
Identifies the range of traps that you want the IAN-150 to filter.
Block Trap [polConfTrapFiltBlock]
Designates whether traps will be blocked. The default value of this field is NO, which indicates
the range of traps identified above will be operational.
Block Display Trap [polConfTrapDisplayBlock]
Determines whether trap will be displayed on screen number 3.3 SNMP Tray Display. The
default value of this field is NO, which indicates the traps will not be displayed on screen 3.3.
IAN150/IPP MT
6/30/97
4-9
SNMP Monitoring
The IAN-150 supports SNMP protocol which enables communication with host network
management software. The IAN-150 sends a transmission to the host with a pre-determined
response expected. If an error occurs, a trap is generated and displayed on the SNMP Trap
Display screen.
The IAN-150’s local traps are sent to the SNMP Trap Display after being filtered. Any other
node in the network can also specify a destination IP address on this node and its traps will also
be displayed. To access this screen from the Main Menu, follow the path:
3. Utilities
or enter US or 33 from the command line of any menu or screen and press Enter. The system
displays the SNMP Trap Display. A sample SNMP Trap Display is shown below:
0
10
153
153
10
10
10
10
3
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:45
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
SYSTM
X28
SYSTM
SYSTM
X28
X28
X28
X28
X28
Node
Port
Port
Port
Port
Port
Port
Port
Port
0 Installing Task
47 Installing Task
48 Installing Task
49 Installing Task
50 Installing Task
0 Link Recovery
Each trap contains an index number which is used for filtering, the date and time of the trap, the
IP address of the node issuing the trap, and a description of the event that caused the trap. Traps
having an IP address of 000.000.000.000 are those that were issued by the local node.
The number of traps held for display can be configured between 20 and 1023 by adjusting the
number of traps stored is 20. When the number of traps generated exceeds the Trap Queue Depth
value, the earliest traps generated will be discarded.
The traps that are stored will scroll continuously until they have all been displayed. To pause the
screen, press Ctrl-s; to resume scrolling, press Ctrl-q. To exit the display, press < \ > or Esc.
NOTE:
If you use a web browser, the trap message list will not
automatically scroll. To view new trap messages, you must issue
the reload command.
For more information on the Trap Display, see SNMP Trap Display in Chapter 5 of this
manual. For a complete list of IAN-150 traps and their descriptions, see Appendix C, “Trap
Messages,” in this manual. For information on how to configure the IAN-150 to filter certain
traps or display traps from another node, see Trap Output Configuration earlier in this chapter.
4-10
IAN150/IPP MT
6/30/97
Chapter
5
Utilities and Diagnostics
NOTE:
noted.
This chapter describes utilities and diagnostic programs that are supplied with the Synchrony
IAN-150 operating software.
The following utilities programs are available:
•
Ping - Used to diagnose and debug network communications.
•
Table Flush - Clears IP and IPX routing table information.
•
SNMP Trap Display - Lists SNMP traps generated by selected nodes.
•
Pseudoport - Used to diagnose and debug network communications.
•
Loader - Enables download and upload of IAN-150 software.
•
Telnet - Provides remote access to another IAN-150.
The following diagnostics programs are available:
•
Node Monitoring - Used to monitor node status.
•
Port Diagnostics - Used to diagnose line/port problems without taking the IAN-150 offline.
To access the Utilities menu, select Utilities from the Main Menu, or type UI or 3 from the
command line of any menu or screen and press Enter. The system displays the following menu:
3. [UI] Utilities
1. Ping
2. Table Flush
4. Pseudoport
5. Loader
6. Telnet
Figure 5-1. Utilities Menu
IAN150/IPP MT
6/30/97
5-1
Chapter 5, Utilities and Diagnostics
The options on the Utilities menu are explained in the following sections of this chapter.
Ping Utility
Ping programs test IP and IPX protocol communications between devices over a data
communications network. The IAN-150 ping utility includes ICMP and IPX ping functions.
ICMP Ping
The IAN-150 sends an Internet Control Message Protocol (ICMP) echo packet to a specified
device and waits for a response from that device. To access the ICMP Ping Parameters screen,
from the Main Menu, follow the path:
3. Utilities
1. Ping
1. ICMP Ping
or enter UPP or 311 from the command line of any menu or screen and press Enter. The system
displays the following ICMP Ping Parameters screen:
3.1.1 [UPP] ICMP Ping Parameters
Destination Host
Data Size (bytes)
Pings Requested
Timeout (sec)
Time Delay (sec)
Ping Status
Pings Sent
Valid Responses
Invalid Responses
Total Responses
Port No of Last Ping
Min Round Trip Delay
Max Round Trip Delay
Avg Round Trip Delay
Sent
(ms)
(ms)
(ms)
000.000.000.000
544
1
1
1
NEVER RUN
0
0
0
0
0
0
0
0
Figure 5-2. ICMP Ping Parameters Screen
The first five fields require user input, while the remaining eight fields are response-only fields.
The ICMP Ping parameters are described in the following paragraphs. Corresponding MIB
values, where applicable, appear in brackets next to the parameter fields. If you have previously
defined data for this screen, perform a Read command to view the currently configured settings.
Destination Host [polUtilPingIPAddress]
Identifies the IP Address of the destination you are going to ping. Enter the address in dotted
decimal format.
Data Size [polUtilPingDataSize]
Designates the number of bytes to be transmitted during each ping transmission. The value can
be any number between 1 and 4096. The default is 544.
5-2
IAN150/IPP MT
6/30/97
Pings Requested [polUtilPingNumPings]
Designates the number of ping transmissions to be initiated. Valid values can be any number
between 1 and 2,147,483,647. The default is 1.
Timeout [polUtilPingTimeInt]
After the number of seconds specified in this field, a ping test that has not received a response
packet will time out. Valid values are from 1 to 535 seconds. The default is 1 second.
Time Delay [polUtilPigTimeDelay]
Designates the time delay in seconds between successive transmissions of the ping echo packets.
Valid values for this parameter are from 0 to 535 seconds; the default is 1 second.
Viewing Ping Response
Once you complete the parameter input fields, the transmission of echo packets begins. To view
ping responses, type < . > R and press Enter.
The Ping Status field message changes from NEVER RUN to RUNNING, and then to
COMPLETED. The ping response fields then display the results of the test.
Ping Status [polUtilPingStatus]
Indicates the status of the ping test being performed.
Pings Sent [polUtilPingNumSent]
Indicates the number of echo packets sent from this device to the destination.
Valid Responses [polUtilPingNumRcvd]
Indicates the number of valid responses received during the test.
Invalid Responses [polUtilPingNumError]
Indicates the number of invalid responses received during the test. Invalid responses are those
that contain errors (for example, corrupted data).
Total Responses [polUtilPingNumTotal]
Displays the total number of responses received during the test.
Port No of Last Ping Sent [polUtilPingLastPingPort]
Indicates the port number on which the last ping packet was sent. This is useful in instances
where there is more than one IP port.
Min Round Trip Delay [polUtilPingMinTime]
Indicates the minimum delay in milliseconds between when an echo packet was sent and when a
response packet was received.
Max Round Trip Delay [polUtilPingMaxTime]
Indicates the maximum delay in milliseconds between when an echo packet was sent and when a
response packet was received.
Avg Round Trip Delay [polUtilPingAveTime]
Indicates the average delay in milliseconds between when an echo packet was sent and a response
packet was received.
IAN150/IPP MT
6/30/97
5-3
IPX Ping
The IAN-150 sends an Internet Packet Exchange echo packet to a specified device and waits for a
response from that device. To access the IPX Ping Parameters screen from the Main Menu follow
the path:
3. Utilities
1. Ping
2. IPX Ping
or enter UPX or 312 from the command line of any menu or screen and press Enter. The system
displays the following IPX Ping Parameters screen:
3.1.2 [UPX] IPX Ping Parameters
Dest Network
Dest Host
Data Size (bytes)
Pings Requested
Timeout (sec)
Time Delay (sec)
Ping Status
Pings Sent
Valid Responses
Invalid Responses
Total Responses
Port No of Last Ping
Min Round Trip Delay
Max Round Trip Delay
Avg Round Trip Delay
00000000
00:00:00:00:00:00
544
1
1
1
NEVER RUN
0
0
0
0
Parameters
0
(ms)
0
(ms)
0
(ms)
0
Figure 5-3. IPX Ping Parameters Screen
You use the IPX Ping Parameters screen to perform the same tests between networks as the
ICMP Ping performs within a network. Because these tests are performed between networks, the
following additional parameter field appears on the IPX Parameters screen:
Dest Network [polUtilPingIPAddress]
Identifies the IPX Address of the network on which the destination object resides.
Dest Host [polUtilPingHostddress]
Identifies the MAC Address of the destination object on the network.
5-4
IAN150/IPP MT
6/30/97
Table Flush Utility
The Table Flush Utility enables you to clear IP and IPX protocol tables. From the Main Menu,
follow the path:
3. Utilities
2. Table Flush
or enter UF or 32 from the command line of any menu or screen and press Enter. The system
displays the Table Flush Menu:
3.2 [UF] Table Flush
1. IP Table Flush
2. IPX Table Flush
Figure 5-4. Table Flush Utilities Menu
IP Table Flush
Select IP Table Flush from the Table Flush Utilities menu to clear either the Common Routing
Table or the ARP Table. From the Main Menu, follow the path:
3. Utilities
2. Table Flush
1. IP Table Flush
or enter UFI or 321 from the command line of any menu or screen and press Enter. The system
displays the IP Table Flush menu:
3.2.1 [UFI] IP Table Flush
1. Common Routing Table Flush
2. ARP Table Flush
Figure 5-5. IP Table Flush Menu
To flush a particular table, select the table and enter a destination host IP address at the prompt.
Press < . >, then type SU (for Submit) and press Enter to clear the table.
IAN150/IPP MT
6/30/97
5-5
IPX Table Flush
Select IPX Table Flush from the Table Flush Utilities menu to clear the IPX Routing Table or
the IPX SAP Table. From the Main Menu, follow the path:
3. Utilities
2. Table Flush
2. IPX Table Flush
or type UFX or 322 from the command line of any menu or screen and press Enter. The system
displays the IPX Table Flush menu:
3.2.2. [UFX] IPX Table Flush
1. IPX Routing Table Flush
2. IPX SAP Table Flush
Figure 5-6. IPX Table Flush Menu
To flush a particular table, select the table and enter a destination network ID or SAP name at the
prompt. Press < . >, then type SU and press Enter to clear the table.
SNMP Trap Display
The console port on the IAN-150 can act as a network manager by displaying traps in a userreadable form on an attached terminal or PC. The IAN-150’s local traps are sent to the SNMP
Trap Display after being filtered. Any other node in the network can also specify a destination IP
address on this node and its traps will also be displayed. To access this screen from the Main
3. Utilities
or type US or 33 from the command line of any menu or screen and press Enter. A sample
SNMP Trap Display is shown below:
0
10
153
153
10
10
10
10
3
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
AUG01
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:44
10:32:45
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
SYSTM
X28
SYSTM
SYSTM
X28
X28
X28
X28
X28
Node
Port
Port
Port
Port
Port
Port
Port
Port
0 Installing Task
47 Installing Task
48 Installing Task
49 Installing Task
50 Installing Task
0 Link Recovery
5-6
IAN150/IPP MT
6/30/97
Each trap display contains an index number used for filtering, the date and time when the trap
occurred, the IP address of the node that issued the trap, the protocol or process that issued the
trap, the port number, and a brief description of the event that caused the trap. Traps that have an
IP address of 000.000.000.000 are those that were issued by the local node.
You can configure the number of traps held for display from 20 through 1023 by adjusting the
number of traps stored is 20. When the number of traps generated exceeds the Trap Queue Depth
value, the earliest traps will be discarded.
If there are more trap messages than can be displayed on one screen, the list automatically scrolls
to the end, and you will only see the last screenful of messages. To suspend the scrolling
function, press Ctrl-s. To restart the scrolling function, press Ctrl-q. To save trap messages to a
file on a PC running Talk connected to the console port, press < \ > to return to the Utilities
Menu. Press F4 to initiate a screen capture. Type the desired path and filename at the prompt that
appears at the bottom of the screen. Select SNMP Trap Display. After all trap messages have
been displayed, press F2 to end the screen capture. The Trap messages are now in ASCII format
in the file you specified.
NOTE:
If you use a web browser, the trap message list will not
automatically scroll. To view new trap messages, you must issue
the reload command.
For information on how to configure trap generation, see Trap Output Configuration in
Chapter 4. You can block the display of traps by using the Trap Blocking screen (2.1.5.5), and
setting the parameter Block Display Trap to no. For a complete list of IAN-150 traps and their
descriptions, see Appendix C, “Trap Messages.”
Pseudoport Utility
The Pseudoport Utility emulates addressable devices and has specific functions that provide you
with additional diagnostic tools to help test and debug the network. Pseudoports can be used to
induce a load into the network, diagnose routing problems within the network, isolate hardware
problems, and isolate infrastructure problems such as poor lines. A pseudoport can implement the
following functions:
•
Data Traffic Generation
•
Data Echo
•
Data Sink
•
Response-Time Measurement
In a minimal application, you can configure a pseudoport with a Traffic Generator function and
then submit requests using the Pseudoport Operation screen (3.4.3). The pseudoport establishes a
call to the address specified in the submit request, and generates the specified amount of data to
that port. The destination port could be another pseudoport or any other addressable entity, such
as an X.28 terminal.
IAN150/IPP MT
6/30/97
5-7
If the called entity is a pseudoport that has been configured to echo data, then the submit request
can specify that the originating pseudoport calculate round-trip delay. This allows you to monitor
responsiveness of the network. For detailed information, see Pseudoport Configuration or
Pseudoport Operation later in this chapter.
Pseudoport User Interface
A pseudoport user interface is provided by the NMS (Network Management System) console and
EMS 200. The user interface allows you to configure and initiate the traffic generator function on
a pseudoport, read the configuration and status of any pseudoport, and abort the activity of any
pseudoport.
Traffic Generator Function
The traffic generator transmits data traffic to any available port or device in the network. The
traffic generator places a call to the X.121 address or destination pseudoport provided in the user
interface and upon successful completion of the call, transmits a configurable number of data
packets to the destination end.
Several different patterns can be generated using the Generate function. The packet size
negotiated on the call must be greater than or equal to the length of the pattern. If not, the call
will be cleared and the Submit request will not be accepted. Also, pattern verification and
response-time measurements only apply to certain patterns: pattern verification only applies to
511 SYNC through ASCII BAR and response-time measurements only apply to 64 byte through
2048 byte patterns.
Table 5-1 provides a description of each of the patterns and indicates whether the pattern can be
used for data verification or response-time measurements.
5-8
IAN150/IPP MT
6/30/97
Table 5-1. Data Patterns
Pattern
Verification
Allowed
Response
Time
Length
(Bytes)
Description
511 SYNC
Yes
No
64
ITU-T sync pattern.
0-7F
Yes
No
128
This pattern will range from 0x00 to 0x7F hex.
Values which could result in the inadvertent
transmission of XOFF or XON to an X.28 device
will be decremented by one.
40-7F
Yes
No
64
This pattern will range from 0x40 to 0x7F hex.
0-FF
Yes
No
256
This pattern will range from 0x00 to 0xFF hex.
zeros
Yes
No
64
This pattern is all zeros.
ones
Yes
No
64
This pattern is all ones.
ASCII FOX
Yes
No
56
Contains the message "The quick brown fox
jumps over the lazy dog 0123456789"
ASCII TIM
Yes
No
81
Contains the message " ASCOM TIMEPLEX
BARBERPOLE ASCOM TIMEPLEX
BARBERPOLE ASCOM TIMEPLEX
BARBERPOLE".
ASCII GRA
Yes
No
96
Consists of the printable ASCII graphic
characters, ranging from $20 to $7e.
Contains the standard barber pole pattern.
ASCII BAR
Yes
No
79
64 byte
No
Yes
64
128 byte
No
Yes
128
The content of these packets is undefined. They
256 byte
No
Yes
256
are used to calculate round-trip delay or to
512 byte
No
Yes
526
introduce traffic into the network.
1024 byte
No
Yes
1024
2048 byte
No
Yes
2048
Echo Function
The Echo function accepts a call from another device or pseudoport and then echoes any data
packets it receives back to the originating device or pseudoport. Up to 32 circuits can be
configured for the echo function.
Sink Function
The Sink function accepts a call from another device or pseudoport and subsequently sinks
(discards) any data packets that it receives. Up to 32 circuits can be configured for the sink
function.
IAN150/IPP MT
6/30/97
5-9
Pseudoport Configuration
Pseudoport parameters are located on the following screens:
•
Pseudoport Port Configuration (3.4.1)
•
Pseudoport Circuit Configuration (3.4.2)
•
Pseudoport Operation (3.4.3)
To access the Pseudoport Port Configuration screen from the Main Menu, follow the path:
3. Utilities
4. Pseudoport
1. Port Configuration
or type UUP or 341 from any menu or screen and press Enter. The pseudoport is defined as Port
62. The pseudoport parameters will not take effect until you go to the Port Status screen (1.2.1)
and cycle Port 62.
3.4.1 [UUP] Pseudoport Port Configuration (Port 62)
Max Circuit Count
8
Figure 5-8. Pseudoport Port Configuration Screen
Max Circuit Count [polConfIntfPpMaxlcns]
This is the number of circuits installed on the port. The range is from 1 to 999. The default
number of circuits is 8.
After you set Max Circuit Count, type < . > W and press Enter to save the value to the
configuration database. Press < \ > to return to the previous screen (3.4); then select Circuit
Configuration. The system displays the Pseudoport Circuit Configuration screen:
3.4.2
[UUC] Pseudoport Circuit Configuration
Circuit Range
000-000
Address
Network
Packet Size
Throughput
Password
00000
128
9,600
******
Pattern
Action
Verify Data
511 SYNC
ECHO
NO
Group
Window
Timeout Min
000
002
NO
User
Modulo
Force Acks
000
8
NO
Figure 5-9. Pseudoport Circuit Configuration Screen
5-10
IAN150/IPP MT
6/30/97
The Pseudoport Circuit Configuration parameters are described in the following paragraphs.
Corresponding MIB values, where applicable, appear in brackets next to the parameter fields. If
you have previously defined data for this screen, enter the circuit numbers and execute a Read
command to see the currently configured settings.
Circuit Range [polConfCircLo] [polConfCircHi]
Defines the addresses of the first and last circuits in a circuit block. A circuit block may consist
of a single circuit, or may contain as many circuits as are valid for the port.
Address [polConfCircAddress]
Provides the address for calls on this circuit. The Address field can contain as many as 15 digits.
When a subsequent Submit command is executed from the Pseudoport Operation screen (3.4.3),
the Called Address, if different from this address, will override it.
Network [polConfCircNetwrk]
Identifies the virtual network to which this circuit block belongs. Valid values are from 0 to
65535. The default value is 0.
Group [polConfCircGroup]
Identifies the Closed User Group to which this circuit belongs. Valid values are from 0 to 255.
The default value is 0.
User [polConfCircUser]
Identifies a user in the Closed User Group to which the circuit belongs. User field values are
from 0 to 255. The default value is 0.
Packet Size [polConfCircPktSiz]
Defines the maximum packet size for this circuit block. If settings at the ends of a call differ,
Packet Size is negotiated towards a setting of 128. The value of this parameter must be less than
or equal to the corresponding MTU Size parameter for this port. Available packet settings are:
1
8
64
512
2
16
128
1024
4
32
256
2048
Window [polConfCircWindow]
Defines the maximum number of unacknowledged packets allowed for calls on a circuit. For
incoming calls, this parameter defines the limiting window size. If settings at the ends of a call
differ, Window is negotiated towards a setting of 2. For outgoing calls, this parameter is used as
a default when no X.25 call facility is present. When Modulo is set to 8, this parameter can range
from 1 to 7; when Modulo is set to 128, this parameter can range from 1 to 127. The default
value is 2.
Modulo [polConfCircModulo]
Defines the numbering arrangement for the sequencing of information packets over this circuit
block. If the Modulo parameter setting at the calling end does not match the Modulo parameter
setting at the called end, an error occurs. Available parameters are 8 and 128. The default setting
is 8.
IAN150/IPP MT
6/30/97
5-11
Throughput [polConfCircThrPut]
Used for outgoing calls when no X.25 call facility is present. If settings at the ends of a call
differ, Throughput is negotiated to the lower setting. Valid values for this parameter are:
75
300
1200
4800
19200
150
600
2400
9600
48000
Timeout Min [polConfCircTimOut]
Defines the allowed interval, in minutes, during which there may be no data traffic on this circuit
block. When the Timeout Min interval expires, a LOCAL PROCEDURE ERROR or REMOTE
PROCEDURE ERROR appears, and a TIME EXPIRED diagnostic code also appears. The
Timeout Min setting used for a call will be the one configured at the node that sources the call.
The following settings are available:
2
15
30
90
180
5
20
45
120
210
10
25
60
150
240
NO
The default setting is NO, which means that no timeout will occur and no error message will be
generated.
Force Acks [polConfCircFrcAck]
Defines how Level 3 acknowledgments will be handled. Available values are:
YES
Indicates that Level 3 acknowledgments will be passed through the
network immediately.
NO
Indicates that Level 3 acknowledgments will be suppressed until
unACKed packets total one-half of the Window parameter setting.
The default setting is NO.
Password [polConfCircPassWd]
Defines, for incoming calls, a password to access a resource such as a printer or host computer.
This parameter is also used for outgoing permanent virtual circuit calls from a non-X.28 port to
define a password required at the destination address. The Password field is six alphanumeric
characters.
Pattern [polConfCircPsePattern]
Defines the patterns used by the circuit to send or verify data and to calculate delay time. See
Table 5-1 in Traffic Generator Function earlier in this chapter for the patterns and their
descriptions.
5-12
IAN150/IPP MT
6/30/97
Action [polConfCircPseFunction]
The operation of the circuit. The options for operation are:
GENERATE
Places a call and transmits a configurable number of data packets to a
designated destination. For a Submit command, this is the only valid value.
ECHO
Accepts a call from another device or pseudoport and echoes any data packets
it receives back to the originating device.
SINK
Accepts a call from another device or pseudoport and discards any data
packets it receives.
The default operation is ECHO.
Verify Data [polConfCircPseVerify]
Compares the incoming data against the configured pattern. The options are YES (Verify) and
NO (Don’t Verify). The default is NO.
Pseudoport Operation
Before you can perform a pseudoport operation, you must write the pseudoport port and circuit
configurations to the configuration database and cycle the pseudoport using the Port Status and
Control screen (Screen 1.2.1). Once you have accomplished this, access the Pseudoport
Operation screen by typing UUO or 343 from any menu or screen command line and pressing
Enter. The system displays the Pseudoport Operation screen:
3.4.3 [UUO] Pseudoport Operation (Port 62)
Circuit
0
Called Address
Number of Packets
Pattern
Function
256
511 SYNC
ECHO
Verify Data
Calculate RT Delay
Transmit Delay (msec)
YES
NO
0
Packets In
Packets Out
Verify Errors
0
0
0
State
Duration
Average RT Delay (msec)
Last RT Delay (msec)
NEVER RUN
0000:00:00
0
0
Figure 5-10. Pseudoport Operation Screen
The following paragraphs describe pseudoport operation parameters. Corresponding MIB values,
where applicable, appear in brackets next to the parameter fields. If you have previously defined
data for this screen, enter the circuit number and execute a Read command to see the currently
configured settings.
IAN150/IPP MT
6/30/97
5-13
Circuit [polUtilPseudoCircuit]
Identifies the logical channel number (circuit) that will be used for this pseudoport operation.
Called Address [polUtilPseudoAddress]
Identifies the address to which the call will be established to generate traffic.
Number of Packets [polUtilPseudoNumPkts]
Defines the number of packets that will be generated and transmitted over the virtual call. Valid
values are from 0 to 483,647 packets. The default number is 256.
Pattern [polUtilPseudoPattern]
Identifies the pattern that will be generated in each packet. The pattern chosen determines
whether data verification or response-time measurements (or both) apply. See Table 5-1 in
Traffic Generator Function, earlier in this chapter, for descriptions of possible patterns.
Function [polUtilPseudoFunction]
Defines the data operation that the pseudoport is performing. Valid functions are GENERATE,
ECHO, and SINK. For a Submit, the only valid function is GENERATE. For a Read of status,
all functions are valid. The valid functions are described below.
GENERATE
Transmits a configurable number of data packets to a designated destination.
For a Submit command, this is the only valid value.
ECHO
Accepts a call from another device or pseudoport and echoes any data
packets it receives back to the originating device.
SINK
Accepts a call from another device or pseudoport and discards any data
packets it receives.
Verify Data [polUtilPseudoVerify]
If set to YES, the port verifies any incoming data packets against the pattern specified. This
option is only valid for certain patterns. See Table 5-1 in this chapter for details.
Calculate RT Delay [polUtilPseudoCalcRt]
If set to YES, the round-trip delay will be calculated. This option is only valid for certain
patterns. See Table 5-1 for details. RT Delay is only performed on the GENERATE side of the
call.
Transmit Delay [polUtilPseudoTxDelay]
Defines the delay in milliseconds between successive packet transmissions. The range is from 0
through 65535 ms. If set to 0, packets will be generated until the window is full.
After setting these pseudoport operating parameters, press < . >, then type SU and press Enter to
initiate the pseudoport function. The remaining parameters on this screen are for monitoring the
pseudoport operation. Execute a Read command to see the parameter values.
Packets In [polUtilPseudoPktIns]
Identifies the number of packets received on the pseudoport. Due to network flow control and the
fact that the Clear Request may pass the last data packet as it transits the network, the number of
packets transmitted may not equal the number of packets received.
Packets Out [polUtilPseudoPktOuts]
Identifies the number of packets transmitted by the circuit on the pseudoport.
5-14
IAN150/IPP MT
6/30/97
Verify Errors [polUtilPseudoErrors]
Identifies the number of packets received whose pattern did not exactly match the configured
pattern. Verify Data must be set to YES in order for this number to be valid.
State [polUtilPseudoState]
Identifies the current state of this test circuit. Possible states are NEVER RUN, RUNNING,
COMPLETED, and ABORTED.
Duration [polUtilPseudoDuration]
Identifies the length of time in hours, minutes and seconds that the submission has been active.
Average RT Delay [polUtilPseudoAvgRt]
Identifies the average round-trip delay in milliseconds between send and receive.
Last RT Delay [polUtilPseudoLastRt]
Identifies the round-trip delay in milliseconds of the last packet received.
Loader Utility
The IAN-150 stores its operating software internally in Flash Memory, and its configuration
database in Non-Volatile RAM (NVM). Trivial File Transfer Protocol (TFTP) can be used to
handle data transfer operations. The Loader screen allows you to configure the download/upload
operation, and provides status information. To access the Loader screen from the Main Menu,
follow the path:
3. Utilities
5. Loader
or type UL or 35 from any menu or screen and press Enter. The system displays the Loader
screen:
3.5 [UL] Loader
Action
File Name
LOAD PROGRAM
Load Status
Error Code
Error Msg
NONE
Host IP
000.000.000.000
Load Result
UNKNOWN
0
OK
TFTP State
Total Starts
Total Aborts
Total Retrans
TFTP Message
Packets
Total RRQ
Total WRQ
Total Errors
IDLE
0
0
0
File Size
Bad TID
Bad Filename
Memory Full
IN
0
0
0
0
0
0
0
0
OUT
0
0
0
0
Program Filename
Config. Filename
Figure 5-11. Loader Screen
IAN150/IPP MT
6/30/97
5-15
The following paragraphs describe loader parameters. Corresponding MIB values, where
applicable, appear in brackets next to the parameter names.
Action [polUtilLoadType]
Indicates which operation will be performed. The default value is LOAD PROGRAM. Pressing
spacebar alternately switches between the following functions:
NO LOAD
Does not initiate any file transfer
LOAD PROGRAM
Allows the executable code to be downloaded to the IAN-150 from
the host node specified by Host IP address.
BACKUP CONFIG
Allows the IAN-150 configuration to be saved to a TFTP server if
the IP address of the TFTP server is defined.
RESTORE CONFIG
Allows the configuration file to be restored from the file server to
the IAN-150.
After you select the desired operation in the Action field, enter the appropriate IP address, path
and file name, then execute the operation by typing < . > SU and pressing Enter.
Host IP [polUtilLoadIPAddress]
Identifies the IP address of the source or destination host as determined by the function indicated
in the Action field.
File Name [polUtilLoadFileName]
Identifies the location on the host where the file resides or will be located after execution of the
function indicated in the Action field.
Load Status [polUtilLoadStatus]
Displays the processing status of the operation currently in progress. The load status will be one
of the following:
NONE
IDLE
RECEIVING_PROGRAM_FILE
PROGRAMMING_FLASH
ERASING_FLASH
SENDING_CONFIG_FILE
HOST_STORING_CONFIG
HOST_ERASING_CONFIG
RECEIVING_CONFIG_FILE
STORING_CONFIG
ERASING_CONFIG
5-16
IAN150/IPP MT
6/30/97
Load Result [polUtilLoadResults]
Indicates whether the last loader operation was successful. If no operation has been attempted
since the IAN-150 was last reset, or if an operation is currently in progress, the Load Result will
be NONE. Other valid results are:
UNKNOWN
INDETERMINATE
PROGRAM_LOAD_SUCCESS
LOAD_PROGRAM_FAIL
BACKUP_CONFIG_SUCCESS
BACKUP_CONFIG_FAIL
RESTORE_CONFIG_SUCCESS
RESTORE_CONFIG_FAIL
Error Code [polStatTftpErrCodes]
Displays the numerical value associated with the error code of the last TFTP operation. See Table
5-2 for a list of error codes and their description.
Table 5-2. TFTP Error Codes
IAN150/IPP MT
6/30/97
Error
Code
Error Msg
1
OK
2
File Not Found
3
Access Violation
4
Disk Full or Allocation Exceeded
5
Illegal TFTP Operation
6
Unknown transfer ID
7
File Already Exists
8
No Such User
9
Reached Maximum Retransmit Limit
10
No Buffers Available
11
File Too Big
12
Erase Flash Failure
13
Read Message Fuffer Failure
14
Write Error
15
Exceeded Memory Boundary
16
Read Failure
17
Ram Image Corrupted
18
Network Image Corrupted
19
Flash Image Corrupted. DO NOT RESET.
20
Invalid File Type or Compatibility Number
21
TFTP is serving others. Try Again.
22
Cannot Allocate Timer
23
No Client Session Running
24
Session Aborted by User
25
Network Not Reachable
5-17
Error Msg [polUtilLoadErrMsg]
This field displays a description of the error that occurred in the last aborted operation.
TFTP State [polStatTftpStatus]
Displays a numerical value that corresponds to the type of TFTP function in operation at the time
the Read command was executed. Possible values are:
1
2
3
4
5
NOTE:
IDLE
SERVER MODE
CLIENT_WRITE
(This value has no meaning. It is a place-holder only)
CLIENT_READ
The TFTP state depicted numerically in this field is also displayed
in words in the Load Result parameter on this screen.
File Size [polStatTftpFileSize]
Displays the size (in bytes) of the file(s) received since the last reset. This number is cumulative:
it does not return to zero after a TFTP operation ends or when a new one begins.
Total Starts [polStatTftpStarts]
Displays the total number of times the upload was started since the IAN-150 was last reset.
Bad TID [polStatTftpErrBadTIDs]
Displays the number of unrecognized TFTP Session IDs.
Total Abort [polStatTftpAborts]
The total number of times the TFTP upload was aborted since the last time this IAN-150 was
reset.
Bad Filename [polStatTftpErrBadFns]
Displays the number of RRQs (read requests) that have bad filenames since the IAN-150 was last
reset.
Total Retrans [polStatTftpRetrans]
Displays the total number of retransmitted TFTP packets since the IAN-150 was last reset. If the
server does not respond after 6 retransmissions, the TFTP session will time out.
Memory Full [polstatTftpErrMemFulls]
Displays the number of error packets sent due to memory allocation errors since the IAN-150
was reset
5-18
IAN150/IPP MT
6/30/97
TFTP Message
Packets [polStatTftpInPackets] [polStatTftpOutPackets]
The total number of packets received and transmitted since the IAN-150 was last reset.
Total RRQ [polStatTftpInRRQs] [polStatTftpOutRRQs]
The total number of read requests received and transmitted since the IAN-150 was last reset
Total WRQ [polStatTftpInWRQs] [polStatTftpOutWRQs]
The total number of write requests received and transmitted since the IAN-150 was last reset.
Total Errors [polStatTftpInErrors] [polStatTftpOutErrors]
The total number of error packets received and transmitted since the IAN-150 was last reset
Program Filename [polUtilLoadProgramFileName]
Identifies the current program filename stored in compressed form in this unit. This does not
represent the actual program version used until the user issues the RELOAD command.
Config. Filename [polUtilLoadConfigFileName]
Identifies the last filename used to store this unit’s configuration database into its non-volitaile
memory. If the “nvm” filename is shown, it has never been updated from either a remote IP host
or downloaded from a console port using TALK utility.
TELNET Utility
The TELNET utility allows remote access to another IAN-150 from a local IAN-150. Use the
TELNET protocol to log in to the remote IAN-150 and monitor or control the unit as if you were
locally connected. You can also use this utility to access another IP device.
NOTE:
Using the IP command, it is possible to monitor and control a
remote IAN-150 without the TELNET protocol. For more
information, see IP Command in Chapter 4.
TELNET requires the use of a virtual port configured for X.28. The IAN-150 is shipped with
virtual ports 58 through 61 pre-configured at the factory for TELNET operation. You must also
have IP running on at least one port of both IAN-150s. If you are not sure whether IP is running
on the IAN-150, check the Port Status and Control Screen (Screen 1.2.1). To access this screen,
type SPP or 121 at the command line of any menu or screen and press Enter.
IAN150/IPP MT
6/30/97
5-19
Port
000
Port Type
Active Protocols
MTU Size
Speed
Admin State
Operational State
Operational Since
Address
UNDEFINED
Octets
Unicast Packets
Multicast Packets
Discards
Errors
Unknown Protos
Queue Length
0
0
UP
UP
SEP19-96 12:54:19
00:00:00:00:00:00 (C)
IN
0
0
0
0
0
0
00:00:00:00:00:00 (N)
OUT
0
0
0
0
0
Line Util%:
Last Sec
15 Secs
IN
0
0
OUT
0
0
0
Figure 5-12. Port Status and Control Screen
The Active Protocols field indicates the routing protocols that are operating on the selected port.
Select Port 1, type < . > R and press Enter to read the status of Port 1. Check the Active
Protocols field to see if IP is listed. If not, type < . > N and press Enter to issue a Read Next
command; then check the Active Protocols field for Port 2. If necessary, continue to issue the
Read Next command until a port is found that is running IP.
If IP is not running on the IAN-150, you must write IP port and protocol parameters to the
configuration database and designate either a physical port, a LAP port, or a BRE port as an IP
port. See Chapter 11, “TCP/IP Configuration,” in the Synchrony IAN-150/IPP Reference Manual
for detailed instructions.
To begin a TELNET session, type UT or 36 from the command line of any menu or screen and
press Enter. The 3.6 screen and TELNET prompt will appear. Type open followed by the IP
address of the remote device you wish to access, then press Enter. To terminate a TELNET
connection, press ctrl ] or ctrl z, and then type quit and press Enter.
TELNET blocks login attempts by remote clients when three login attempts have failed. The
login is blocked for the number of minutes specified in the X.28 Violation Delay parameter on
the Node Parameter Configuration screen (2.1.1).
To access the Telnet Help Menu, type h at the telnet prompt and press Enter. Screen 3.6 and the
Telnet Help Menu is shown in the following figure.
5-20
IAN150/IPP MT
6/30/97
3.6 [UT] Telnet (‘help’ for menu,^] or ^z to escape)
telnet> h
Commands may be abbreviated.
exit/quit
open (ipa)
status
close
abort
help/?
Available commands are:
exit telnet
connect to a site
print status information
close current connection
abort current connection
print help information
telnet>
Figure 5-13. Telnet Help Menu
Diagnostics
The IAN-150 operating software includes the following types of internal diagnostic tools:
•
Power-Up Self Tests
•
Node Monitoring
•
Port Diagnostics
These diagnostics are described in the following paragraphs.
Power-Up Self-Tests
When an IAN-150 is powered on, Flash Memory is checksummed to ensure integrity of the
object code.
Node Monitoring
To access the Node Status menu, type SNN or 1.1.1 from the command line of any menu or
screen and press Enter.
IAN150/IPP MT
6/30/97
5-21
1.1.1 [SN] Node Status
Description
Operational Since
Last Failure
Failure Reason
SEP23-96 17:48:20
SEP23-96 17:47:39
POWER FAILURE
MEMORY
NVM RAM
Buffer RAM
Flash
BYTES INSTALLED
122,368
5,516,560
5,120,000
CPU Utilization.
HARDWARE STATUS
Port Status
Port Install
Hardware Status
Hardware Install
BYTES AVAILABLE
102,024
4,511,456
Last 10 Secs
Last 1 Min
32
20
%
83
81
Last 5 Mins
10
31->0
00000000000000000000000000111111
00000000000000000000000000111111
00000000000000000000000000000000
00000000000000000000000000000000
Figure 5-14. Typical Node Status Monitoring Screen
Node status parameters are described in the following paragraphs. Corresponding MIB values,
> or Esc.
Description [polStatNodeSoftwareVersion]
Provides the following system software information: software version number, software builddate, target hardware platform, and the checksum value.
Operational Since [polStatNodeBootTime]
Contains the date (MMMDD-YY) and time (HH:MM:SS) that this device was last reset or
powered up.
Last Failure [polStatNodeLastFail]
Contains the date (MMMDD-YY) and time (HH:MM:SS) that this device last failed.
Failure Reason [polStatNodeFailCause]
Describes the reason for the last failure experienced by this device.
5-22
IAN150/IPP MT
6/30/97
MEMORY
NVM RAM [polStatNodeNvmTotal, polStatNodeNvmPercent]
The IAN-150 has 128 KB of non-volatile SRAM (NVM) available to store system configuration
information. The NVM is backed up by lithium batteries which can preserve the data for up to
seven years without external power. Some of the 128 KB of memory is reserved for internal
functions and is therefore not included in the numbers displayed on this screen. The BYTES
INSTALLED column displays the total amount of NVM that is available for allocation. The
BYTES AVAILABLE column displays the number of bytes that are currently unallocated. The
% column displays the percentage of the total available for allocation that is not currently
allocated.
Buffer RAM [polStatNodeRamTotal, polStatNodeRamPercent]
The IAN-150 contains 2 MB of DRAM soldered to the motherboard. In addition, a 4, 8, or 16
MB DRAM SIMM can be installed in a SIMM socket, providing a total of 6, 10, of 16 MB of
RAM. (A maximum of 16 MB of DRAM can be addressed by the CPU.) Some of this memory is
reserved for internal use and is therefore not included in the numbers displayed on this screen.
The BYTES INSTALLED column displays the total amount of DRAM that is available for
allocation. The BYTES AVAILABLE column displays the number of bytes that are currently
unallocated. The % column displays the percentage of the total available for allocation that is not
currently being used. The IPP has no base DRAM; a DRAM SIMM installed in a SIMM socket
provides 4, 8, or 16 MB or DRAM.
Flash [polStatNode Flash Total]
System software is stored in and executed from 5MB of Flash memory. This field displays the
number of bytes of Flash Ram that is currently installed in the IAN-150.
CPU Utilization [polStatNodeCpuUtil10Sec, polStatNodeCpuUtil1Min,
polStatNodeCpuUtil5Min]
Indicates the percent of CPU bandwitdth used over the specified time period of 10 seconds, 1
minute, or 5 minutes.
HARDWARE STATUS
Port Status [polStatNodePortStatus]
Indicates the results of the internal diagnostic test that has been run on the physical port. If the
internal diagnostic test has failed the bit correponding to the physical port number will be set to
0. If the diagnostic test has passed or has not been run the bit will be set to 1. If the port is not
present in the IAN-150, the bit will be set to 0.
Port Install [polStatNodePortInstall]
Indicates the physical presence of ports in the IAN-150. Ports that are physcially installed will be
indicated with the correpsonding bit set to 1. Ports that are not physically present will be
indicated with the corresponding bit set to 0.
Hardware Status [polStatNodeHWStatus]
Hardware Install [polStatNodeHWInstall]
IAN150/IPP MT
6/30/97
5-23
Port Diagnostics
The IAN-150 comes with resident port diagnostic programs. These diagnostic programs can be
used to access port operation during normal device operation without taking the IAN-150
offline. During port diagnostics, the selected port will not be operational and the throughput of
the device may be affected but the remaining ports and associated protocols will be functional.
This has the following advantages:
•
The unit can be used to diagnose line or port problems without taking the unit down.
•
The diagnostics are fully supported by SNMP management.
•
Where supported by the physical interface and processor chip, both internal (except Token
Ring) and external diagnostics are supported.
•
Token Ring, Ethernet and ISDN daughterboards on IAN-150s can be tested.
NOTE:
Token Ring diagnostics may take up to a minute before starting
data transfer check. The reason is that the diagnostic check
installs the Token Ring drive and tests the CAMs (content
addressable memory) and only then tests data transfer capability.
Internal diagnostics require no external equipment. A variety of patterns can be generated (for
example, 511 sync, ASCII FOX) and both pattern errors and length errors are logged. [V.54 local
and remote loopback serial port test capabilities are provided.]
NOTES:
1. External diagnostics require loopback cables or external
equipment such as a MAU.
2. Before performing port diagnostics, you must evacuate the
port. If this is not done, an error will occur. Go to Screen 1.2,
enter the desired port number, then type < . > E and press Enter.
3. After performing port diagnostics, you must cycle the port to
bring it back online.
You access the Port Diagnostics screen by typing DP or 41 from the command line of any menu
or screen and pressing Enter. The following figure illustrates a typical Port Diagnostics screen.
5-24
IAN150/IPP MT
6/30/97
4.1 [DP] Port Diagnostics
Port
000
Test
Cycles
Pattern
INTERNAL
20
511 SYNC
Mode
Baud Rate
Halt On
ASYNC
50
CYCLES
Tx External
0
Rx External
0
Length Errors
0
Patt Errors
0
Hardware
UNTESTED
Signals
UNTESTED
Async
UNTESTED
Sync
UNTESTED
Figure 5-15. Typical Port Diagnostics Display
Port Diagnostics parameters are described in the following paragraphs.
Port [polDiagIntfIntNum]
Identifies the port on which you want to run diagnostics.
Test [polDiagIntfLoopBk]
Provides five optional loopback tests. Pressing spacebar to scroll through the choices, select the
test you wish to run. The five optional tests are:
INTERNAL
Verifies operation of all internal logic and port drivers (this test is not used for
Token Ring).
EXTERNAL
Verifies operation of all internal logic and port drivers as well as data
connectors (To run external tests, loopback connectors are required. Choose the
appropriate connector according to information in the following tables. For
IAN-150 loopback connectors, refer to Table 5-3. For IPP loopback connectors,
refer to Table 5-4.)
LOCAL
V.54 loop 3 loopback test: Verifies operation of the local modem connected to
the local port (serial port only.)
REMOTE
V.54 loop 2 loopback test: Verifies operation of a remote modem connected
through the local modem port (serial port only).
212-A
Original Bell 212-A, a modem analog loopback: Verifies operation of all
internal logic and port drivers. The local/remote 212-A tests are only run on
serial ports.
IAN150/IPP MT
6/30/97
5-25
Table 5-3. IAN-150 Loopback Connectors
Interface
WPM/Daughter Card Number
Loopback Connector
Part Number
ISDN
ISDN 116229-2
127418-1
Ethernet
Ethernet 116227-1
612276-1
Token Ring
Token Ring 116228-1
612277-1
V.11
V.11 100268-1
612275-1
V.35
V.35 100257-1
100217-3
V.28
V.28 100267-1 (DCE)
100255-1 (DTE)
612275-1
100217-1
X.21
V.11 100268-1
612275-1
MIL-STD-188-114A
MIL-STD-188-114A 100258-2
612275-1
Table 5-4. IPP Loopback Connectors
Interface
WPM/Daughter Card Number
Loopback Connector
Part Number
V.11
V.11 100268-1
612279-1
V.35
V.35 100257-1
612265-1
V.28
V.28 100267-1 (DCE)
100255-1 (DTE)
612267-1
612266-1
X.21
V.11 100268-1
612279-1
MIL-STD-188-114A
MIL-STD-188-114A 100258-2
612279-1
Mode [polDiagIntfDriver]
Indicates the diagnostic test mode. The following diagnostic test modes are supported:
BITSYNC, ETHERNET, TOKEN RING, CHAR SYNC, and ASYNC. Press spacebar to
scroll through the choices. Press Enter to select the mode you want to test.
NOTE:
You should know the port type before you select the test mode.
For port information, refer to the Port Status and Control screen.
Cycles [polDiagIntfCycles]
Indicates how many cycles you wish the pattern to repeat. Valid values are any number between
20 and 1,000,000. The default value is 20.
5-26
IAN150/IPP MT
6/30/97
Baud Rate [polDiagIntfBaud]
This field offers choices of baud rate from 50 bps to 16 Mbps. Valid values, in bps, are:
50
52
75
110
134
150
300
600
1200
1800
2000
2400
36000
4000
4800
7200
8000
9600
14400
16000
19200
32000
38400
48000
64000
96000
128000
192000
256000
384000
512000
768000
1024000
1536000
1544000
2048000
10000000
16000000
Press spacebar to scroll through the choices. Press Enter to select the value you want the test to
run.
•
If Mode is ASYNC the maximum baud rate allowed is 56 Kbps. If you specifiy a value
higher than this, the system restores it to 56 Kbps.
•
Ιf Mode is Token Ring only two values are allowed: 4 Mb and 16 Mb. If you specify a baud
rate less than 16 Mb, the system will set the value to 4 Mb.
•
Ιf Mode is Ethernet, the only value allowed is 10 Mb. The system tests the Ethernet port at
10 MB regardless of what other value you set.
•
Ιf ISDN daughter card is being tested then only BIT.SYNC mode is valid. If you choose any
other mode, the system returns an error message. This board is tested at 64 Kbps regardless
of what other value you select.
Pattern [polDiagIntfPattern]
Indicates the pattern to be transmitted during testing. Press spacebar to scroll through the
choices, then press Enter to select the pattern you wish to transmit. The supported patterns are:
ZEROS
ONES
ASCII FOX, ASCII TIM, ASCII GRA, ASCII BAR
64 BYTE, 128 BYTE, 256 BYTE, 512 BYTE, 1024 BYTE, 2048 BYTE
MAX ETHER
MAX TOKEN
511 SYNC
00 to 7F
40 to 7F
00 to FF
The default is 511 SYNC.
IAN150/IPP MT
6/30/97
5-27
Halt On [polDiagIntfHaltOn]
Indicates if you want the test to halt on CYCLES or ERRORS. If you select CYCLES, the test
continues even if errors are detected.
The remaining fields on the Port Diagnostics Screen are responses to the submitted test:
Tx-External [polDiagIntfTxExts]
The Transmit External field provides a count of detected transmit communications errors at the
port being tested. One or more Tx External errors indicate a hardware fault.
Rx-External [polDiagIntfRxExts]
The Receive External field provides a count of detected receive communications errors at the port
being tested. One or more Rx External errors indicate a hardware fault.
Length Errors [polDiagIntfLenErrs]
Provides a count of the number of times a frame was received that was a different length than the
transmitted test frame. One or more Length Errors indicates a hardware fault.
Patt Errors [polDiagIntfPatErrs]
Provides a count of the number of times the contents of the received pattern failed to match the
contents of the transmitted test pattern. One or more Pattern Errors indicates a hardware fault.
Hardware [polDiagIntfHardware]
Provides status and results of the general hardware diagnostic test that was run on the identified
port. Possible status indications include:
UNTESTED
TESTING
PASSED
FAILED
Indicates that no test was run.
Indicates that the test is currently underway.
Indicates that the identified port has passed the test.
Indicates that the identified port has failed the test.
After you specify the above fields, press <.>, then type SU to submit the test.
Signals [polDiagIntfSignals]
Provides status and results of the input/output diagnostic test that was run on the identified port.
These status statements are the same as those shown above for the Hardware field. However, in
the event of a failure, the applicable failure types are different. The failure types for the port
input/output tests are shown in the following table.
5-28
IAN150/IPP MT
6/30/97
Table 5-5. Input/Output Signal Diagnostic Failure Types
Failure Type
Description
TXD
Transmit data failure
RXD
Receive data failure
RTS
Request to send failure
CTS
Clear to send failure
DTR
Data terminal ready failure
DSR
Data set ready failure
DCD
Data carrier detect failure
RNG
Ring detect/latch failure
TXC
Transmit clock input failure
RXC
Receive clock input failure
TSC
Transmit clock output failure
OUT
Special output OT1 or OT2 signal failure
BSY
Failure of busy output signal
TI
Test indicate signal failure
CSI
CTS conversion control failure
CKE
Clock enable control failure
Async [polDiagIntfAsync]
Provides status and results of the asynchronous loopback diagnostic test run on the identified
port. These status statements are the same as those shown above for the Hardware field.
Sync [polDiagIntfSync]
Provides status and results of the BIT synchronous loopback diagnostic test that was run on the
identified port. These status statements are the same as those shown above for the Hardware
field. This field also shows the status and results of internal/external loopback tests on Ethernet,
and external loopback test on Token Ring.
IAN150/IPP MT
6/30/97
5-29
Chapter
6
Troubleshooting
NOTE:
noted.
This chapter helps you analyze and determine the probable causes of malfunctions associated
with the Synchrony IAN-150. Malfunctions usually fall into one or more of the following
categories:
•
Cable problems
•
Equipment incorrectly configured
•
Service provider’s circuit outage
•
Hardware failures
Regardless of the category of malfunction, it is recommended you follow certain standard
troubleshooting procedures during the initial stages of problem analysis.
Initial Problem Analysis
To narrow the possibilities and help you determine the cause(s) of a malfunction, Ascom
Timeplex has developed an Initial Evaluation Procedure that should be followed during the first
15 minutes after a problem occurs. A critical part of this procedure involves capturing each
screen displayed on the PC that is attached to the console port and saving these screens to a file
which can then be printed and analyzed. The data recorded during this procedure will be helpful
should you need to contact Customer Support.
NOTE:
The following procedures are intentionally generic. If you are not
sure what to look for, or how to interpret the information
displayed on each screen, continue with the screen capture
process. After you complete the Initial Evaluation, print the file
and give it to your network administrator or Customer Support
representative.
1. Visually inspect all cables to verify that they have not become loose or disconnected and that
cable locking mechanisms are engaged.
2. Record the state of each LED (ON, OFF, BLINKING) for each port.
IAN150/IPP MT
6/30/97
6-1
Chapter 6, Troubleshooting
3. Connect a user interface terminal or PC to the console port (Port 0). If you are using a PC, be
sure that it has terminal emulation capability to capture information. (The TALK program
supplied with the IAN-150 operating software is recommended.)
4. If you are using TALK, press F4 to begin the screen capture process. For other terminal
emulation programs, use the appropriate keystrokes.
5. At the message line displayed at the bottom of your screen, type a name and path for the save
file and press Enter. The following statement will appear: Saving Com x to [filename]
(where x identifies the communication port).
6. Log in at the highest access level (Level 0). (The factory default login/password for Level 0
is superuser/root.) The system will then display the Main Menu.
NOTE:
If the problem node is not the local node, Telnet to the problem
Node and record the Alarm Log as described below. (To access
the TELNET prompt, type UT or 36 at the command line of any
user interface menu or screen and press Enter.)
SNMP Alarm Log
7. Review and capture the Alarm Log (SNMP trap display). To display the recorded SNMP
traps, type US or 33 at the command line of any user interface menu or screen and press
Enter.
8. Observe the displayed SNMP messages. (If the first messages scroll off the screen, press
Ctrl-s to pause the screen. Press Ctrl-q to resume scrolling.) If the messages indicate an
error for a process or a specific port, or for a circuit that corresponds to a particular port, go
to the appropriate status or monitoring screen for that process port or circuit and perform a
Read-Next command. (For a complete list of all status and monitoring screens for the
IAN-150, see Appendix D of this manual.)
9. Type < . > 11 and press Enter. The Node Status screen will appear. To see the most current
values, type < . > R and press Enter.
10. To access the Hardware Type Display, type < . > 192 and press Enter. To view the most
current values, type < . > R and press Enter. Note which expansion ports (if any) are
currently installed. Also note the Board Revision level.
11. To access the Port Status and Control screen , type < . > 12 and press Enter. Issue a series of
Read-Next commands and check the port status for all configured ports, virtual as well as
physical. If you suspect a connectivity problem, go to Step 17. If you suspect a line problem,
go to Step 18.
12. Now that you know which ports are active and the type of protocol associated with each port,
check the respective Port and Protocol configuration screens for each protocol suspected of
errors, and verify the the configuration. To view the most current values, issue a Read
command from the command line.
6-2
IAN150/IPP MT
6/30/97
Crash Dump Procedure
NOTES:
1. Before you obtain a crash dump, be sure you activate the
screen capture capability of the user interface device. If you are
using a PC with the TALK terminal emulator, press F4 to begin
screen capture.
2. To initiate a crash dump, either follow the procedure below or
press the NMI (non-maskable interrupt) button that is located
near the console port on the IAN-150. On the IPP, the NMI button
is located at the top of the faceplate. Press the NMI button to
force a crash dump and reset the IAN-150/IPP.
13. Logon with Superuser access (refer to for information about user access levels). From the
command line of any menu or screen, type SH and press Enter. The system displays the
VxWorks Shell Access screen. The VxWorks command line prompt (->) is at the bottom of
the screen.
14. At the VxWorks command line prompt, type crashList and press Enter. If a crash has
occurred, the system will display one or more buffer numbers. If a crash has not occurred,
skip Step 15 and proceed to Step 16.
15. For each crash dump listed, type crashShow x, where x is the buffer number.
16. For a complete list of VxWorks tasks, type < i > and press Enter. Use taskmem to display
the amount of memory held by each task currently running in the IAN-150. To return to the
User Interface, press Esc.
17. If you suspect a connectivity problem, read the routing status screens and the routing table
screens, then initiate the Ping Utility (for IP and IPX protocols) or the Pseudoport Utility (for
legacy protocols) to communicate with a remote node.
Port Diagnostics
If you suspect a line problem, perform an offline loopback test from the Port Diagnostics screen
(Screen 4.1).
NOTE:
Before you perform port diagnostics, you must evacuate the port.
If this is not done, an error will occur. Go to Screen 1.2.1, enter
the desired port number, then type < . > E and press Enter.
18. From the command line of any menu or display, type < . > 41 and press Enter. Specify a
port, select a Test Type and Mode, and indicate the number of cycles you desire to run and
the baud rate. Select a pattern and choose the Halt method. Then type < . > SU (Submit) and
press Enter. While the test is running, use the Monitor command to review the screen for
several seconds. Then return to the Port Status and Control (1.2.1) screen and use the
Monitor command to monitor the port for incoming and outgoing packets.
For more information on port diagnostics parameters, see Port Diagnostics in Chapter 5 of
this manual. For information on the use of the Monitor command, see Port Monitoring in
Chapter 3.
NOTE:
IAN150/IPP MT
6/30/97
After you perform the loopback test, you must install the port to
bring it back online.
6-3
19. If you suspect a particular port has a problem, use the Monitor command to monitor that
port for several seconds. Also refer to Line Trace Procedure, below, for additional port
monitoring commands.
20. Observe and verify that the network is operating normally, based upon the network
topological map.
21. To end the TALK screen capture process, press F2.
Line Trace Procedure
If you suspect a port problem, you can enable a line trace facility to examine the problem. The
Line Trace Procedure is initiated by a Superuser from within the Shell command.
22. Logon using Superuser access. From the command line of any menu or screen, type SH and
press Enter. The system displays the VxWorks Shell Access screen. You will see the
VxWorks command line prompt (->) at the bottom of the screen.
23. Initialize the line trace resources for the specified port. From the VxWorks command line,
type:
initLineTrc (port, offset, byteCnt, bufferCnt); where:
port is the physical port you want to diagnose
offset is the byte offset from beginning of the frame to be copied
byteCnt is the number of bytes to be copied
bufferCnt is the number of trace buffers
24. Enable the line trace resources for the specified port. From the VxWorks command line,
type:
enableLineTrc (port, reset); where:
port is the physical port you want to diagnose
reset is set to 1 to reset the write pointer to the first entry;
set to 0 to continue the line trace from the current write pointer
NOTE:
The amount of time to run the line trace procedure is determined
by the user. After the specified amount of time, disable the line
trace.
25. Disable the line trace resources for the specified port. From the VxWorks command line,
type:
disableLineTrc (port); where:
port is the physical port on which you want to disable line tracing
6-4
IAN150/IPP MT
6/30/97
26. View line trace information. From the VxWorks command line, type:
lineTrcShow (port, level, firstEntry, numEntries); where:
port is the physical port for which you want to display information
level is set to 0 to display line trace configurations;
set to 1 to display line trace configurations and the trace buffers
numEntries is the number of entries you want the system to display
27. Disable the line trace and remove the line trace resources. From the VxWorks command line,
type:
killLineTrc (port); where:
port is the physical port on which you want disable line tracing
Preventive Maintenance
•
It is good practice to document and keep a record of normal network operation. An example
would be a topological map of the physical and logical configuration of your network.
•
Routinely monitor and create a record of daily changes in traffic patterns, as some problems
may accompany increased traffic or peak traffic periods.
•
When problems occur, collect on-site performance data as a reference so you can quickly
recognize a problem if it occurs again. When the problem has been resolved, record and
communicate the solution to your colleagues. See Chapters 7 through 18 of this manual for
further information about monitoring your network.
•
Track system changes. Carefully plan and review the proposed changes to prime network
devices. Consider the consequences of intended changes to addresses, circuit parameters,
configurations for networking protocols, and software versions in local or remote prime
network devices. Ensure the changes are appropriate and are entered correctly. See the
Synchrony IAN-150/IPP Reference Manual for information regarding IAN-150 configuration
and programming.
•
Test the communication media for physical-layer problems that are intermittent or chronic.
Conduct tests of the communication media (coaxial cables, twisted pairs, and/or fiber optic
cables) using appropriate monitoring and test devices, such as physical-layer scanners.
Utilize internetworking data analyzers to record higher-layer protocol traffic so that you may
analyze internetworking or interoperability issues. On systems involving wide area networks,
contact your service provider to verify that the data links are intact and functioning properly.
IAN150/IPP MT
6/30/97
6-5
Factory Diagnostics
Each IAN-150 board is tested at the factory before shipping. The same tests that are run at the
factory can be performed in the field using the ascom Timeplex Loader menu for the IAN-150.
The factory test consists of a series of tests performed on dynamic memory, battery backed
RAM, WATCHDOG, and all ports. For IPP, PBUS (PIPE Bus) tests are also performed. PBUS
tests ensure that PBUS hardware on the IPP operates properly. PBUS tests are performed only in
Master slots of the ST-1000/ER-5 chassis. Before you run the tests, external loopback connectors
must be plugged into each port that is being tested. (For IAN-150, in lieu of a loopback
connector the Token Ring port can be connected to an external MAU as long as no other devices
are on the ring.) Refer to Chapter 5, “Utilities and Diagnostics,” for a list of loopback connectors.
To access the ascom Timeplex Loader menu you can either power cycle the IAN-150, or log on
with Superuser access and from the main menu follow the path :
1. Node Status and Control
1. Node Status
then type .RST from the command line of the Node Status screen and press Enter. When the
message
System will start in 10 secs
To stop system start-up, enter two ESCs...
appears on the user interface screen, press Esc twice. The system displays the following menu:
(c)1996 ascom Timeplex Loader
IAN 150 Version 1.0.0 Sep 24 1996
=========================================================
TALK File Transfer
Baud rate:
115200
=========================================================
(G) Start executing flash
(U) Unzip flash files to execution flash
(C) Configure TALK file transfer baud rate
(T) Start TALK load
(D) Default system configuration
(S) Save system configuration to file.
(R) Restore system configuration from file
(L) List flash files
(E) Edit board information
(F) Factory test
(B) Reboot the system
(M) Mon960 menu
Main>
Figure 6-1. Loader Menu
6-6
IAN150/IPP MT
6/30/97
CAUTION:
The Mon960 menu option on the ascom Timeplex Loader menu
provides access to the user interface of the Intel i960 processor.
Do not use this option unless you are a qualified developer or
Customer Support representative!
Type f and press Enter to run the factory diagnostics. The system displays the following menu:
Factory Test Menu
--------------------------------------------------------(E) Execute Factory Test
(C) Execute Continuous Factory Test
(X) Exit to Main Menu
FactoryTest>
Figure 6-2. Factory Test Menu
The factory test consists of a series of diagnostics that are run to test all the board hardware. If
any port fails a diagnostic, the OP LED for that port begins flashing approximately two times per
second, the entire test is aborted, and the system halts. The IAN-150 must then be power-cycled
to continue operation. The factory test also displays the total DRAM tested.
The factory test menu options are described in reverse order in the following paragraphs:
(X) Exit to Main Menu
Returns you to the ascom Timeplex Loader menu.
(C) Execute Continuous Factory Test
Runs one complete cycle of diagnostics, pauses for approximately one minute, resets the IAN150 and reruns the diagnostics. As long as all the diagnostics pass, this continues until Esc is
pressed twice when the message
appears. This action terminates the factory test and causes the Loader Menu to be displayed.
Select option G or B to resume normal operation. (For information on other Loader Menu
options, see Loading or Upgrading System Software in Appendix A of this manual.)
If any diagnostic fails during any cycle, the OP LED for that port begins flashing approximately
two times per second, the entire factory test is aborted, and the system halts. The IAN-150 must
then be power-cycled to resume operation.
IAN150/IPP MT
6/30/97
6-7
(E) Execute Factory Test
When this option is selected, the following events take place:
1. All port LEDs on the IAN-150 or IPP go OFF.
2. The following message appears on the user interface screen:
Calculate Execution Flash Checksum...
Start Execution Flash at 0xc0000584...
FACTORY TESTS INITIATED
3. The OP LED goes ON on all installed physical ports in succession.
4. The TX and RX LEDs on each port flicker as the diagnostic tests are running.
5. If all diagnostics pass, the OP LEDs on all the ports flash ON in sequence, creating a
marquee pattern. This marquee pattern is different from the flashing LED that indicates a
port failure. If there is a Memory, BBRAM, or watchdog failure, all the OP LEDs start to
flash.
6. When a test is conducted, the system displays test status messages on the user interface
screen. Specific messages depend on your system configuration.
If the test is conducted on an IAN-150, the following messages are typical of those that
appear on the user interface screen when the factory tests are successful:
BATTERY BACKED (nvm) RAM PATTERN TEST PASSED
TESTING 16 MB DRAM: PATTERN TEST ..PASSED
CPU WATCHDOG TEST ....................PASSED
STARTING PORT TESTS
TOKEN RING TEST ON PORT 1 .........PASSED
ETHERNET TEST ON PORT 2 ...........PASSED
ASYNC TEST ON PORT 3 ..............PASSED
TOKEN RING TEST ON PORT 1 .........PASSED
ETHERNET TEST ON PORT 2 ...........PASSED
SYNC TEST ON PORT 3 .............. PASSED
SYNC TEST ON PORT 4 ...............PASSED
FACTORY TESTS SUCCESSFULLY COMPLETED
After you complete the factory test, power-cycle the IAN-150.
If any diagnostic on any port fails, the OP LED for that port begins flashing approximately two
times per second, the entire factory test is aborted, and the system halts. The system displays the
word “FAILED” next to the port number that did not pass the test. The IAN-150 must then be
power-cycled to resume operation. After all factory tests are complete, if any failures occurred
the system displays the following message:
FACTORY TESTS REPORT FAILURE: RESET THE BOARD TO RESUME OPERATION
6-8
IAN150/IPP MT
6/30/97
If the test is conducted on an IPP, the following messages are typical of those that appear on the
user interface screen when the factory tests are successful:
BATTERY BACKED (NVM) RAM PATTERN TEST PASSED
TESTING 16 MB DRAM: PATTERN TEST ..PASSED
CPU WATCHDOG TEST ....................PASSED
STARTING PBUS TESTS
PBUS CLOCK PRESENCE TEST ................PASSED
PBUS REGISTER TEST ......................PASSED
FIFO ALMOST EMPTY FLAG TEST..............PASSED
RECEIVE DMA BUSY TEST....................PASSED
INCOMPLETE TRANSMIT TEST.................PASSED
PBUS WATCHDOG TEST .....................PASSED
DATA LOOPBACK TEST UNDER DMA.............PASSED
DATA LOOPBACK WITH 64 bit BUS SEGMENT AB..PASSED
DATA LOOPBACK WITH 64 bit BUS SEGMENT AC..PASSED
DATA LOOPBACK WITH 64 bit BUS SEGMENT BC..PASSED
ALL PBUS TESTS COMPLETED
STARTING PORT TESTS
ASYNC TEST ON PORT 7...............PASSED
ASYNC TEST ON PORT 8...............PASSED
SYNC TEST ON PORT 7................PASSED
SYNC TEST ON PORT 8................PASSED
FACTORY TESTS SUCCESSFULLY COMPLETED
If the IPP is in a slave slot or standby master slot, PBUS tests would be skipped and the system
displays the following message:
IPP in SLAVE SLOT : PBUS TESTS SKIPPED
or
IPP IN MASTER_B SLOT : PBUS TESTS SKIPPED
After you complete the factory test, power-cycle the IPP.
IAN150/IPP MT
6/30/97
6-9
If a factory test fails and all the LEDs are blinking approximately two times per second, there is a
memory failure, watchdog failure or PBUS failure. The entire factory test is aborted, and the
system halts. The system displays the word “FAILED” next to the diagnostic test that failed. If
the OP LED for a specific port begins flashing approximately two times per second, it means the
specific port has failed the test. The entire factory test is aborted, and the system halts. The
system displays the word “FAILED” next to the port number that did not pass the test. In the
event of either type of failure, the IPP must then be power-cycled to resume operation. After all
factory tests are complete, if any failures occurred the system displays the following message:
FACTORY TESTS REPORT FAILURE: RESET THE BOARD TO RESUME OPERATION
6-10
IAN150/IPP MT
6/30/97
Chapter
7
Ethernet Monitoring
NOTE:
The information in this chapter applies only to the Synchrony
IAN-150.
The IAN-150 provides information to help monitor and troubleshoot Ethernet operations. The
IAN-150 is used to monitor Ethernet ports located on both local and remote nodes. You can
access the remote IAN-150 without using telnet because the local console acts as a SNMP
(Simple Network Management Protocol) agent. The IPA (Internet Protocol Address) command
changes to the target IP (Internet Protocol) address of each SNMP command to allow you to
access the remote node. This allows you to read and update remote screen information. This
chapter describes Ethernet monitoring and troubleshooting capabilities.
Ethernet Monitoring Tips
display or table, the values in the default template appear.
NOTE:
If you access a remote node, the current IP address set by the IPA
command displays on the main menu. The IPA command will
default to the local node if you issue the command without any
parameters.
To view current values, refresh the screen by issuing either a Read or Read Next command from
the command line. The screen displays the statistics that applied when the command was
executed. To view current values for statistical displays, type < . > R and press Enter. To view
current values for tables, type < . > N and press Enter.
Each table can be sorted by key fields, which are located in the first line of every table. To
display information about a specific table entry, refresh the screen then enter the appropriate
identifying data in the first line of the table, then execute a Read command. The screen displays
that table entry as the first table entry.
the number of seconds between screen updates. Press < . >, then type MON x and press Enter.
To end the Monitor process and remain at this screen, press < . >.
To exit the display, press < \ > or Esc.
IAN150MT
6/30/97
7-1
Chapter 7, Ethernet Monitoring
Ethernet Port Status
The Ethernet Port Status display provides general statistics on Ethernet port operation. To select
Ethernet Port Status monitoring from the Main Menu, follow the path:
1.Status and Control
2. Port
2. Ethernet
or enter SPE or 122 from the command line of any menu or screen and press Enter. The system
displays the following screen:
1.2.2 [SPE] Ethernet Port Status
Port
000
IN
Alignment Errors
FCS (CRC) Errors
Internal MAC Errors
Frames Exceeding MTU
0
0
0
0
OUT
Single Collisions
Multiple Collisions
Frames Deferred (Busy)
Late Collisions
Excessive Collisions
Internal MAC Errors
Carrier Sense Lost
0
0
0
0
0
0
0
Figure 7-1. Ethernet Port Status Screen
Ethernet Port Status parameters are described in the following paragraphs. Corresponding MIB
values appear in brackets next to the parameter names. To view current values for a specific
Ethernet port, enter the port number in the Port field, then refresh the screen by typing < . > R
and pressing Enter. The screen displays the statistics that applied when the command was
executed. To exit the display, press < \ > or Esc.
Port [dot3StatsIndex]
Identifies the Ethernet port under examination. The IAN-150 comes with a maximum of six
physical ports and an expansion slot that can hold up to two additional ports. The ports are
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Console Port
Token Ring port
Ethernet port
WAN port
WAN port
WAN port
The only valid Ethernet ports on the IAN-150 are Port 2 and, if the Ethernet expansion card is
installed, Port 6.
7-2
IAN150/IPP MT
6/30/97
Chapter 7, Ethernet Monitoring
Alignment Errors [dot3StatsAlignmentErrors]
Contains a count of the frames received on the selected port that are not an integral number of
octets in length and do not pass the FCS check.
FCS (CRC) Errors [dot3StatsFCSErrors]
Displays the number of frames received on a particular port that are an integral number of octets
in length but do not pass the FCS check. Frame Check Sequence (FCS) is used to check the
integrity of each block of data. A 32-bit field that contains a FCS value is added to the end of
each frame during transmission. The FCS value is computed using CRC32 computation. At the
receiving end, a similar calculation is performed and a comparison made.
Internal MAC (Receive) Errors [dot3StatsInternalMACReceiveErrors]
Contains a count of frames for which were not received due to an internal MAC sub-layer receive
error. A frame is included in this count if it is not counted by either the Frames Exceeding MTU
parameter, the Alignment Error parameter, or the FCS Errors parameter. Increasing the buffer
count [pciConfIntfBufCnt] may reduce this error.
Frames Exceeding MTU [dot3StatsFrameTooLongs]
Indicates when a frame has exceeded the Maximum Transfer Unit (MTU) length of 1500 bytes
for Ethernet transmission.
Single Collisions [dot3StatsSingleCollisionFrames]
Contains a count of successfully transmitted frames on the selected port for which transmission
was inhibited by exactly one collision.
Multiple Collisions [dot3StatsMultipleCollisionFrames]
Contains a count of successfully transmitted frames on the selected port for which transmission
was inhibited by more than one collision.
Frames Deferred (Busy) [dot3StatsDeferredTransmissions]
Contains a count of frames for which the first transmission attempt on the selected port was
delayed because the medium was busy. Frames involved in collisions are not included in this
count.
Late Collisions [dot3StatsLateCollisions]
Contains a count of the number of times that a collision has been detected on the selected port
later than 512 bit-times into the transmission of a packet.
Excessive Collisions [dot3StatsExcessiveCollisions]
Contains a count of frames for which transmission on the selected port failed due to excessive
collisions.
Internal MAC (Transmit) Errors [dot3StatsInternalMACTransmitErrors]
Contains a count of frames for which transmission on the selected port failed due to an internal
MAC sub-layer transmit error. A frame is included in this count if it is not counted by either the
Late Collisions parameter, the Excessive Collisions parameter, or the Carrier Sense Lost
parameter.
Carrier Sense Lost [dot3StatsCarrierSenseErrors]
Contains a count of the number of times the carrier sense condition was lost or never asserted
when attempting to transmit a frame on this port.
IAN150/IPP MT
6/30/97
7-3
Chapter
8
Token Ring Monitoring
NOTE:
IAN-150.
The IAN-150 provides extensive capabilities, through the use of various informational displays,
to help you monitor and troubleshoot Token Ring operations. This chapter describes these
capabilities.
Token Ring Monitoring Tips
display or table, the system displays the default template values. To view current values, refresh
the screen by issuing either a Read or Read Next command from the command line. The screen
statistical displays, type < . > R and press Enter. To see current values for tables, type < . > N
and press Enter.
Each table can be sorted by key fields located in the first line of every table. To display
information about a specific table entry, enter the appropriate identifying data in the first line of
the table after you have refreshed the screen, then execute a Read command. The screen displays
IAN150/IPP MT
6/30/97
8-1
Chapter 8, Token Ring Monitoring
Token Ring Port Status
The Token Ring Port Status display provides general statistics on Token Ring port operation. To
select Token Ring Port Status, from the Main Menu, follow the path:
2. Port
3. Token Ring
or enter SPT or 123 from the command line of any menu or screen and press Enter. The system
1.2.3 [SBPT] Token Ring Port Status
Port
000
Admin
Ring
Ring
Open
Ring
Status
Status
State
Status
Speed
NOT OPERATIONAL
0
OPENED
OPEN
UNKNOWN
Line Errors
AC Set Bit Problems
Internal Errors
Receive Congestion
Token Errors
Hard Errors
Transmit Beacons
Lobe Wire Faults
Singles
0
0
0
0
0
0
0
0
0
Burst Errors
Transmit Abort Error
Lost Frames
Frame Copy Errors
Soft Errors
Signal Loss
Ring Recoveries
Removes
Frequency Errors
0
0
0
0
0
0
0
0
0
Figure 8-1. Token Ring Port Status Screen
The following paragraphs describe token ring port status parameters. Corresponding MIB values
appear in brackets next to the parameter names. To view current values for a specific Token Ring
port, enter the port number in the Port field, then refresh the screen by typing < . > R and
pressing Enter. The screen displays the statistics that applied when the command was executed.
Port [dot5RingPort]
Identifies the Token Ring port under examination. The IAN-150 comes with a maximum of six
physical ports and an expansion slot that can hold up to two additional ports. The ports are
Port 0
Port 1
Port 2
Port 3
Port 4
Port 5
Console Port
Token Ring port
Ethernet port
WAN port
WAN port
WAN port
The only valid Token Ring ports on the IAN-150 are Port 1 and, if the appropriate expansion
card is installed, Port 6.
8-2
IAN150/IPP MT
6/30/97
Admin Status [ifAdminStatus]
This field describes the current status of the Token Ring port. Valid values:
NOT OPERATIONAL
The port has not been enabled.
OPEN
Corresponds to a configured Admin Status of UP.
RESET
The port is in the process of resetting.
CLOSED
Corresponds to a configured Admin Status of DOWN.
Ring Status [dot5RingStatus]
Displays a numerical value that refers to the current port status. This field can be used to
diagnose fluctuating problems that can occur after a station has been successfully added to the
ring. The object’s value is the sum of the values associated with each applicable condition. Valid
values are:
0
No problem detected
32
Ring recovery
64
Single station
256
Remove received
512
Reserved
1024 Auto removal error
2048 Lobe wire fault
4096 Transmit beacon
8192 Soft error
16384 Hard error
32768 Signal loss
131072 No status, open not completed
Before an open is completed, the object has the value 131072, which indicates no status. The
dot5RingState and dot5RingOpenStatus objects (see below) allow you to debug problems when
the station can not even enter the ring.
Ring State [dot5RingState]
Indicates the current port state with respect to entering or leaving the ring. Valid settings:
OPENED, CLOSED, OPENING, CLOSING, OPEN FAILURE, and RING FAILURE.
Opening and closing operations take approximately one millisecond to complete; therefore, it is
unlikely that OPENING or CLOSING will appear in this field. OPEN FAILURE indicates that
an Open command was received by the port, but was not successfully executed. RING FAILURE
indicates a more catastrophic malfunction than OPEN FAILURE.
Open Status [dot5RingOpenStatus]
Indicates the success or reason for failure of the most recent attempt to enter the ring. Valid
values:
NO OPEN
BAD PARAM
LOBE FAILED
SIGNAL LOSS
IAN150/IPP MT
6/30/97
No Open command has been attempted.
One or more of the parameters passed with the Open command is
invalid.
The port is unable to detect a MAU.
A signal loss condition has been detected at the receiver input
during the Open process.
8-3
INSERT TIMEOUT
RING FAILED
BEACONING
DUPLICATE MAC
REQUEST FAILED
REMOVE RECEIVED
LAST OPEN
The port failed to insert onto the ring before the insertion timer
expired.
The port timed out while attempting a ring purge after becoming
the active monitor. (The port was unable to receive its own ring
purge MAC frames.)
The port received a beacon MAC frame after physically inserting
into the ring.
The port has found that another station on the ring is already using
the MAC address that this port wants to use.
The port has determined that a Ring Parameter Server (RPS) is
present on the ring but does not respond to a Request Initialization
MAC frame.
The port received a Remove Adapter MAC frame during the
insertion process.
The last Open attempt was successful.
Ring Speed [dot5RingSpeed]
Indicates the ring speed at the next insertion into the ring. Valid values: UNKNOWN, ONE
MEGABIT, FOUR MEGABIT, and SIXTEEN MEGABIT.
Line Errors [dot5StatsLineErrors]
Displays a count of the total Line Errors since startup. The value is incremented when a frame or
token is copied or repeated by a station.
Burst Errors [dot5StatsBurstErrors]
Displays a count of the total number of burst errors since startup. The value is incremented when
a station detects the absence of transitions for five half-bit timers (burst-five errors).
AC Set Bit Problems [dot5StatsACErrors]
Displays a count of the total number of AC bit errors. It denotes a station that cannot set the AC
bits properly.
Transmit Abort Error [dot5StatsAbortTransErrors]
Displays a count of the total number of abort transmission errors. The counter is incremented
each time a station sends an abort delimiter while transmitting.
Internal Errors [dot5StatsInternalErrors]
Displays a count of the total number of internal errors.
Lost Frames [dot5StatsLostFrameErrors]
Displays a count of the total number of lost frames (frame errors) since startup. The counter is
incremented each time a transmitting station in strip mode does not receive the trailer of the
frame before the TRR timer goes off.
Receive Congestion [dot5StatsReceiveCongestions]
Displays a count of the total number of congestion errors. The counter is incremented when a
station recognizes a frame addressed to its specific address but has no available buffer space,
indicating that the station is congested.
8-4
IAN150/IPP MT
6/30/97
Frame Copy Errors [dot5StatsFrameCopiedErrors]
Displays a count of the total number of frame copy errors since startup.
Token Errors [dot5StatsTokenErrors]
Displays a count of the total number of token errors. The counter is incremented each time a
station, acting as the active monitor, recognizes an error condition that requires a token
transmitted.
Soft Errors [dot5StatsSoftErrors]
Displays a count of the total number of soft errors detected by this port. The number corresponds
to the number of Report Error MAC frames that this port has transmitted.
Hard Errors [dot5StatsHardErrors]
Displays a count of the total number of hard errors detected by this port. The number corresponds
to the number of times that this port has detected an immediately recoverable fatal error. It
denotes the number of times the port either transmitted or received beacon MAC frames.
Signal Loss [dot5StatsSignalLoss]
Displays a count of the total number of times that this port detected a loss of signal condition
from the ring.
Transmit Beacons [dot5StatsTransmitBeacons]
Displays a count of the total number of times that this port has transmitted a Beacon frame.
Ring Recoveries [dot5StatsRecoverys]
Displays a count of the total number of Claim Token MAC frames received or transmitted after
the port received a Ring Purge MAC frame. This counter signifies the number of times the ring
was purged and was recovered back into a normal operating state.
Lobe Wire Faults [dot5StatsLobeWires]
Displays a count of the total number of times that this port detected an open or short circuit in the
lobe data path.
Removes [dot5StatsRemoves]
Displays a count of the total number of times that this port received a Remove Ring Station
MAC frame request.
Singles [dot5StatsSingles]
Displays a count of the total number of times that this port sensed that it was the only station on
the ring. This condition occurs each time this port is the first one up on a ring.
Frequency Errors [dot5StatsFreqErrors]
Displays a count of the total number of times that this port detected that the frequency of the
incoming signal differs from the expected frequency by more than the IEEE 802.3 standard.
IAN150/IPP MT
6/30/97
8-5
Chapter
9
Bridge Monitoring
NOTE:
references ot the IAN-150 apply to the IPP unless otherwise
noted.
The IAN-150 provides you with the tools necessary to monitor bridge status for a variety of
bridging methods, including Bridge Relay Element (BRE) Virtual and Physical Port Bridging,
General (Transparent) Bridging, Spanning Tree Bridging, and Source Route Bridging. This
chapter describes bridge monitoring capabilities.
Bridge Monitoring Tips
display or table, the system displays values in the default template. To view current values,
refresh the screen by issuing either a Read or Read Next command from the command line. The
screen displays the statistics that applied when the command was executed. To view current
values for statistical displays, type < . > R and press Enter. To see current values for tables, type
< . > N and press Enter.
information about a specific table entry, refresh the screen, enter the appropriate identifying data
in the first line of the table, then issue a Read command. The screen displays that table entry as
the first table entry.
To automatically update and continuously display the most current statistics, issue a Monitor
IAN150/IPP MT
6/30/97
9-1
Chapter 9, Bridge Monitoring
Bridging Status Menu
The Bridging Status menu provides categories about IAN-150 bridge monitoring. To select the
Bridging Status screen, from the Main Menu, follow the path:
3. Bridging
or type SB or 13 from the command line of any menu or screen and press Enter. The system
1.3 [SB] Bridging Status
1. BRE Ports
2. General Bridging
3. Spanning Tree Algorithm Protocol (STA/P)
4. Source Route
5. Bridging Tables
Figure 9-1. Bridging Status Menu
There are five bridging monitoring options:
•
BRE Ports - This option allows you to monitor the Bridge Relay Element (BRE) physical
and virtual ports. Bridge Relay Element (BRE) Status is described later in this chapter.
•
General Bridging - This option provides the current status of transparent bridging
operations for the port you select.
•
Spanning Tree Algorithm Protocol (STA/P) - This option allows you to monitor the
operation of the Spanning Tree Protocol for a bridge domain as well as the status of a
specific port that is running Spanning Tree protocol.
•
Source Route - This option shows the number of specifically routed frames received and
transmitted, and the number of All Route Explorer frames received and transmitted, and the
number of Spanning Tree Explorer frames received and transmitted by the port you selected,
as well as other source-route bridging statistics.
•
Bridging Tables - This option enables you to view a Bridge Forwarding Table, a Source
Route Encapsulation Table, and a Source Route-Transparent Bridge (SR-TB) Translation
Table.
Each of these options is described in the following sections.
9-2
IAN150/IPP MT
6/30/97
General Bridging Status
The General Bridging Status screen provides current statistics about transparent bridging
operations. To access the General Bridging Status screen, from the Main Menu, follow the path:
3. Bridging
2. General Bridging
or enter SBG or 132 from the command line of any menu or screen and press Enter. The system
1.3.2 [SBB] General Bridging Status
Port
001
Maximum Info Size
Octets
Frames
Filtered
Discards
FILTERED
Address
Mask
Static
0
IN
0
0
0
0
0
0
0
DISCARD
Error
Transmit Delay
MTU Exceeded
OUT
0
0
0
0
0
0
0
0
0
0
Figure 9-2. General Bridging Status Display
The following paragraphs describe general bridging status parameters. Corresponding MIB
for a specific port, enter the port number in the Port field, then refresh the screen by typing < . >
R and pressing Enter. The screen displays the statistics that applied when the command was
Port [polStatTBPort]
Identifies the port being monitored.
Maximum Info Size [dot1dTBPortMaxInfo]
Contains the Maximum Transmission Unit (MTU) of the frames being sent by this port.
Octets IN/OUT [polStatTBPortInOctets] [polStatTBPortOutOctets]
Contains the total number of bytes received (Octets IN) and forwarded (Octets OUT) by this
port.
Frames IN/OUT [dot1dTBPortInFrames] [dot1dTBPortOutFrames]
Contains the number of frames received (Frames IN) and forwarded (Frames OUT) by this
port.
IAN150/IPP MT
6/30/97
9-3
Filtered IN/OUT [polStatTBPortInFilters] [polStatTBPortOutFilters]
Contains the number of filtered frames received (Filtered IN) and not forwarded (Filtered OUT)
at this port.
Discards IN/OUT [polStatTBPortInDiscards] [polStatTBPortOutDiscards]
Contains the number of frames discarded when received (Discards IN) and discarded before
(Discards OUT) forwarding by this port.
Filtered Address IN/OUT [polStatTBPortInAddrFilters]
[polStatTBPortOutAddrFilters]
Contains the number of incoming or source (Filtered Address IN) and outgoing or destination
(Filtered Address OUT) MAC address pairs that were filtered. This type of filtering is on a
device level and is applied to all ports at the source and/or destination interface.
Filtered Mask IN/OUT [polStatTBPortInMaskFilters]
[polStatTBPortOutMaskFilters]
Contains the number of incoming (Filtered Mask IN) and outgoing (Filtered Mask OUT)
frames that were filtered using a 32-bit bridge mask filter. If a sequence of bits in the frame
matches the sequence of bits in the bridge mask filter table, and the Access parameter from the
Bridge Mask Filter Configuration display (Screen 2.3.4.2) is set to PERMIT for this port, then
the frame is allowed to pass out through the destination port interface. However, if the Access
parameter is set to DENY, then the frame will be dropped at the source or destination port. An
offset of up to 255 bytes starting at the beginning of the frame locates the value to be checked.
Filtered Static IN/OUT [polStatTBPortInStaticFilters]
[polStatTBPortOutStaticFilters]
Contains the number of incoming (Filtered Static IN) and outgoing (Filtered Static OUT)
destination MAC addresses that were filtered. For bridge traffic, static filters filter destination
MAC addresses associated with pre-designated ports. If the Access parameter from the Bridge
Static Filter Configuration Display (Screen 2.3.4.3) is set to PERMIT for this port, the affected
frames are permitted to pass through the destination port. If the Access parameter is set to
DENY, the affected frames are dropped at the source or destination port.
Discard Error [polStatTBPortOutErrorOnDiscards]
Contains the total number of frames discarded for any reason at this port.
Discard Transmit Delay [polStatTBPortDelayExceededDiscards]
Contains the number of frames discarded because the maximum bridge transmission delay time
was exceeded.
Discard MTU Exceeded [polStatTBPortMTUExceededDiscards]
Contains the number of frames discarded because frame size exceeded the Maximum
Transmission Unit limit.
9-4
IAN150/IPP MT
6/30/97
Spanning Tree (STA/P) Status Menu
Spanning Tree Algorithm Protocol (STA/P) provides an algorithm that determines the most costeffective method of transferring data from bridge to bridge. The Spanning Tree Status Menu
provides categories relating to the STA/P monitoring. To access the Spanning Tree Status screen,
3. Bridging
or enter SBS or 133 from the command line of any menu or screen and press Enter. The system
1.3.3 [SBS] Spanning Tree Status
1. Protocol
2. Port
Figure 9-3. Spanning Tree Status Menu
There are two monitoring categories for STA/P:
•
Protocol - provides information about device-wide STA/P features.
•
Port - provides information relating to STA/P functionality for a specific port.
Each of these categories is described in the following sections.
IAN150/IPP MT
6/30/97
9-5
Spanning Tree Protocol Status
The Spanning Tree Protocol Status monitoring screen provides information about STA/P features
that are applied device-wide in the IAN-150. To access the Spanning Tree Protocol Status screen,
3. Bridging
1. Protocol
or enter SBST or 1331 from the command line of any menu or screen and press Enter. The
1.3.3.1 [SBST] Spanning Tree Protocol Status
Bridging Domain ID
01
DESIGNATED ROOT
Bridge ID 00:00:00:00:00:00:00:00
Max Age (sec)
0
Hello Time (sec)
0
Forward Delay (sec)
0
Root Path Cost
0
Root Port
0
Protocol Spec
UNKNOWN
LOCAL BRIDGE
Bridge ID 00:00:00:00:00:00:00:00
Max Age (sec)
0
Hello Time (sec)
0
Forward Delay (sec)
0
Topology Change Detected
Topology Change
Topology Change Time (sec)
Hold Time (sec)
Time Since Last Topology Change
Topology Changes Since Last Initialization
FALSE
FALSE
0
0
0000:00:00
0
Figure 9-4. Spanning Tree Protocol Status Display
The following paragraphs describe spanning tree protocol status parameters. Corresponding MIB
values, where applicable, appear in brackets next to the parameter names. To view current values,
issue a Read command from the command line by typing < . > R and pressing Enter. The screen
> or Esc.
Bridging Domain ID [polStatStapBDMId]
The ID for a logical grouping of bridged LAN traffic isolated from the bridged traffic in other
bridging domains within the same IAN-150.
Protocol Spec [polStatStapBDMProtoSpec]
Indicates whether this bridge conforms to IEEE 802.1d standards or to DEC LAN Bridge 100
specifications. Possible values for this field are: UNKNOWN, DECLB100, and IEEE 802.1D.
The IAN-150 currently supports IEEE 802.1D only.
9-6
IAN150/IPP MT
6/30/97
DESIGNATED ROOT:
Bridge ID [polStatStapBDMRootId]
Contains the eight octet, hexadecimal identifier for the designated (assumed) root bridge.
Max Age (sec) [polStatStapBDMMaxAge]
Contains the maximum age in seconds of received protocol information before it is discarded at
the (assumed) root bridge.
Hello Time (sec) [polStatSTAPBDMHelloTime]
Contains the time in seconds before transmission of confirmation Bridge Protocol Data Units by
the (assumed) root bridge.
Forward Delay (sec) [polStatStapBDMForwardDelay]
Contains the time in seconds spent by the (assumed) root bridge in the listening state, while
moving from the blocking state to the learning state.
Root Path Cost [polStatStapBDMRootPathCost]
Contains the cost of the path to the root bridge from the local bridge.
Root Port [polStatStapBDMRootPort]
Identifies the local port that offers the lowest cost path to the root bridge.
LOCAL BRIDGE:
Bridge ID [polStatStapBDMLocalId]
Contains the eight octet, hexadecimal identifier of the local bridge (as derived from the unique
bridge address and priority).
Max Age (sec) [polStatStapBDMBridgeMaxAge]
Contains the maximum age in seconds, of received protocol information before it is discarded at
the local bridge, when it is the root bridge.
Hello Time (sec) [polStatStapBDMBridgeHelloTime]
Contains the time in seconds before transmission of confirmation Bridge Protocol Data Units by
the local bridge when the local bridge is, or is attempting to become the root bridge.
Forward Delay (sec) [polStatStapBDMBridgeForwardDelay]
Contains the time in seconds spent in the listening state while moving from the blocking state to
the learning state by the local bridge, when the local bridge is or is attempting to become, the
root bridge.
Topology Change Detected [polStatStapBDMTopChgDetected]
Contains the setting of the topology change acknowledgment flag in the next configuration
Bridge Protocol Data Unit (BPDU) to be transmitted from the associated port. Available values
for this field are TRUE and FALSE.
Topology Change [polStatStapBDMTopChg]
Contains the setting of the topology change flag in the configuration Bridge Protocol Data Unit
(BPDU) to be transmitted by the local bridge on LANs from which the local bridge is the
designated bridge. Available values for this field are TRUE and FALSE.
IAN150/IPP MT
6/30/97
9-7
Topology Change Time (sec) [polStatStapBDMTopChgTime]
Contains the time period in seconds following detection of a topology change during which
Bridge Protocol Data Units (BPDUs) are transmitted with the topology change flag set by the
local bridge, when the local bridge is the root bridge.
Hold Time (sec) [polStatStapBDMHoldTime]
contains the minimum time period in seconds between transmissions of configuration Bridge
Protocol Data Units (BPDUs) through a bridge port. A maximum of two confirmation BPDUs
can be transmitted in a Hold Time interval.
Time Since Last Topology Change [polStatStapBDMTimeSinceTopChg]
Contains the elapsed time (hours:minutes:seconds) since the topology change flag was last set to
TRUE.
Topology Changes Since Last Initialization [polStatStapBDMTopChgCount]
Contains the number of times the topology change flag for the local bridge was set since the
bridge was powered on or initialized.
Spanning Tree Port Status
The Spanning Tree Port Status monitoring screen provides information about STA/P features that
are applied to a specific port in the IAN-150. To access the Spanning Tree Port Status screen
3. Bridging
2. Port
or enter SBSP or 1332 from the command line of any menu or screen and press Enter. The
1.3.3.2 [SBSP] Spanning Tree Port Status
Port
STAP State
Designated
Designated
Designated
Designated
Forwarding
000
Port State
UNKNOWN
DISABLED
Root
00:00:00:00:00:00:00:00
Root Path Cost
0
Root Bridge
00:00:00:00:00:00:00:00
Root Port
0000
State Transitions
0
Config BPDUs
TCN BPDUs
Discards
NetUps
NetDowns
IN
0
0
0
0
0
OUT
0
0
ATTEMPTS
0
0
Figure 9-5. Spanning Tree Port Status Display
9-8
IAN150/IPP MT
6/30/97
The following paragraphs describe Spanning Tree Port Status parameters. Corresponding MIB
Port [dot1dStpPort]
Port State [dot1dStpPortState]
Indicates whether or not the designated port is participating in STA/P. Valid values: UP,
DOWN, and UNKNOWN. If the port is configured to enable STA/P, the parameter will read
UP. If the port is not configured to enable STA/P, the parameter will read DOWN.
STAP State [polStatStapPortIntfState]
Indicates the status of STA/P on the designated port. Valid settings: Disabled, Listening,
Learning, Forwarding, and Blocking.
Designated Root [dot1dStpPortDesignatedRoot]
Contains the eight octet, hexadecimal identifier of the bridge recorded as the root in the Root
Identifier parameter of configuration BPDUs, transmitted by the Designated Bridge for the LAN
to which the port is attached.
Designated Root Path Cost [dot1dStpPortDesignatedCost]
Indicates the cost in time (seconds) of the path to the root, offered by the Designated Port on the
LAN to which this port is attached.
Designated Root Bridge [dot1dStpPortDesignatedBridge]
Contains the eight octet, hexadecimal identifier of the bridge that is assumed to be the
Designated Bridge for the LAN associated with the port. This parameter is used together with
the Designated Port and Port Identifier parameters for the port to ascertain whether this port
should be the Designated Port for the LAN to which it is attached.
Designated Root Port [dot1dStpPortDesignatedPort]
Contains the port identifier of the bridge port assumed to be the Designated Port for the LAN
associated with the port. This parameter is used together with the Designated Root Bridge to
ascertain whether this port should be the Designated Port for the LAN to which it is attached.
Forwarding State Transitions [dot1dStpPortForwardTransitions]
Indicates the number of times the STAP State has changed from Forwarding to one of the other
states, plus the number of times the state has changed from one of the other states to Forwarding.
Config BPDUs IN/OUT/ATTEMPTS [polStatStapPortConfigRxs]
[polStatStapPortConfigTxs] [polStatStapPortConfigAtemps]
Contains the number of Bridge Protocol Data Units (BPDUs) received (Config BPDUs IN),
transmitted (Config BPDUs OUT), and attempted (Config BPDUs ATTEMPTS) on this port.
TCN BPDUs IN/OUT/ATTEMPTS [polStatStapPortTCNRxs]
[polStatStapPortTCNTxs] [polStatStapPortTCNAtempts]
Indicates the number of Topology Change Notification (TCN) BPDUs received (TCN BPDUs
IN), transmitted (TCN BPDUs OUT), and received (TCN BPDUs ATTEMPTED) on this port.
IAN150/IPP MT
6/30/97
9-9
Discards [polStatStapPortDiscards]
Indicates the number of received messages that were discarded by this port.
NetUps [polStatStapPortNetUpRXS]
Indicates the number of NETUP messages received by this port.
NetDowns [polStatStapPortNetDnRXS]
Indicates the number of NETDOWN messages received by this port.
Source Route Bridging Status
Unlike transparent bridging, which depends upon bridge intelligence, the source route (SR)
bridging method requires the originating workstation (source) determine the routing path. The
Source Route Bridging Status screen provides source route bridging statistics about a specific
port. To access the Source Routing Bridging Status screen from the Main Menu, follow the path:
3. Bridging
4. Source Route
or enter SBR or 134 from the command line of any menu or screen and press Enter. The system
1.3.4 [SBR] Source Routing Bridging Status
Port
001
Invalid RIFs
Hop Exceeded
SPECIFICALLY ROUTED FRAMES
Octets
Frames
Discards
ALL ROUTE EXPLORER
Octets
Frames
Discards
Hop Exceeded
Duplicate Lan ID
SPANNING TREE EXPLORER
Octets
Frames
Discards
Hop Exceeded
Tree Error
0
0
IN
0
0
0
Duplicate RIFs
Lan ID Mismatches
OUT
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Figure 9-6. Source Routing Bridging Status Display
The following paragraphs describe source routing bridging parameters. Corresponding MIB
Port [dot1dSRPort]
9-10
IAN150/IPP MT
6/30/97
Invalid RIFs [dot1dSRPortSegmentMisMatchDiscards]
Indicates the number of spanning tree explorer frames that were discarded because of invalid
Routing Information Fields (RIFs).
Duplicate RIFs [dot1dSRPortDuplicateSegmentDiscards]
Indicates the number of spanning tree explorer frames that were discarded because the LAN ID
already appeared in the Routing Information Field (RIF).
Hops Exceeded [dotIdSRPortHop-CountExceededDiscards]
Indicates the number of explorer frames received on an associated port that were discarded
because the number of route designators in the routing information exceeded the RD limit.
LAN ID Mismatches [dot1dSRPortLanIdMisMatchs]
Indicates the number of spanning tree explorer frames that were discarded because the last LAN
ID in the routing information did not match the LAN ID of the input port.
SPECIFICALLY ROUTED FRAMES:
Octets IN/OUT [polStatSRPortSRFInOctets]
[polStatSRPortSRFOutOctets]
Contains the number of valid octets received (Octets IN) and forwarded (Octets OUT) for
specifically routed frames.
Frames IN/OUT [dot1dSRPortSpecInFrames]
[dot1dSRPortSpecOutFrames]
Contains the number of valid specifically routed frames received (Frames IN) and forwarded
(Frames OUT).
Discards [polStatSRPortSRFInDiscards]
Indicates the number of invalid specifically routed frames that were received and discarded.
ALL ROUTE EXPLORER:
Octets IN/OUT [polStatSRPortAPEInOctets]
[polStatSRPortAPEOutOctets]
Contains the octet count for all-route explorer frames received (Octets IN) and forwarded
(Octets OUT) at this port.
Frames IN/OUT [dot1dSRPortAPEInFrames]
[dot1dSRPortAPEOutFrames]
Contains the number of all-route explorer frames received (Frames IN) and forwarded (Frames
OUT) at associated MAC.
Discards [polStatSRPortAPEInDiscards]
Indicates the total number of all-route explorer frames received that were discarded.
Hops Exceeded [polStatSRPortAPEHopCountExceededDiscards]
Contains the number of all-route explorer frames received on an associated port that were
discarded because the number of route designators in the routing information would have
exceeded the RD limit.
IAN150/IPP MT
6/30/97
9-11
Duplicate LAN ID [polStatSRPortAPEDuplicateLanIds]
Contains the number of Spanning Tree explorer frames that were discarded because the LAN-out
ID already appeared in the Routing Information Field (RIF).
SPANNING TREE EXPLORER:
Octets IN/OUT [polStatSRPortSteInOctets]
[polStatSRPortSTEOutOctets]
Contains the total number of spanning tree explorer octets received (Octets IN) and forwarded
(Octets OUT) by the source-route bridging port.
Frames IN/OUT [dot1dSRPortSteInFrames]
[dot1dSRPortSTEOutFrames]
Contains the number of spanning tree explorer frames received (Frames IN) and forwarded
(Frames OUT) at the source-route bridging port.
Discards [polStatSRPortSteInDiscard]
Contains the number of spanning tree explorer frames discarded at the source-route bridging port.
Hops Exceeded [polStatSRPortSteHopCountExceededDiscards]
Contains the number of spanning tree explorer frames received on an associated source routing
port that were discarded because the number of route designators in the routing information
exceeded the route designators limit.
Tree Error [polStatSTEPortSteTreeErrors]
Contains the total number of Spanning Tree Explorer (STE) frames dropped when the interface is
configured for SRT and STAP is set for BLOCKING.
Bridge Relay Element (BRE) Statistics
The Bridge Relay Element (BRE) Statistics menu provides categories about BRE monitoring. To
access the Bridge Relay Element Statistics menu from the Main Menu, follow the path:
3. Bridging
1. BRE Ports
or enter SBB or 131 from the command line of any menu or screen and press Enter. The system
1.3.1 [SBB] Bridge Relay Element Statistics
1. BRE Port Statistics
2. BRE Physical Port Statistics
3. BRE Forwarding Table
4. BRE Routing Table
5. BRE Adjacency Table
Figure 9-7. Bridge Relay Element Statistics Menu
9-12
IAN150/IPP MT
6/30/97
There are five BRE monitoring categories:
•
BRE Port Statistics - provides statistics about BRE virtual ports.
•
BRE Physical Port Statistics - provides information about BRE physical ports.
•
BRE Forwarding Table - provides learned information about other BRE bridges in the
VLAN.
•
BRE Routing Table - provides routing information about other BRE bridges in the VLAN.
•
BRE Adjacency Table - provides reachability information about BRE bridges in the VLAN.
BRE Port Statistics
BRE Port Statistics provide current statistics on BRE virtual ports. To access the BRE Port
Statistics screen, from the Main Menu, follow the path:
3. Bridging
1. BRE Ports
1. BRE Port Statistics
or type SBBE or 1311 from the command line of any menu or screen and press Enter. The
1.3.1.1 [SBBE] BRE Port Statistics
Port
TSF Packets
EF Packets
SRF Packets
BPDU Packets
BDRUs
BDHellos
TSF Discards
00
BRE Bridge Number
OUT
OWN
0
0
0
0
0
0
0
0
0
0
0
0
0
IN
0
0
0
0
0
0
0
No Known Bridges
No Routes
Hello Bad MTU
Hello Dup BN
Fragment OKs
Fragment Creates
Reassembly OKs
Reassembly Requests
Switch OKs
No Source IP
Unknown Route Des
0
0
0
0
0
0
0
0
0
0
0
00000000
FILTERED
0
0
0
No Blocks Avail
No Adjacency
Port Dn Discards
Hello Bad BTL
Fragment Fails
TTL Expired
Reassembly Fails
Reassemby Timeouts
Switch Fails
Alloc Fails
Send Failures
0
0
0
0
0
0
0
0
0
0
0
Figure 9-8. BRE Port Statistics Display
The following paragraphs describe BRE Port Statistics parameters. Corresponding MIB values,
where applicable, appear in brackets next to the parameter names. To view current values for a
specific port, enter the port number in the Port field, then refresh the screen by typing < . > R and
IAN150/IPP MT
6/30/97
9-13
To view additional BRE bridge information for the selected port, type < . > N and press Enter.
Port [polStatBreIntfPort]
BRE Bridge Number [polStatBreIntfBreBn]
Contains the eight digit, hexadecimal identifier of a particular BRE bridge.
TSF Packets IN/OUT [polStatBreIntfProcessdIns]
[polStatBreIntfCountOuts]
Contains the number of transparent spanning tree frames received (TSF Packets IN) and
transmitted (TSF Packets OUT) on this BRE 2 port.
TSF Packets OWN [polStatBreIntfOwnTRFs]
Contains the number of transparent spanning tree frames transmitted and then received back on
this BRE 2 port.
TSF Packets FILTERED [polStatBreIntfTREFilters]
Contains the number of transparent spanning tree frames filtered by this BRE 2 port.
EF Packets IN/OUT [polStatBreIntfEFProcessdIns]
[polStatBREIntfEFCountOuts]
Contains the number of explorer frames that were received (EF Packets IN) and transmitted (EF
Packets OUT) on this BRE 2 port.
EF Packets OWN [polStatBreIntfOwnEFs]
Contains the number of explorer frames transmitted and then received back on this BRE 2 port.
EF Packets FILTERED [polStatBreIntfEFFilters]
Contains the number of explorer frames filtered at this BRE 2 port.
SRF Packets IN/OUT [polStatBreIntfSRFProcessdIns]
[polStatBreIntfSRFCountOuts]
Contains the number of source-routed frames that have been received (SRF Packets IN) and
transmitted (SRF Packets OUT) on this BRE 2 port.
SRF Packets OWN [polStatBreIntfOwnSRFs]
Contains the number of source-routed frames transmitted and then received back on this BRE 2
port.
SRF Packets FILTERED [polStatBreIntfSRFFilters]
Contains the number of source-routed frames filtered at this BRE 2 port.
BPDU Packets IN/OUT [polStatBreIntfBPDUProcessdIns]
[polStatBreIntfBPDUCountOuts]
Contains the number of spanning tree frames received (BPDU Packets IN) and transmitted
(BPDU Packets OUT) on this BRE 2 port.
9-14
IAN150/IPP MT
6/30/97
BPDU Packets OWN [polStatBreIntfOwnBPDUs]
Contains the number of spanning tree frames transmitted and then received back on this BRE 2
port.
BDRUs IN/OUT [polStatBreIntfBDRUIns]
[polStatBreIntfBDRUOuts]
Contains the number of Bridge Discovery Routing Updates received (BDRUs IN) and
transmitted (BDRUs OUT) on this BRE 2 port.
BDRU’s OWN [polStatBreIntfOwnBDRUs]
Contains the number of Bridge Discovery Routing Updates transmitted and then received back
on this BRE 2 port.
BDHellos IN/OUT [polStatBreIntfBDHelloIns]
[polStatBreIntfBDHelloOuts]
Contains the number of Bridge Discovery Hello messages received (BDHellos IN) and
transmitted (BDHellos OUT) on this BRE 2 port.
BDHello OWN [polStatBreIntfOwnBDHellos]
Contains the number of Bridge Discovery Hello messages transmitted and received back on this
BRE 2 port.
TSF Discards IN/OUT [polStatBreIntfDiscardTRFIns]
[polStatBreIntfDiscardTRFOuts]
Contains the number of transparent spanning tree frames received and discarded, and the number
of transparent spanning tree frames that were to be transmitted but were discarded, on this BRE 2
port.
No Known Bridges [polStatBreIntfnoKnownBridges]
Contains the number of source-routing frames not forwarded on this BRE 2 port because the
destination route designator was unknown.
No Blocks Avail [polStatBreIntfDiscards]
Contains the number of bridged frames not transmitted on this BRE 2 port because there were
insufficient message blocks.
No Routes [polStatBreIntfNoRoutes]
Contains the number of frames discarded because no route was available.
No Adjacency [polStatBreIntfNoAdjacencies]
Contains the number of frames discarded because no adjacency was available.
Hello Bad MTU [polStatBreIntfBDHelloBadMTUs]
Contains the number of Hello messages received on this BRE 2 port with an incompatible
Maximum Transmission Unit (MTU); the frames are discarded.
Port Dn Discards [polStatBreIntfDiscardsPortDowns]
Contains the number of frames not transmitted on this BRE 2 port because the BRE 2 port was
down.
IAN150/IPP MT
6/30/97
9-15
Hello Dup BN [polStatBreIntfBDHelloDupBNs]
Contains the number of discarded Hello message frames received on this BRE-2 port, identifying
a BRE 2 bridge which bridge number is a duplicate of another BRE 2 bridge.
Hello Bad BTL [polStatBreIntfBDHelloBadRPIs]
Contains the number of discarded Hello message frames received on this BRE 2 port, indicating
a Bridging Transport Layer incompatible with this BRE 2 port.
Fragment OKs [polStatBreIntfFragOks]
Contains the number of frames that required fragmentation to be transmitted on this BRE 2 port.
Fragment Fails [polStatBreIntfFragFails]
Contains the number of fragments that were unable to be transmitted on this BRE 2 port.
Fragment Creates [polStatBreIntfFragCreates]
Contains the number of fragments transmitted on this BRE 2 port.
TTL Expired [polStatBreIntfTTLExpires]
Contains the number of bridged frames discarded because time-to-live (TTL) had expired. TTL is
analogous to switch hop count. TTL is initialized to 8 and is decremented each hop. When TTL
becomes zero, the frame is discarded.
Reassembly OKs [polStatBreIntfReasmOks]
Contains the number of fragments received on this BRE 2 port that were successfully
reassembled.
Reassembly Fails [polStatBreIntfReasmFails]
Contains the number of fragments received on this BRE 2 port that could not be reassembled.
Reassembly Requests [polStatBreIntfReasmReqds]
Contains the number of fragments received on this BRE 2 port and waiting to be reassembled.
Reassembly Timeouts [polStatBreIntfReasmTimeouts]
Contains the number of fragments that were discarded because they timed out while waiting to be
reassembled.
Switch OKs [polStatBreIntfSwitchOks]
Contains the number of frames received on this BRE 2 port that were forwarded to the
destination BRE 2 bridge in the VLAN. Switches occur when the frame is not destined for the
receiving BRE 2 bridge but rather destined to another BRE 2 bridge that the receiving BRE 2
bridge has discovered.
Switch Fails [polStatBreIntfSwitchFails]
Contains the number of frames received on this BRE 2 port that were unable to be forwarded to
the destination BRE 2 bridge.
No Source IP [polStatBreIntfDiscardsNoSrcIps]
Contains the number of frames using IP as the network layer protocol, that were discarded
because no IP address was found for the destination BRE 2 bridge.
9-16
IAN150/IPP MT
6/30/97
Alloc Fails [polStatBreIntfAdjAllocsFails]
Contains the number of times memory allocation requests failed. Memory is allocated for the
BRE 2 Adjacency Table and the BRE 2 Routing Table; Alloc Fails could be caused by too many
BRE 2 bridges across all BRE 2 ports.
Unknown Route Des [polStatBreIntfDiscardsUnknownRts]
Contains the number of outbound source-routed frames discarded because the source route
designator in the frame’s RIF did not match any known destination BRE 2 bridge’s source route
designator (LAN ID and SR bridge number).
Send Failures [polStatBreIntfSendFails]
Contains the number of messages which failed to be sent.
BRE Physical Port Statistics
The BRE Physical Port Statistics provides current statistics on BRE physical ports. To access the
BRE Physical Port Statistics screen, from the Main Menu, follow the path:
3. Bridging
1. BRE Ports
2. BRE Physical Port Statistics
or type SBBP or 1312 from the command line of any menu or screen and press Enter. The
1.3.1.2 [SBBP] BRE Physical Port Statistics
PORT
HELLO IGNORES
BDRU IGNORES
INVALID PACKETS
========================================================
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Figure 9-9. BRE Physical Port Statistics Screen
The following paragraphs describe BRE Physical Port Statistics parameters. Corresponding MIB
> or Esc.
PORT [polStatBrePhysPort]
Identifies the ports for which statistics are being displayed.
HELLO IGNORES [polStatBreBDHelloIgnores]
Contains the number of BD Hello frames that were ignored by the physical port.
IAN150/IPP MT
6/30/97
9-17
BDRU IGNORES [polStatBreBDRUIgnores]
Contains the number of Bridge Discovery Routing Update frames that were ignored by the
physical port.
INVALID PACKETS [polStatBreInvalidPktsIns]
Contains the number of invalid frames received by the physical port.
BRE Forwarding Table
This screen provides current learned information about end stations and their respective BRE 2
bridges in the VLAN. To access the BRE Forwarding Table screen, from the Main Menu, follow
the path:
3. Bridging
1. BRE Ports
3. BRE Forwarding Table
or type SBBF or 1313 from the command line of any menu or screen and press Enter. The
1.3.1.3 [SBBF] BRE Forwarding Table
PORT
INDEX
BRIDGE
LAN
SR
MAC ADDRESS
BRIDGE
DOMAIN
ID
BRIDGE #
NUMBER
=========================================================================
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
00
0000
00000
0000
0
00:00:00:00:00:00
00000000
Figure 9-10. BRE Forwarding Table Screen
The following paragraphs describe BRE Forwarding Table parameters. Corresponding MIB
for a specific table entry, enter the appropriate identifying data (for example, PORT) in the first
line of the table, then refresh the screen by typing < . > N and pressing Enter. The screen
> or Esc.
To display information about a specific table entry, refresh the screen, enter the appropriate
identifying data (for example, PORT number) in the first line of the table, press Enter, type < .
> R and then press Enter again. The screen displays that table entry as the first table entry.
9-18
IAN150/IPP MT
6/30/97
PORT [polStatBreFtPort]
This field identifies the BRE 2 ports for which statistics are being displayed.
INDEX [polStatBreFtIndex]
This field contains an arbitrary number that identifies each record displayed.
BRIDGE DOMAIN [polStatBreFtBd]
This field identifies the ID for the bridge domain being monitored. A bridge domain is a logical
grouping of bridged LAN traffic that is isolated from the bridged traffic in other bridging
domains within the same IAN-150.
LAN ID [polStatBreFtLanId]
This field contains the LAN ID number that was assigned to the BRE 2 bridge from which the
end station was learned.
SR BRIDGE # [polStatBreFtBridgeNo]
This field contains the source-route bridge number of the BRE 2 bridge for this entry.
MAC ADDRESS [polStatBreFtMacAddress]
This field contains the MAC address of the learned end station.
BRIDGE NUMBER [polStatBreFtSbbn]
This field contains the BRE 2 bridge number of the bridge from which the end station was
learned.
IAN150/IPP MT
6/30/97
9-19
BRE Routing Table
The BRE Routing Table provides current information about routing to other non-adjacent BRE 2
bridges in the VLAN. To access the BRE Routing Table screen, from the Main Menu, follow the
path:
3. Bridging
1. BRE Ports
4. BRE Routing Table
or type SBBR or 1314 from the command line of any menu or screen and press Enter. The
system displays the following table:
1.3.1.4 [SBBR] BRE Routing Table
BRE INDEX DEST
NEXT
COST DL NET
IP ADDRESS
DLCI LAN REACH
PORT
BRIDGE BRIDGE
INTF
ID
============================================================================
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
00
0000 00000000 00000000 000 FR 00
000.000.000.000 0000 0000 NO
Figure 9-11. BRE Routing Table
The following paragraphs describe BRE Routing Table parameters. Corresponding MIB values,
specific table entry, enter the appropriate identifying data (for example, PORT) in the first line
of the table, then refresh the screen by typing < . > N and pressing Enter. The screen displays the
statistics that applied when the command was executed. To exit the display, press < \ > or Esc.
BRE PORT [polStatBreRTPort]
Identifies the BRE 2 ports for which statistics are being displayed.
INDEX [polStatBreRTIndex]
Contains a cumulative count which identifies each record displayed.
DEST BRIDGE [polStatBreRTdbbn]
Identifies the BRE 2 bridge number of the destination bridge.
9-20
IAN150/IPP MT
6/30/97
NEXT BRIDGE [polStatBreRTsbbn]
Identifies the BRE 2 bridge number of the next bridge to reach the destination bridge.
COST [polStatBreRTmetric]
Indicates the cost, in time (seconds), to reach the destination bridge.
DL [polStatBreRTdataLinkType]
Identifies the protocol for that Data Link. Valid values:
FR - Frame Relay
IP - Internet Protocol
ERR - Error
NET INTF [polStatBreRTnetIntf]
Contains the ID number of the port interface.
IP ADDRESS [polStatBreRTipAddress]
Contains the Internet Protocol (IP) destination address for use with outbound frames from a
bridge and for routing frames to a bridge (IP bridging transport only).
DLCI [polStatBreRTdlci]
The Data Link Connection Identifier field contains the destination address for Data Link bridging
transport.
LAN ID [polStatBreRTLanId]
Identifies the LAN ID of the destination BRE 2 bridge.
REACH [polStatBreRTreachable]
Indicates whether the destination BRE 2 bridge can be reached. Valid values: YES, NO, and
ERR.
IAN150/IPP MT
6/30/97
9-21
BRE Adjacency Table
This screen provides current information about adjacent BRE 2 bridges. To access the BRE
Adjacency Table, from the Main Menu, follow the path:
3. Bridging
1. BRE Ports
5. BRE Adjacency Table
or type SBBA or 1315 from the command line of any menu or screen and press Enter. The
1.3.1.5 [SBBA] BRE Adjacency Table
BRE INDEX BRE
MTU DL NET IP ADDRESS
DLCI LAN REACH HELLO
PORT
BRIDGE
INTF
ID
INTERVAL
==========================================================================
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
00
0000 00000000 0000 FR 00
000.000.000.000 0000 0000 NO
000
Figure 9-12. BRE Adjacency Table Screen
The following paragraphs describe BRE Adjacency Table parameters. Corresponding MIB
> or Esc.
BRE PORT [polStatBreADJPort]
Identifies the ports for which statistics are being displayed.
INDEX [polStatBREADJIndex]
Contains a cumulative count which identifies the record being displayed.
BRE BRIDGE [polStatBreAdjBridgeNum]
Contains the number assigned to the adjacent BRE 2 bridge.
9-22
IAN150/IPP MT
6/30/97
MTU [polStatBreAdjMTU]
Contains the Maximum Transmission Unit, which is the largest possible unit of data that can be
sent on a physical medium such as BRE 2 bridge.
DL [polStatBreAdjDataLinkType]
The Data Link field identifies the protocol. Valid values:
FR - Frame Relay
ERR - Error
NET INTF [polStatBreAdjNetIntf]
Contains the ID number of the port interface.
IP ADDRESS [polStatBreAdjIPAddress]
Contains the Internet Protocol destination address for use with outbound frames from a bridge
and for routing frames to a bridge (IP bridging transport only).
DLCI [polStatBreAdjDlci]
The Data Link Connection Identifier field contains the destination address for Data Link bridging
transport.
LAN ID [polStatBreAdjLanId]
Identifies the LAN ID of the destination BRE 2 bridge.
REACH [polStatBreAdjReachable]
Indicates whether the destination BRE 2 bridge can be reached. Valid values: YES, NO, and
ERR.
HELLO INTERVAL [polStatBreAdjHelloInterval]
Identifies the interval in seconds, during which Hello messages are exchanged with adjacent BRE
bridges.
IAN150/IPP MT
6/30/97
9-23
Bridging Tables Menu
The Bridging Tables menu provides categories about how the IAN-150 implements bridging. To
select the Bridging Tables menu, from the Main Menu, follow the path:
3. Bridging
5. Bridging Tables
or enter SBT or 135 from the command line of any menu or screen and press Enter. The system
1.3.5 [SBT] Bridging Tables
1.
Bridge Forwarding Database
2.
Source Route Encapsulation Table
3.
SR-TB Translation Table
Figure 9-13. Bridging Tables Menu
The IAN-150 provides the following screens to help you monitor bridging applications:
•
Bridge Forwarding Database - Shows a history of forwarded bridge traffic for a selected
bridge domain.
•
Source Route Encapsulation Table - Provides information ports that have source route
encapsulation enabled.
•
SR-TB Translation Table - Provides information about ports that have source routetransparent bridging translation enabled.
Each of these screens is described in the following sections.
9-24
IAN150/IPP MT
6/30/97
Bridge Forwarding Table
The Bridge Forwarding database is a table that shows the history of forwarded bridge traffic for
the selected Bridge Domain. To access the Bridge Forwarding Table screen from the Main Menu,
follow the path:
3. Bridging
5. Bridging Tables
1. Bridge Forwarding Database
or enter SBTF or 1351 from the command line of any menu or screen and press Enter. The
1.3.5.1 [SBTF] Bridge Forwarding Table
Bridge Domain
UNICAST MAC ADDRESS
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
1
PORT
000
000
000
000
000
000
000
000
ENTRY AGE
0000:00:00
0000:00:00
0000:00:00
0000:00:00
0000:00:00
0000:00:00
0000:00:00
0000:00:00
STATUS
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
OTHER
Figure 9-14. Bridge Forwarding Table Screen
The following paragraphs describe Bridge Forwarding Table parameters. Corresponding MIB
for a specific table entry, enter the appropriate identifying data (for example, UNICAST MAC
ADDRESS) in the first line of the table, then refresh the screen by typing < . > N and pressing
Enter. The screen displays the statistics that applied when the command was executed. To exit
the display, press < \ > or Esc.
Bridge Domain [local parameter]
Identifies the ID for the bridge domain being monitored. A bridge domain is a logical grouping
of bridged LAN traffic that is isolated from the bridged traffic in other bridging domains within
the same IAN-150.
UNICAST MAC ADDRESS [dot1dTPFDbAddress]
Identifies the MAC address to which the frames were forwarded.
PORT [dot1dTPFDbPort]
Identifies the port to which the frames were forwarded.
IAN150/IPP MT
6/30/97
9-25
ENTRY AGE [polStatBrgFwdAge]
Lists the length of time (in hours:minutes:seconds) that this entry has been last encountered in
this table.
STATUS [dot1dTPFDbStatus]
Identifies the status of a particular table entry. Valid values are:
OTHER - Table entry was obtained in some way other than the options listed.
INVALID - Data contained in this table entry is no longer valid (that is, the entry expired).
LEARNED - Information contained in table entry was learned from an outside source.
SELF- Information contained in this table entry resides in the bridge itself.
MGMT - This is a static table entry.
The Source Route Encapsulation Table displays information about ports on the IAN-150 that
have source route encapsulation enabled. To access the Source Route Encapsulation Table
screen, from the Main Menu, follow the path:
3. Bridging
5. Bridging Tables
2. Source Route Encapsulation Table
or type SBTS or 1352 from the command line of any menu or screen and press Enter. The
1.3.5.2 [SBTS] Source Route Encapsulation Table
Bridge Domain
1
Port Age
MAC Address
Length Routing Info Field
000 0000:00:00 00:00:00:00:00:00
000
000 0000:00:00 00:00:00:00:00:00
000
000 0000:00:00 00:00:00:00:00:00
000
000 0000:00:00 00:00:00:00:00:00
000
(C)
00:00:00:00:00:00 (N)
(C)
00:00:00:00:00:00 (N)
(C)
00:00:00:00:00:00 (N)
(C)
00:00:00:00:00:00 (N)
Figure 9-15. Source Route Encapsulation Table Screen
The following paragraphs describe Source Route Encapsulation parameters. Corresponding MIB
> or Esc.
9-26
IAN150/IPP MT
6/30/97
Bridge Domain
Identifies the ID for the bridge domain being monitored. In the current release, the IAN-150 only
supports one bridge domain.
Port [polStatBrgSrePort]
Identifies the port to on which source route encapsulation has been enabled and whose
information is being displayed in this entry.
Age [polStatBrgSreAge]
Lists the length of time (in hours:minutes:seconds) since the source routing software last
accessed this entry.
MAC Address (C) [polStatBrgSreMacAddr]
Identifies the destination MAC address, in canonical format, for this entry.
MAC Address (N) [polStatBrgSreMacAddr]
Identifies the destination MAC address, in non-canonical format, for this entry.
Length [polStatBrgSreRifLen]
Defines the length of the Routing Information Field.
Routing Info Field [polStatBrgSreRifString]
Displays the information contained in the Routing Information Field that specifies the path to the
destination MAC address of this entry.
IAN150/IPP MT
6/30/97
9-27
The Source Route-Transparent Bridging (SR-TB) Translation Table displays information about
ports on the IAN-150 that have source route translation enabled. To access the SR-TB
Translation Table screen from the Main Menu, follow the path:
3. Bridging
5. Bridging Tables
3. SR-TB Translation Table
or type SBTX or 1353 from the command line of any menu or screen and press Enter. The
1.3.5.3 [SBTX] SR-TB Translation Table
Bridge Domain
1
Port Age
MAC Address
Length Routing Info Field
000 0000:00:00 00:00:00:00:00:00
000
000 0000:00:00 00:00:00:00:00:00
000
000 0000:00:00 00:00:00:00:00:00
000
000 0000:00:00 00:00:00:00:00:00
000
000 0000:00:00 00:00:00:00:00:00
000
(C)
00:00:00:00:00:00 (N)
(C)
00:00:00:00:00:00 (N)
(C)
00:00:00:00:00:00 (N)
(C)
00:00:00:00:00:00 (N)
(C)
00:00:00:00:00:00 (N)
Figure 9-16. SR-TB Translation Table Screen
The following paragraphs describe SR-TB Translation parameters. Corresponding MIB values,
specific table entry, enter the appropriate identifying data (for example, PORT) in the first line
of the table, then refresh the screen by typing < . > N and pressing Enter. The screen displays the
statistics that applied when the command was executed. To exit the display, press < \ > or Esc.
> R and press Enter again. The screen displays that table entry as the first table entry.
Bridge Domain
Identifies the ID for the bridge domain being monitored. In the current release, the IAN-150 only
supports one bridge domain.
Port [polStatBrgXlatPort]
Identifies the port to on which source route encapsulation has been enabled and whose
information is being displayed in this entry.
Age [polStatBrgXlatAge]
Lists the length of time (in hours:minutes:seconds) since the source routing software accessed
this entry.
9-28
IAN150/IPP MT
6/30/97
MAC Address (C) [polStatBrgXlatMACAddr]
Identifies the destination MAC address, in canonical format, for this entry.
MAC Address (N) [polStatBrgXlatMACAddr]
Identifies the destination MAC address, in non-canonical format, for this entry.
Length [polStatBrgXlatRofLen]
Defines the length of the Routing Information Field.
Routing Info Field [polStatBrgXlatRifString]
Displays the information contained in the Routing Information Field that specifies the path to the
Destination MAC address of this entry.
IAN150/IPP MT
6/30/97
9-29
Chapter
10
DLSw Monitoring
NOTE:
noted.
The IAN-150 provides routing information to help monitor and troubleshoot Data Link
Switching applications. This chapter describes DLSw monitoring and troubleshooting
capabilities.
DLSw Status and Control Menu
The DLSw Status and Control menu provides categories that relate to the monitoring of DLSw
for the IAN-150. To select the DLSw Status and Control menu from the Main Menu, follow the
path:
4. Routing
4. DLSW
or enter SRD or 144 from the command line of any menu or screen and press Enter. The system
1.4.4
[SRD] DLSW Status and Control
1. Port Statistics
2. DLSW Connection Summary
3. DLSW NetBios Name Caching Table
Figure 10-1. DLSw Status and Control Menu
There are three categories for DLSw:
•
Port Statistics - This screen provides a summary of port-specific DLSw statistics.
•
DLSw Connection Summary - This table provides a summary of active DLSw sessions.
•
DLSw NetBios Name Caching Table - This table lists the NetBios entities to which the
IAN-150 is trying to send data.
IAN150/IPP MT
6/30/97
10-1
Chapter 10, DLSw Monitoring
DLSw Monitoring Tips
The IAN-150 uses templates for each of its statistical displays and tables; when you first access a
display or table, the system displays the values in the default template. To view current values,
values for statistical displays, type < . > R and press Enter. To see current values for tables, type
< . > N and press Enter.
Each table can be sorted on the basis of key fields, which are located in the first line of every
table. To display information about a specific table entry, refresh the screen, enter the appropriate
To end the Monitor process and remain at this screen, press < . >. To exit the display, press < \ >
or Esc.
DLSw Port Statistics
The DLSw Port Statistics display provides current general statistics on DLSw port operations. To
select the DLSw Port Statistics display from the Main Menu, follow the path:
4. Routing
4. DLSW
1. Port Statistics
or enter SRDP or 1441 from the command line of any menu or screen and press Enter. The
1.4.4.1 [SRDP] DLSW Port Statistics
Port
000
TCP Connections
Last Failure Reason
ACTIVE
0
000
SUCCEEDED
0
FAILED
0
All Route Explorers
CANUREACH's
NetBios Name Qry's
DLC Name Qry's
UI Datagrams
IN
0
0
0
0
0
OUT
0
0
0
0
0
FAILED
0
0
LAST CONNECTION ATTEMPTED
Connection Initiated by None Attempted
SOURCE
SAP
MAC address
NetBios Name
00
00:00:00:00:00:00
DESTINATION
00
00:00:00:00:00:00
Figure 10-2. DLSw Port Statistics Screen
10-2
IAN150/IPP MT
6/30/97
The DLSw Port Statistics parameters are described in the following paragraphs. Corresponding
MIB values appear in brackets next to the parameter names. To view current values for a specific
port, enter the port number in the Port field, then refresh the screen by typing < . > R and
Port [polStatDlswIntfNum]
Identifies the port to be examined.
TCP Connections [polStatDlswTcpActives] [polStatDlswTcpConnects]
[polStatDlswTcpFailures]
Provides a count of possible TCP connections. TCP Connection ACTIVE lists the total number
of currently active TCP connections. TCP Connections SUCCEEDED lists the total number of
times the response received from TCP is type Open Success, and the TCP connection states for
read and write are in the opened state. TCP Connections FAILED lists the total number of
times the response received from TCP is type Terminate or TCP Error.
Last Failure Reason [polStatDlswTcpFailCauses]
Lists a numeric value that corresponds to a definition describing why the last failed TCP
connection occurred. Valid TCP failure codes and their definitions are listed in Table 10-1 below.
Table 10-1. TCP Connection Failure Reasons
Code
Failure Name
Failure Reason
101
RESET_CONNECTION
Remote TCP ABORTs connection.
102
USER_TIMEOUT
Untimely data transfer.
103
BAD_RANGE
Security ranges must be pairs.
104
NO_SUCH_LCN
Connection does not exist.
105
NOT_YET_OPEN
Connection unestablished.
106
CLOSING_CONNECTION
Inappropriate data transfer.
107
BAD_PRECEDENCE
Precedence request unallowed.
108
BAD_SECURITY
Security request not allowed.
109
NO_FOREIGN_SOCKET
Socket unspecified (UNUSED).
110
EXISTING_CONNECTION
Connection already exists.
111
NO_RESOURCES
Insufficient resources.
112
CONNECTION_REFUSED
LCN refused by remote TCP.
113
ILLEGAN_SYN
Unexpected SYN received.
114
DUPLICATE_CONNECTION
Requested LCN already used.
115
HFP_NO_RESOURCES
Insufficient resources (HFP).
116
TELNET_AUTH_FAILURE
TELNET rejected connection.
All Route Explorers [polStatDlswAreTestIns] [polStatDlswAreTestOuts]
[polStatDlswAreTestFails]
Lists the total number of All Route Explorer frames transmitted (All Route Explorers OUT),
received (All Route Explorer IN), and rejected (ALL Route Explorers FAILED) by this
device over this port.
IAN150/IPP MT
6/30/97
10-3
CANUREACH’s [polStatDlswCanureachIns] [polStatDlswCanureachOuts]
Lists the number of CANUREACH frames transmitted (CANUREACH’s OUT), and received
(CANUREACH’s IN) by this device over this port.
NetBios Name Qry’s [polStatDlswNetBiosNQIns]
[polStatDlswNetBiosNQOuts] [polStatDlswNetBiosNQFails]
Lists the number of NetBios Name Query commands either transmitted or received. NetBios
Name Qry’s IN lists the number of times a NetBios Name Query command is received over this
port. NetBios Name Qry OUT lists the number of times a NetBios Name Query is sent over this
port. NetBios Name Qry FAILED lists the number of times the circuit state is Disconnected or
Resolve Pending during a NetBios session.
DLC Name Qry’s [polStatDlswDlcNameQIns] [polStatDlswDlcNameQOuts]
Lists the number of Data Link Connection Name Query frames either transmitted (DLC Name
Qry’s OUT) and received (DLC Name Qry’s IN) by this device over this port.
UI Datagrams [polStatDlswDgrmIns] [polStatDlswDgrmOuts]
Lists the number of Unnumbered Information frames either transmitted (UI Datagrams OUT) or
received (UI Datagrams IN) by this device over this port.
LAST CONNECTION ATTEMPTED [polStatDlswLstConCause]
Displays information that describes how the last connection was established. Possible values for
this field are:
Connection Initiated by None Attempted
Connection Initiated by All Route Explorer
Connection Initiated by CANUREACH
Connection Initiated by NetBios Name Query
Connection Initiated by DLC Name Query
SAP [polStatDlswLstConSrcSap] [polStatDlswLstConDstSap]
Lists the numeric identifier for the source (SAP SOURCE) and destination (DESTINATION
SAP) service access points for the DLSW connection listed in the LAST CONNECTION
ATTEMPTED field.
MAC address [polStatDlswLstConSrcMac] [polStatDlswLstConDstMac]
Lists the MAC address for the Source NetBios Entity (MAC ADDRESS SOURCE) and the
destination NetBios entity (MAC ADDRESS DESTINATION) for the DLSW connection listed
in the LAST CONNECTION ATTEMPTED field.
NetBios Name [polStatDlswLstConSrcName]
[polStatDlswLstConDstName]
Lists the name of the source (NetBios Name SOURCE) and destination (NetBios Name
DESTINATION) NetBios entity associated with the above listed MAC address for the DLSW
connection listed in the LAST CONNECTION ATTEMPTED field.
10-4
IAN150/IPP MT
6/30/97
DLSw Connection Summary
The DLSw Connection Summary shows the current and past history of DLSw connections per
port for the IAN-150. To access the DLSw Connection Summary screen from the Main Menu,
follow the path:
4. Routing
4. DLSW
2. DLSW Connection Summary
or enter SRDC or 1442 from the command line of any menu or screen and press Enter. The
1.4.4.2 [SRDC] DLSW Connection Summary
Port
Num
Src MAC address/
NetBios Name
Src
SAP
Dest MAC address/
NetBios Name
Dest
SAP
DLSW
State
000
00:00:00:00:00:00
00
00:00:00:00:00:00
00
0
000
00:00:00:00:00:00
00
00:00:00:00:00:00
00
0
000
00:00:00:00:00:00
00
00:00:00:00:00:00
00
0
000
00:00:00:00:00:00
00
00:00:00:00:00:00
00
0
000
00:00:00:00:00:00
00
00:00:00:00:00:00
00
0
000
00:00:00:00:00:00
00
00:00:00:00:00:00
00
0
000
00:00:00:00:00:00
00
00:00:00:00:00:00
00
0
000
00:00:00:00:00:00
00
00:00:00:00:00:00
00
0
Figure 10-3. DLSw Connection Summary Screen
The following paragraphs describe DLSw Connection Summary parameters. Corresponding MIB
values appear in brackets next to the parameter names. To view the current data on this table,
execute a Read Next command by typing < . > N and pressing Enter. To view the data for a
specific port not shown on the first page of the table, enter the port number in the first column,
then refresh the screen by executing a Read Next command. The screen displays the statistics
that applied when the command was executed. To exit the display, press < \ > or Esc.
Port Num [polStatDlswConnPortNum]
Src MAC address/NetBios Name [polStatDlswConnSrcMac]
Identifies the MAC address of the local end station that is on the LAN side of the IAN-150.
IAN150/IPP MT
6/30/97
10-5
Src SAP [polStatDlswConnSrcSap]
Displays the source Service Access Point (SAP) in hexidecimal used by the local end station that
is on the LAN side of the IAN-150.
Dest MAC address/NetBios Name [polStatDlswConnDstMac]
Displays the MAC address of the remote end station that is on the WAN side of the IAN-150.
Dest SAP [polStatDlswConnDstSap]
Displays the destination Service Access Point (SAP) in hexidecimal used by the remote end
station that is on the WAN side of the IAN-150.
DLSW State [polStatDlswConnState]
Indicates the current state of the DLSw circuit. Valid values:
1
2
3
4
5
6
7
8
9
10
11
12
10-6
Disconnected
Disconnect Pending
Resolve Pending
Circuit Pending
Circuit Established
Contact Pending
Connect Pending
Connected
Circuit Restart
Halt Pending
Restart Pending
Restart Pending 1
IAN150/IPP MT
6/30/97
DLSw NetBios Name Caching Table
The DLSw NetBios Name Caching Table provides information about the NetBios entities to
which the IAN-150 is trying to send data. To access the DLSw NetBios Name Caching Table
screen from the Main Menu, follow the path:
4. Routing
4. DLSW
3. DLSW NetBios Name Caching Table
or enter SRDN or 1443 from the command line of any menu or screen and press Enter. The
1.4.4.3 [SRDN] DLSW NetBios Name Caching Table
Port
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Entity Name
IP Address
MAC address
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
Age
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Figure 10-4. DLSw NetBios Name Caching Table Screen
The following paragraphs describe DLSw NetBios Name Caching parameters. Corresponding
MIB values appear in brackets next to the parameter names. To view the current data on this
table, execute a Read Next command by typing < . > N and pressing Enter. To view the data for
a specific port not shown on the first page of the table, enter the port number in the first column,
then refresh the screen by executing a Read Next command. The screen displays the statistics
that applied when the command was executed. To exit the display, press < \ > or Esc.
Port [polStatDlswNetBiosPortNum]
This parameter identifies the port to be examined.
Entity Name [polStatDlswNetBiosName]
Displays the name of the NetBios entity to which the router is trying to send data.
IP Address [polStatDlswNetBiosIP]
Identifies the IP address of the DLSw partner associated with this entity name.
MAC address [polStatDlswNetBiosMac]
Identifies the MAC address of the DLSw partner associated with this entity name.
IAN150/IPP MT
6/30/97
10-7
Age [polStatDlswNetBiosAge]
Identifies the age of the entry.
LLC Status
The LLC Status screen provides statistics from the IAN-150’s global LLC table. This table,
which displays connection information, contains entries from both DLSw and QLLC2 users. To
select the LLC Status screen from the Main Menu, follow the path:
4. Routing
9. LLC
or enter SRL or 149 from the command line of any menu or screen and press Enter. The system
1.4.9 [SRL] LLC Status
SOURCE
SAP
MAC address
Port Number
FRMR IN
FRMR OUT
UI Frames
TESTs
XIDs
RNRs
REJs
SABMEs
UAs
DISCs
DMs
FRMRs
Frames
DESTINATION
00
00:00:00:00:00:00
000
NONE
NONE
00
00:00:00:00:00:00
LLC State
Contents
Contents
IN
0
0
0
0
0
0
0
0
0
0
0
DISCONNECT
00000000
00000000
OUT
0
0
0
0
0
0
0
0
0
0
0
Figure 10-5. LLC Status Screen
The following paragraphs describe LLC Status parameters. Corresponding MIB values appear in
brackets next to the parameter names. To view current values, issue a Read command from the
command line by typing < . > R and pressing Enter. The screen displays the statistics that
applied when the command was executed. To exit the display, press < \ > or Esc.
The key fields for this display are SAP SOURCE, SAP DESTINATION and their respective
MAC addresses. To display information about a particular SAP, enter the appropriate identifying
data, then refresh the screen by typing < . > R and pressing Enter.
SAP [polStatLlcSrcSap] [polStatLlcDstSap]
Identifies the source and destination service access points. SAP SOURCE identifies the SAP
that originated the data packet. SAP DESTINATION identifies the SAP for which the data
packet is intended.
10-8
IAN150/IPP MT
6/30/97
MAC address [polStatLlcSrcMac] [polStatLlcDstMac]
Indicates the MAC address for local and non-local nodes. MAC address SOURCE displays the
MAC address for the local node for both DLSw and QLLC2 connections. MAC address
DESTINATION displays the MAC address for the host device (QLLC2 connections) or the
remote host device (DLSw connections).
Port Number [polStatLlcPortNum]
Identifies the port associated with this LLC session.
LLC State [polStatLlcState]
Indicates the state of this LLC connection. Valid values:
IAN150/IPP MT
6/30/97
DISCONNECT
Inoperative state.
ADM
Initial operational state, or a DISC has been received.
SETUP
SABME has been sent; awaiting UA.
SETUP COLL
SABME collision encountered.
CONN
SABME received; waiting for task acknowledgment.
ERROR
FRMR sent.
NORMAL
Link established. (This is the normal state.)
RESET
SABME sent; awaiting UA to reset link.
RESET WAIT
FRMR received; waiting for reset from task.
RESET RSP WAIT
Received SABME after FRMR; waiting for task to acknowledge.
CONN REJECT
REJECT frame sent.
BUSY
Received RNR.
BUSY REJ
REJECT frame sent after having received an RNR.
BUSY ACK
Awaiting a Poll response after having received an RNR.
BUSY REJ ACK
Awaiting a Poll response, having sent a REJECT and having received
an RNR.
AWAIT
Awaiting a Poll response.
AWAIT REJECT
Awaiting a Poll response after having sent a REJECT.
LOCAL BUSY
Network window closed; RNR sent.
REJECT
REJECT frame sent.
CONN RNR
Closed network window detected; RNR sent.
REJECT BUSY
REJECT and RNR sent.
AWAIT BUSY
Awaiting Poll response and RBR sent.
AWAIT BUSY REJ
Awaiting Poll response; RNR and REJECT sent.
AWAIT POLLING
Awaiting ACK and REJECT sent.
AWAIT REJ ACK
Reject frame sent and awaiting Poll response.
10-9
FRMR In [polStatLlcFrmrCodeRx]
Defines the information received in a Frame Rejected frame, indicating that LLC has generated
and transmitted a defective packet. Valid values:
NONE
Indicates that no FRMR frames have been received.
UNDEFINED
Indicates that there was a problem with the transmitted packet not
defined by any of the available categories.
LENGTH ERROR
Indicates that the size of the packet exceeded acceptable values
MTU EXCEEDED
Indicates that the data unit size has exceeded acceptable values.
INVALID NR
Indicates that there was an invalid transmitter receive sequence
number.
Contents [polStatLlcFrmrFrameRx]
Displays the information contained in the received FRMR frame.
FRMR Out [polStatLlcFrmrCodeTx]
Defines the information transmitted in a Frame Rejected frame, indicating that LLC has received
a defective packet. Valid values:
NONE
UNDEFINED
LENGTH ERROR
MTU EXCEEDED
INVALID NR
number.
Contents [polStatLlcFrmrFrameTx]
Displays the information contained in the transmitted FRMR frame.
UI Frames [polStatLlcUiIns] [polStatLlcUiOuts]
Number of Unnumbered Information (UI) frames received and transmitted over this connection.
UI IN lists the number of UI frames received. UI OUT lists the number of UI frames
transmitted.
TESTs [polStatLlcTestIns] [polStatLlcTestOuts]
Number of Test frames received and transmitted over this connection. Test IN lists the number
of Test frames received. Test OUT lists the number of Test frames transmitted.
XIDs [polStatLlcXidIns] [polStatLlcXidOuts]
Number of Exchange Identification (XID) frames received and transmitted over this connection.
XID IN lists the number of XID frames received. XID OUT lists the number of XID frames
transmitted.
RNRs [polStatLlcRnrIns] [polStatLlcRnrOuts]
Number of Receiver Not Ready (RNR) frames received and transmitted over this connection.
RNR IN lists the number of RNR frames received. RNR OUT lists the number of RNR frames
transmitted.
10-10
IAN150/IPP MT
6/30/97
REJs [polStatLlcRejIns] [polStatLlcRejOuts]
Number of Rejected (REJ) frames received and transmitted over this connection. REJ IN lists
the number of REJ frames received. REJ OUT lists the number of REJ frames transmitted.
SABMEs [polStatLlcSabmeIns] [polStatLlcSabmeOuts]
Number of Set Asynchronous Balanced Mode Extended (SABME) frames received and
transmitted over this connection. SABME IN lists the number of SABME frames received.
SABME OUT lists the number of SABME frames transmitted.
UAs [polStatLlcUaIns] [polStatLlcUaOuts]
Number of Unnumbered Acknowledgment (UA) frames received and transmitted over this
connection. UA IN lists the number of UA frames received. UA OUT lists the number of UA
frames transmitted.
DISCs [polStatLlcDiscIns] [polStatLlcDisnOuts]
Number of Disconnect (DISC) frames received and transmitted over this connection. DISC IN
lists the number of DISC frames received. DISC OUT lists the number of DISC frames
transmitted.
DMs [polStatLlcDmIns] [polStatLlcDmOuts]
Number of Disconnect Mode (DM) frames received and transmitted over this connection. DM IN
lists the number of DM frames received. DM OUT lists the number of DM frames transmitted.
FRMRs [polStatLlcFrmrIns] [polStatLlcFrmrOuts]
Number of Frame Rejected (FRMR) frames received and transmitted over this connection.
FRMR IN lists the number of FRMR frames received. FRMR OUT lists the number of FRMR
frames transmitted.
Frames [polStatLlcFrmIns] [polStatLlcFrmOuts]
Total number of received and transmitted frames over this connection. Frames IN lists the
number of frames received. Frames OUT lists the number of frames transmitted.
IAN150/IPP MT
6/30/97
10-11
Chapter
11
TCP/IP Monitoring
NOTE:
noted.
to help you monitor TCP/IP routing. This chapter describes these capabilities.
TCP/IP Monitoring Tips
display or table, the values in the default template appear. To view current values, refresh the
statistical displays, type < . > R and press Enter. To view current values for tables, type < . > N
and press Enter.
To end the Monitor process and remain at this screen, press < . >. To exit the screen, press < \ >
or Esc.
IAN150/IPP MT
6/30/97
11-1
Chapter 11, TCP/IP Monitoring
IP Control and Status
The IP Control and Status screens provide monitoring information about the IP suite of routing
protocols. To reach the IP Control and Status menu from the Main Menu, follow the path:
4. Routing
1. IP
or type SRI or 141 from the command line of any menu or screen and press Enter. The system
1.4.1 [SRI] IP Control and Status
1. IP Status
2. ICMP Status
3. UDP Status
4. HTTP Status
Figure 11-1. IP Control and Status Menu
The IAN-150 provides status information for four main categories within the IP Control and
Status menu:
11-2
•
•
ICMP - Internet Control Message Protocol
•
UDP - User Datagram Protocol
•
HTTP - Hyper Text Transport Protocol
IAN150/IPP MT
6/30/97
IP Status
The IP Status menu provides access to the IP protocol monitoring features supported by the IAN150. To select the IP Status menu from the Main Menu, follow the path:
4. Routing
1. IP
1. IP Status
or type SRII or 1411 at the command line of any menu or screen and press Enter. The system
1.4.1.1 [SRII] IP Status
1. IP Statistics
2. IP Common Routing Table
3. ARP Table
4. IP Address Table
Figure 11-2. IP Status Menu
IP Status information consists of four different displays:
•
IP Statistics - provides current statistics on IP operation.
•
IP Common Routing Table - provides IP routing status information arranged by IP address
used to obtain the routing status information.
•
ARP Table - shows mapping between IP addresses and physical addresses for all IPconfigured ports.
•
IP Address Table - shows the IP address, network mask, and maximum reassembly size for
each IAN-150 IP interface.
Each of these displays is described in the following sections.
IAN150/IPP MT
6/30/97
11-3
IP Status Screen
The IP Status screen provides current statistics on IP interface operation. To select the IP Status
screen, from the Main Menu, follow the path:
4. Routing
1. IP
1. IP Status
1. IP Statistics
or type SRIII or 14111 at the command line of any menu or screen and press Enter. The system
1.4.1.1 1 [SRIII] IP Status
Forwarding
Logical Disconnect
PSN Loopback Mode
Clearing Redirect Table Interval (sec)
Static Routes in Non-Volatile RAM
Default Time To Live
Forwarded Pkts
In Receives
In Hdr Errs
In Unkwn Protos
In Addr Errs
In Discards
In Delivers
Reasm OKs
Reasm Timeout
0
0
0
0
0
0
0
0
0
TRUE
FALSE
FALSE
00000
00000
00000
Filtered Pkts
Out Discards
Out NoRoutes
Out Requests
Frag Creates
Frag OKs
Frag Fails
Reasm Fails
Reasm Reqds
0
0
0
0
0
0
0
0
0
Figure 11-3. IP Status Screen
The following paragraphs describe IP Status parameters. Corresponding MIB values, where
applicable, appear in brackets next to the parameter names. To view current values, issue a Read
command from the command line by typing < . > R and pressing Enter. The screen displays the
statistics that applied when the command was executed. To exit the screen, press < \ > or Esc.
Forwarding [ipForwarding]
Indicates the status of the Gateway Mode.
TRUE - Indicates gateway is operational.
FALSE - Indicates gateway is not operating.
Logical Disconnect [polstatipLogicalDis]
Indicates whether IP processes or discards datagrams.
TRUE - Indicates IP discards all incoming and outgoing datagrams.
FALSE - Indicates IP processes all datagrams.
11-4
IAN150/IPP MT
6/30/97
PSN Loopback Mode [polstatipLoopbacks]
Indicates whether IP sends datagrams destined for local network to local PSN or to the next
higher level protocol.
TRUE - Indicates that IP sends datagrams to local PSN.
FALSE - Indicates that IP sends datagrams to next higher level protocol.
Clearing Redirect Table Interval (sec) [polStatIpRedirectTimers]
Indicates interval, in seconds, between clearing of invalid entries from the common routing table.
Static Routes in Non-Volatile RAM [polStatIpStaticRoutes]
Indicates number of static routes currently maintained in non-volatile RAM.
Default Time To Live [ipDefaultTTL]
Indicates default length of time, in seconds, that is inserted into the time-to-live field of the IP
header of datagrams originating at the IAN-150 if a TTL value is not supplied by the transport
layer protocol.
Forwarded Pkts [ipForwDatagrams]
Indicates number of datagrams routed towards a final destination. For non-IP equipment, this
value indicates the number of packets successfully source-routed.
Filtered Pkts [polStatIpFilteredPkts]
Indicates number of datagrams discarded due to filtering.
In Receives [ipInReceives]
Indicates number of datagrams received, including those in error.
Out Discards [ipOutDiscards]
Indicates number of output datagrams without other problems, but nevertheless discarded due to
lack of buffers. This value includes discarded datagrams counted in the Forwarded Pkts item.
In Hdr Errs [ipInHdrErrors]
Indicates number of datagrams discarded due to errors in their IP headers.
Out NoRoutes [ipOutNoRoutes]
Indicates number of output datagrams without other problems, for which no route could be
found. This value includes discarded datagrams counted in the Forwarded Pkts item.
In Unkwn Protos [ipInUnknownProtos]
Indicates number of datagrams discarded due to unknown or unsupported protocol.
Out Requests [ipOutRequests]
Indicates number of datagrams supplied to IP in requests for transmission by IP user protocols.
This value does not include datagrams counted in the Forwarded Pkts item.
In Addr Errs [ipInAddrErrors]
Indicates number of datagrams discarded due to errors in IP address. For non-IP equipment, this
indicates the number of datagrams discarded because destination address was not local.
Frag Creates [ipFragCreates]
Indicates number of datagram fragments generated in local equipment.
IAN150/IPP MT
6/30/97
11-5
In Discards [ipInDiscards]
Indicates number of datagrams received without other problems but nevertheless discarded. This
value does not include datagrams discarded while awaiting reassembly.
Frag OKs [ipFragOKs]
Indicates number of datagrams successfully fragmented in local equipment.
In Delivers [ipInDelivers]
Indicates number of datagrams successfully delivered to user protocols, including ICMP.
Frag Fails [ipFragFails]
Indicates number of datagrams discarded because they were not successfully fragmented in local
equipment.
Reasm OKs [ipReasmOKs]
Indicates number of IP datagrams successfully reassembled.
Reasm Fails [ipReasmFails]
Indicates number of IP reassembly algorithm failures.
Reasm Timeout [ipReasmTimeout]
Indicates maximum time, in seconds, that received IP fragments are held while awaiting
reassembly.
Reasm Reqds [ipReasmReqds]
Indicates number of IP fragments received and requiring local assembly.
IP Common Routing Table
The IP Common Routing Table screen provides information on IP routing status arranged by IP
address or by the protocol used to obtain the routing status information. To access the IP
Common Routing Table screen from the Main Menu, follow the path:
4. Routing
1. IP
1. IP Status
2. IP Common Routing Table
or type SRIIR or 14112 at the command line of any menu or screen and press Enter. The system
1.4.1.1.2 [SRIIR] IP Common Routing Table
Route
===============
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
Mask
===============
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
Gateway
Cost Override Protocol Intf
============ ==== ======== ======== ====
000.000.000.000 0
FALSE
OTHER
0
000.000.000.000 0
FALSE
OTHER
0
000.000.000.000 0
FALSE
OTHER
0
000.000.000.000 0
FALSE
OTHER
0
000.000.000.000 0
FALSE
OTHER
0
000.000.000.000 0
FALSE
OTHER
0
Figure 11-4. IP Common Routing Table Screen
11-6
IAN150/IPP MT
6/30/97
The following paragraphs describe IP Common Routing Table parameters. Corresponding MIB
values, where applicable, appear in brackets next to the parameter names. To view the current
data on this table, issue a Read Next command by typing < . > N and pressing Enter. To view
the current values for a specific route not shown on the first page of the table, enter the route or
gateway of the route you want to monitor, then refresh the screen by issuing a Read Next
command. The screen displays the statistics that applied when the command was executed. To
exit the screen, press < \ > or Esc.
Route [ipRouteDest]
Indicates network address of the destination network.
Mask [ipRouteMask]
Indicates the Subnet Mask that identifies the network portion of the associated destination
network address.
Gateway [ipRouteNextHop]
Indicates the gateway address of the next hop to reach the specified network address.
Cost [ipRouteMetric1]
Indicates the route cost of the specified network address.
Override [polipRouteOverrideFlag]
Indicates route replacement status.
TRUE - Indicates the route will not be changed, even if a better path is learned.
FALSE - Indicates the route will be changed if a better path is learned.
Protocol [ipRouteProto]
Indicates the protocol used to learn the route.
Intf [ipRouteIfIndex]
Indicates the interface on the IAN-150 used to reach the destination network address.
IAN150/IPP MT
6/30/97
11-7
Address Resolution Protocol (ARP) Table
The Address Resolution Protocol Table screen shows equivalencies between Internet Protocol
(IP) addresses and physical addresses for all IP-configured ports. To select the ARP Table screen
4. Routing
1. IP
1. IP Status
3. ARP Table
or type SRIIA or 14113 at the command line of any menu or screen and press Enter. The system
1.4.1.1.3 [SRIIA] Address Resolution Protocol Table
Intf
====
0
0
0
Physical Address
================
00:00:00:00:00:00
00:00:00:00:00:00
00:00:00:00:00:00
Network Address
===============
000.000.000.000
000.000.000.000
000.000.000.000
Type
====
Other
Other
Other
Figure 11-5. Address Resolution Protocol (ARP) Table Screen
The following paragraphs describe Address Resolution Protocol Table parameters paragraphs.
Corresponding MIB values, where applicable, appear in brackets next to the parameter names. To
view the current data on this table, issue a Read Next command by typing < . > N and pressing
Enter. To view the current values for a specific interface not shown on the first page of the table,
enter the interface or physical address you want to monitor, then refresh the screen by issuing a
Read Next command. The screen displays the statistics that applied when the command was
executed. To exit the screen, press < \ > or Esc.
Intf [ipNetToMediaIfIndex]
Indicates the ID of the interface to reach the next hop of the route.
Physical Address [ipNetToMediaPhysAddress]
Indicates the media-dependent MAC address.
Network Address [ipNetToMediaNetAddress]
Indicates the IP address that corresponds to the media-dependent physical address.
Type [ipNetToMediaType]
Indicates the type of mapping. There are four available values for this field:
11-8
INVALID
Indicates this table entry has aged-out and is no longer valid but has not yet
been flushed from the table.
DYNAMIC
ARP entries are learned or discovered from connected segments of the
network.
STATIC
ARP entries configured at the local interface.
OTHER
Indicates the mapping for the associated port is not operative.
IAN150/IPP MT
6/30/97
IP Address Table
The IP Address Table screen shows the IP address, network mask, and maximum reassembly size
for each IAN-150 IP interface. To access the IP Address Table screen, from the Main Menu,
follow the path:
4. Routing
1. IP
1. IP Status
4. IP Address Table
or type SRIIT or 14114 at the command line of any menu or screen and press Enter. The system
1.4.1.1.4 [SRIIT] IP Address Table
Intf
====
0
0
0
0
IP Address
==========
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
Network Mask
============
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
Max
Reassembly Size
===============
0
0
0
0
Figure 11-6. IP Address Table Screen
The following paragraphs describe IP Address Table parameters. Corresponding MIB values,
where applicable, appear in brackets next to the parameter names. To view the current data on
this table, issue a Read Next command by typing < . > N and pressing Enter. To view the
current data for a specific interface not shown on the first page of the table, enter the interface
number or IP address you want to check, then refresh the screen by issuing a Read Next
Intf [ipAdEntIfIndex]
Indicates the interface identification number.
IP Address [ipAdEntAddr]
Indicates the IP address of the interface.
Network Mask [ipAdEntNetMask]
Indicates the network mask for the interface.
Max Reassembly Size [ipAdEntReasmMaxSize]
Indicates the size of the largest IP datagram that can be reassembled (from fragmented IP
datagrams) at the interface.
IAN150/IPP MT
6/30/97
11-9
ICMP Status
The ICMP Status screen provides current statistics on Internet Control Message Protocol input
and output messages. To access the ICMP Status screen, from the Main Menu, follow the path:
4. Routing
1. IP
2. ICMP Status
or type SRIC or 1412 at the command line of any menu or screen and press Enter. The system
1.4.1.2 [SRIC] ICMP Status
Messages
Time Stamps
Dest Unreaches
Time Stamp Replies
Errors
Time Exceed Errors
Addr Masks
Addr Mask Replies
Echoes
Echo Replies
Source Quenches
Redirects
Parameter Problems
IN
0
0
0
0
0
0
0
0
0
0
0
0
0
OUT
0
0
0
0
0
0
0
0
0
0
0
0
0
Figure 11-7. ICMP Status Screen
The following paragraphs describe ICMP Status parameters. Corresponding MIB values, where
statistics that applied when the command was issued. To exit the screen, press < \ > or Esc.
Messages [icmpInMsgs] [icmpOutMsgs]
Indicates the number of ICMP messages either received or sent. Messages IN lists the number of
ICMP messages received and includes all message counted in Errors IN. Messages OUT lists the
number of ICMP messages sent and includes all message counted in Errors OUT.
Time Stamps [icmpInTimeStamps] [icmpOutTimeStamps]
Indicates the number of ICMP time stamp (request) messages either sent or received. Time
Stamps IN lists the number of ICMP time stamp (request) messages received. Time Stamps
OUT lists the number of ICMP time stamp (request) messages sent.
Dest Unreaches [icmpInDestUnreachs] [icmpOutDestUnreachs]
Indicates the number of ICMP destination unreachable messages either sent or received. Dest
Unreaches IN lists the number of ICMP destination unreachable messages received. Dest
Unreaches OUT lists the number of ICMP destination unreachable messages sent.
11-10
IAN150/IPP MT
6/30/97
Time Stamp Replies [icmpInTimeStampReps] [icmpOutTimeStampReps]
Indicates the number of ICMP time stamp reply messages either sent or received. Time Stamp
Replies IN lists the number of ICMP time stamp reply messages received. Time Stamp Replies
OUT lists the number of ICMP time stamp reply messages sent.
Errors [icmpInErrors] [icmpOutErrors]
Indicates the number of ICMP messages either sent or received. Errors IN lists the number of
ICMP messages received with errors (such as bad ICMP checksums, bad length). Errors OUT
lists the number of ICMP messages not sent due to errors (such as inability of ICMP to route
resultant datagram).
Time Exceed Errors [icmpInTimeExcds] [icmpOutTimeExcds]
Indicates the number of ICMP time exceeded messages either sent or received. Time Exceed IN
lists the number of ICMP time exceeded messages received. Time Exceed OUT lists the number
of ICMP time exceeded messages sent.
Addr Masks [icmpInAddrMasks] [icmpOutAddrMasks]
Indicates the number of ICMP address mask request messages sent or received. Addr Masks IN
lists the number of ICMP address mask request messages received. Addr Masks OUT lists the
number of ICMP address mask request messages sent.
Addr Mask Replies [icmpInAddrMaskReps] [icmpOutAddrMaskReps]
Indicates the number of ICMP address mask replies either sent or received. Addr Mask Replies
IN lists the number of ICMP address mask reply messages received. Addr Mask Replies OUT
lists the number of ICMP address mask reply messages sent.
Echoes [icmpInEchos] [icmpOutEchos]
Indicates the number of ICMP echo request messages either sent or received. Echos IN lists the
number of ICMP echo request messages received. Echos OUT lists the number of ICMP echo
request messages sent.
Echo Replies [icmpInEchoReps] [icmpOutEchoReps]
Indicates the number of ICMP echo reply messages either sent or received. Echo Replies IN lists
the number of ICMP echo reply messages received. Echo Replies OUT lists the number of
ICMP echo reply messages sent.
Source Quenches [icmpInSrcQuenchs] [icmpOutSrcQuenchs]
Indicates the number of ICMP source quench messages either sent or received. Source
Quenches IN lists the number of ICMP source quench messages received. Source Quenches
OUT lists the number of ICMP source quench messages sent.
Redirects [icmpInRedirects] [icmpOutRedirects]
Indicates the number of ICMP redirect messages either sent or received. Redirects IN lists the
number of ICMP redirect messages received. Redirects OUT lists the number of ICMP redirect
messages sent.
Parameter Problems [icmpInParmProbs] [icmpOutParmProbs]
Indicates the number of ICMP parameter problem messages either sent or received. Parameter
Problems IN lists the number of ICMP parameter problem messages received. Parameter
Problems OUT lists the number of ICMP parameter problem messages sent.
IAN150/IPP MT
6/30/97
11-11
UDP Status
The UDP Status menu provides current statistics on User Datagram Protocol operations. To
select the UDP Status menu from the Main Menu, follow the path:
4. Routing
1. IP
3. UDP Status
or type SRIU or 1413 from the command line of any menu or screen and press Enter. The
system displays the following menu:
1.4.1.3 [SRIU] UDP Status
1. UDP Statistics
2. UDP Listen Table
Figure 11-8. UDP Status Menu
UDP Status information consists of two different displays:
•
UDP Statistics - provides current statistics on User Datagram Protocol operations.
•
UDP Listener Table - lists information about User Datagram Protocol end-points on which
a local datagram is currently accessing datagrams.
UDP Statistics
The UDP Statistics screen provides current statistics on User Datagram Protocol operations. To
access the UDP Statistics screen from the Main Menu, follow the path:
4. Routing
1. IP
3. UDP Status
1. UDP Statistics
or type SRIUS or 14131 at the command line of any menu or screen and press Enter. The
1.4.1.3.1 [SRIUS] UDP Statistics
Datagrams
Octets
Errors
No Ports
IN
0
0
OUT
0
0
0
0
Figure 11-9. UDP Statistics Screen
11-12
IAN150/IPP MT
6/30/97
The following paragraphs describe UDP Statistics parameters. Corresponding MIB values, where
Datagrams [udpInDatagrams] [udpOutDatagrams]
Indicates the number of UDP datagrams either sent or received. Datagrams IN list the number of
UDP datagrams delivered. Datagrams OUT list the number of UDP datagrams sent.
Octets [polStatIpUdpInOctets] [polStatIpUdpOutOctets]
Indicates the number of UDP data octets sent either to upper or lower layer protocols. Octets IN
lists the number of UDP data octets sent to upper layer protocols. Octets OUT lists the number
of UDP data octets sent to lower layer protocols.
Errors [udpInErrors]
Indicates the number of UDP datagrams not delivered for reasons other than no application at the
destination port.
No Ports [udpNoPorts]
Indicates the number of received UDP datagrams for which there was no application at the
destination port.
UDP Listen Table
The UDP Listen Table lists information about User Datagram Protocol end-points on which a
local datagram is currently accessing datagrams. Each line in the table gives information about a
particular UDP listener. To access the UDP Listen Table screen, from the Main Menu, follow the
path:
4. Routing
1. IP
3. UDP Status
2. UDP Listen Table
or type SRIUL or 14132 at the command line of any menu or screen and press Enter. The
1.4.1.3.2 [SRIUL] UDP Listen Table
Local
UDP Address
===========
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
Local
Port Number
===========
0
0
0
0
Applications
============
N/A
N/A
N/A
N/A
Figure 11-10. UDP Listen Table Screen
IAN150/IPP MT
6/30/97
11-13
The following paragraphs describe UDP Listen Table parameters. Corresponding MIB values,
current values for a specific UDP listener not shown on page one of the table, enter the local
UDP address and port number of the listener you want to monitor, then refresh the screen by
issuing a Read Next command. The screen displays the statistics that applied when the command
was executed. To exit the screen, press < \ > or Esc.
Local UDP Address [udpLocalAddress]
Displays the local address for the UDP listener.
Local Port Number [udpLocalPort]
Displays the local port number for the UDP listener.
Applications [polstatipudpUser]
Lists the local process or application associated with the local port number.
HTTP Status
The HTTP Status menu provides access to the HTTP protocol monitoring features supported by
the IAN-150. To select this menu, from the Main Menu, follow the path:
4. Routing
1. IP
4. HTTP
or type SRIH or 1414 from the command line of any menu or screen and press Enter. The
1.4.1.4 [SRIH]
HTTP Status
1. HTTP Protocol Statistics
2. HTTP Connections
3. HTTP Users
Figure 11-11. HTTP Status Menu
HTTP Status information consists of three different displays:
•
HTTP Protocol Statistics - provides current statistics on HTTP protocol operation
•
HTTP Connections - provides information about HTTP connections and their current states
•
HTTP Users - provides statistics about HTTP users
11-14
IAN150/IPP MT
6/30/97
HTTP Protocol Statistics
The HTTP Protocol Statistics screen provides current statistics on HTTP operation, such as the
number of requests that have been received or rejected, and the number of data packets that have
been sent or received. To select the HTTP Protocol Statistics screen, from the Main Menu,
follow the path:
4. Routing
1. IP
4. HTTP
1. HTTP Protocol Statistics
or type SRIHP or 14141 from the command line of any menu or screen and press Enter.
1.4.1.4.1 [SRIHP] HTTP Protocol Statistics
Requests In
Gets In
Posts In
Peak Requests
Failed Accesses
Rejected Requests
Bytes In.
Packets In
Bytes Out
Packets Out
Segments Retransmitted
0
0
0
0
0
0
0
0
0
0
0
Figure 11-12. HTTP Protocol Statistics Screen
The following paragraphs describe HTTP Protocol Statistics parameters. Corresponding MIB
for this table, type < . > N and press Enter. The screen displays the statistics that applied when
the command was executed. To exit the screen, press < \ > or Esc.
Requests In [polStatHttpProtReqIns]
Indicates the number of requests received by the HTTP task since statistics were last reset.
Gets In [polStatHttpProtGetIns]
Indicates the number of GET requests received by the HTTP task since statistics were last reset.
Posts In [polStatHttpProtPostIns]
Indicates the number of POST requests received by the HTTP task since statistics were last reset.
Peak Requests [polStatHttpProtPeakReqIns]
Indicates the highest number of simultaneous outstanding HTTP requests since statistics were
last reset.
Failed Accesses [polStatHttpProtFailedAccesses]
Indicates the number of failed accesses received by the HTTP task since statistics were last reset.
Accesses fail due to invalid login-name/password or expired/invalid cookie.
IAN150/IPP MT
6/30/97
11-15
Rejected Requests [polStatHttpProtRejectedReqs]
Indicates the number of requests rejected by the HTTP task since statistics were last reset. The
count indicates that no connections were available at the time of the request.
Bytes In [polStatHttpProtByteIns]
Indicates the number of bytes received by the HTTP task since statistics were last reset.
Packets In [polStatHttpProtPktIns]
Indicates the number of packets received by the HTTP task since statistics were last reset.
Bytes Out [polStatHttpProtByteOuts]
Indicates the number of bytes transmitted by the HTTP task since statistics were last reset.
Packets Out [polStatHttpProtPktOuts]
Indicates the number of packets transmitted by the HTTP task since statistics were last reset.
HTTP Connections
The HTTP Connections screen lists HTTP connections, and the number of HTTP requests
received and how much time was spent processing those requests for the associated connection.
To select the HTTP connections screen from the Main Menu, follow the path:
4. Routing
1. IP
4. HTTP
2. HTTP Connections
or type SRIHC or 14142 from the command line of any menu or screen and press Enter.
1.4.1.4.2 [SRIHC] HTTP Connections
Conn ID
0
0
0
0
0
0
0
0
Requests In
0
0
0
0
0
0
0
0
Accum. Time (MS)
0
0
0
0
0
0
0
0
Last Time (MS)
0
0
0
0
0
0
0
0
Figure 11-13. HTTP Connections Screen
Conn ID [polStatHttpConnTblIndex]
Lists connection IDs of the IAN-150 HTTP connections.
Requests In [polStatHttpConnTblReqs]
Indicates the number of requests received on this connection since statistics were last reset.
11-16
IAN150/IPP MT
6/30/97
Accum Time [polStatHttpConnTblAccumTime]
Indicates the accumulated time spent processing all HTTP requests on this connection.
Last Time [polStatHttpConnTblLastTime]
Indicates the time spent processing all HTTP requests on the most recent transaction for this
connection.
HTTP Users
The HTTP User screen provides current information about HTTP users that have successfully
performed a remote log in. Inactive users will be logged out after the global X.28 inactivity time.
4. Routing
1. IP
4. HTTP
3. HTTP Users
or type SRIHU or 14143 from the command line of any menu or screen and press Enter.
1.4.1.4.3 [SRIHU] HTTP Users
Login Time (t)
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
IP address
Valid Until (t)
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Requests
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Access Level
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Figure 11-14. HTTP Users screen
Login Time [polStatHttpUserLoginTime]
Indicates the tic count at the moment this user logged in.
IP address [polStatHttpUserIpAddress]
Indicates the IP address associated with this user. Due to proxy servers, multiple users may have
a common IP Address. These users can be distinguished by login time.
IAN150/IPP MT
6/30/97
11-17
Valid Until [polStatHttpUserValidTil]
Indicates the time at which this user (if inactive) will be automatically logged out. This time is
extended to the time of the most recent transaction, plus the x.28 inactivity timeout.
Requests [polStatHttpUserNumReqs]
Indicates the number (count) of requests submitted by this user.
Access Level [polStatHttpUserUserLevel]
Indicates the user’s access class.
TCP Status and Control Menu
The TCP Status and Control menu provides access to the TCP protocol monitoring features
supported by the IAN-150. To select this menu, from the Main Menu, follow the path:
4. Routing
3. TCP
or type SRT or 143 at the command line of any menu or screen and press Enter. The system
1.4.3
[SRT] TCP Status and Control
1. Standard Statistics
2. TCP Connection Table
3. TCP Connection Statistics
4. TCP Receive Statistics
5. TCP Transmit Statistics
Figure 11-15. TCP Status and Control Menu
TCP Status information consists of five different displays:
•
Standard Statistics - provides current statistics on TCP protocol operation.
•
TCP Connection Table - provides information about TCP connections and their current
states.
•
TCP Connection Statistics - provides statistics about TCP connections, discarded data
packets, and round trip time (RTT) data packets.
•
TCP Receive Statistics - provides statistics about the TCP data packets the IAN-150 has
received.
•
TCP Transmit Statistics - provides statistics about the TCP data packets the IAN-150 has
sent out.
11-18
IAN150/IPP MT
6/30/97
TCP Standard Statistics
The TCP Standard Statistics screen provides current statistics on TCP operation, such as the
number of data packets (called segments) that have been sent out, received, or retransmitted, and
the number of closed and active connections. To select the TCP Standard Statistics screen from
the Main Menu, follow the path:
4. Routing
3. TCP
1. Standard Statistics
or type SRTS or 1431 from the command line of any menu or screen and press Enter. The
1.4.3.1 [SRTS] TCP Standard Statistics
Retransmit Timeout Algorithm
OTHER
Connections Now Open
Connections Closed
Active Opens
Passive Opens
0
0
0
0
Open Failures
Errors In
Resets Out
0
0
0
Segments In
Segments Out
Segments Retransmitted
0
0
0
Figure 11-16. TCP Standard Statistics Screen
The following paragraphs describe TCP Standard Statistics parameters. Corresponding MIB
displays the statistics that applied when the command was executed. To exit the screen, press < \
> or Esc.
Retransmit Timeout Algorithm [tcpRtoAlgorithm]
Displays the algorithm used to compute the retransmit timeout value. The system first displays
this parameter as OTHER. After you issue a Read command, the system displays the parameter
as VAN JACOBSONS.
Connections Now Open [tcpCurrEstab]
Displays the number of TCP connections for which the current state is either ESTABLISHED or
CLOSE WAIT.
Connections Closed [tcpEstabResets]
Displays the number of times TCP connections have made a direct transition to the CLOSED
state from either the ESTABLISHED state or the CLOSE WAIT state.
IAN150/IPP MT
6/30/97
11-19
Active Opens [tcpActiveOpens]
Displays the number of times TCP connections have made a direct transition to the SYN SENT
state from the CLOSED state.
Passive Opens [tcpPassiveOpens]
Displays the number of times TCP connections have made a direct transition to the SYN RCVD
state from the LISTEN state.
Open Failures [tcpAttemptFails]
Displays the number of TCP active or passive open connections that failed to be completed.
Errors In [tcpInErrs]
Displays the number of packets received in error (for example, bad TCP checksums).
Resets Out [tcpOutRsts]
Displays the number of TCP segments sent that contain the RST flag.
Segments In [tcpInSegs]
Displays the total number of segments received, including those received in error.
Segments Out [tcpOutSegs]
Displays the total number of segments sent, including those on current connections but excluding
those that contain only retransmitted octets.
Segments Retransmitted [tcpRetransSegs]
Displays the total number of segments retransmitted, that is, the number of TCP segments
transmitted that contain one or more previously transmitted octets.
11-20
IAN150/IPP MT
6/30/97
TCP Connection Table
The TCP Connection Table provides information about individual TCP connections and their
current state. To select the TCP Connection Table screen, from the Main Menu, follow the path:
4. Routing
3. TCP
2. TCP Connection Table
or type SRTT or 1432 at the command line of any menu or screen and press Enter. The system
1.4.3.2 [SRTT] TCP Connection Table
Local Address
Port
Remote Address
Port
State
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
000.000.000.000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
00000
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
CLOSED
Valid
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
Figure 11-17. TCP Connection Table Screen
Note that from this screen a TCP connection can be cleared by a management station, by setting
the State parameter to DELETE TCB, the Valid parameter to YES, then issuing a Write
command from the command line. This action causes the connection to be deleted (as opposed to
closed, which is an internal TCP state).
The following paragraphs describe TCP Connection Table parameters. Corresponding MIB
for this table, type < . > N and press Enter. The screen displays the statistics that applied when
Local Address [tcpConnLocalAddress]
Displays the IP address of the local or managed IAN-150.
Port [tcpConnLocalPort]
Displays the TCP port number on the local or managed IAN-150.
Remote Address [tcpConnRemAddress]
Displays the IP address of the TCP neighbor.
IAN150/IPP MT
6/30/97
11-21
Port [tcpConnRemPort]
Displays the TCP port number of the TCP neighbor.
State [tcpConnState]
Displays the current state of the IAN-150’s TCP connection. Possible states include:
CLOSED
No connection state is present.
LISTEN
Waiting for a connection request from any remote TCP
and port.
SYN SENT
Waiting for a matching connection request after having
sent a connection request.
SYN RECEIVED
Waiting for a confirming connection request
acknowledgment after having both received and sent a
connection request.
ESTABLISHED
Connection has been established; data received can be
delivered to the user. (This is the normal state for the
data transfer phase of the connection.)
FIN WAIT1
Waiting for a connection termination request from the
remote TCP or an acknowledgment of the connection
termination request that was previously sent.
FIN WAIT2
Waiting for a connection termination request from the
remote TCP.
CLOSE WAIT
Waiting for a connection termination request from a local
user.
LAST ACK
Waiting for an acknowledgment of the connection
termination request previously sent to the remote TCP.
CLOSING
Waiting for a connection termination request
acknowledgment from the remote TCP.
TIME WAIT
Waiting for enough time to pass to be sure the remote
TCP received the acknowledgment of its connection
termination request.
DELETE TCB
Indicates this TCP connection will be deleted by a
management station. Used only during SNMP Put or
Write operation.
Valid
This parameter tags the line on which it is included so it can be identified as the portion of the
table being affected. The WRITE command and DELETE TCB state are only effective on rows
marked YES. Available values for this parameter are YES and NO.
11-22
IAN150/IPP MT
6/30/97
TCP Connection Statistics
The TCP Connection Statistics screen provides statistics about TCP connections, discarded data
packets, and round trip time (RTT) data packets. To select the TCP Connection Statistics screen,
4. Routing
3. TCP
3. TCP Connection Statistics
or type SRTC or 1433 from the command line of any menu or screen and press Enter. The
1.4.3.3 [SRTC] TCP Connection Statistics
CONNECTION
Requests
Accepts
Established (including accepts)
Closed (including drops)
Drops
Embryonic Drops
Dropped by Retransmit Timeouts
Dropped by Keep-Alive
0
0
0
0
0
0
0
0
DISCARDS
Bad Checksum
Bad TCP Header Offset Value
Runt Packet
0
0
0
RTT UPDATES
Segments updating RTT
Segments attempting to update
0
0
Figure 11-18. TCP Connection Statistics Screen
The following paragraphs describe TCP Connection Statistics parameters. Corresponding MIB
> or Esc.
CONNECTION - These parameters display statistics about established and closed TCP
connections:
Requests [polStatTcpConnReqs]
Displays the number of connection requests received by the IAN-150 from the network or upper
layer protocols.
Accepts [polStatTcpConnAccepts]
Displays the number of connection requests accepted by the IAN-150 from the network or upper
layer protocols.
IAN150/IPP MT
6/30/97
11-23
Established (including accepts) [polStatTcpConnEstabs]
Displays the total number of TCP connections that have been established (including accepts).
Connections established include those initiated by the IAN-150 and those initiated by TCP
neighbors.
Closed (including drops) [polStatTcpConnCloses]
Displays the total number of TCP connections that have been closed, including drops.
Drops [polStatTcpConnCloseDrops]
Displays the number of aborted TCP connections initiated by either the IAN-150 or a TCP
neighbor.
Embryonic Drops [polStatTcpConnEmbryonics]
Displays the number of TCP connections aborted before the connection was completely
established (entered ESTABLISHED state).
Dropped by Retransmit Timeouts [polStatTcpRetranTOdrops]
Indicates the number of TCP connections dropped because consecutive retransmit attempts on
one connection exceeded the threshold of retransmit attempts.
Dropped by Keep Alive [polStatTcpKeepAliveDrops]
Indicates the number of TCP connections aborted after inactivity on a given connection in excess
of the upper layer protocol’s connection timeout period.
DISCARDS - These parameters display statistics that relate to segments discarded due to faulty
header information.
Bad Checksum [polStatTcpInErrChecksums]
Indicates the number of segments discarded because of bad checksum information in the packet
header.
Bad TCP Header Offset Value [polStatTcpInErrBadHdrs]
Indicates the number of segments discarded because of erroneous header offset information in the
segment.
Runt Packet [polStatTcpInErrRunts]
Indicates the number of segments discarded because they were under the minimum allowable
packet size.
RTT UPDATES - These parameters display statistics about round trip time (RTT), which is the
amount of time TCP measures between sending a byte with a particular sequence number and
receiving an acknowledgment for that sequence number:
Segments updating RTT [polStatTcpRTTUpdates]
Indicates the number of segments that trigger the round trip time to be recalculated.
Segments attempting to update [polStatTcpRTTAttempts]
Indicates the number of segments attempting to update the round trip time.
11-24
IAN150/IPP MT
6/30/97
TCP Receive Statistics
The TCP Receive Statistics screen provides information about the TCP data packets the IAN-150
has received as a TCP neighbor. To select the TCP Receive Statistics screen, from the Main
4. Routing
3. TCP
4. TCP Receive Statistics
or type SRTR or 1434 at the command line of any menu or screen and press Enter. The system
1.4.3.4 [SRTR] TCP Receive Statistics
Packet
0
0
Octet
Acknowledgment
Duplicate Acknowledgment
Unsent Data ACK
0
0
0
0
Duplicate Data
Some Data Duplicate
Out-of-Order Data
Packets After Window
Received After Closed
0
0
0
0
0
0
0
0
0
Window Probe
Window Update
0
0
Receives
In-Sequence
0
Figure 11-19. TCP Receive Statistics Screen
The following paragraphs describe TCP Receive Statistics parameters. Corresponding MIB
> or Esc.
Receives [tcpInSegs]
Indicates the total number of TCP packets received from TCP neighbors.
In-Sequence [polStatTcpInSequences] [polStatTcpInSeqOctets]
Indicates the total number of segments and bytes that arrived in sequence. In-Sequence Packet
indicates the number of TCP segments that arrived in sequence. In-Sequence Octet indicates
the number of bytes that arrived in sequence.
Acknowledgment [polStatTcpInAckSegs] [polStatTcpInAckOctets]
Indicates the number of acknowledgments TCP received that caused TCP to move to the right
edge of the window.
IAN150/IPP MT
6/30/97
11-25
Duplicate Acknowledgment [polStatTcpInAckDups]
Indicates the number of acknowledgments TCP received that did not cause TCP to move closer
to the right edge of the window.
Unsent Data ACK [polStatTcpInAckUnsentDatas]
Indicates the number of acknowledgments TCP received outside the left edge of the receive
window.
Duplicate Data [polStatTcpInCompDups] [polStatTcpInCompDupOctets]
Indicates the number of times TCP received a segment that was a complete duplicate of a
previously received data packet. Duplicate Data Packet indicates the number of segments
containing duplicated information. Duplicate Data Octet indicates the number of bytes of
duplicated information.
Some Data Duplicate [polStatTcpInPartDups] [polStatTcpInPartDupOctets]
Indicates the number of times TCP received a packet that contained both duplicated and new
data. Some Data Duplicate Packet indicates the number of segments containing some
duplicated data and some new data. Some Data Duplicate Octet indicates the number of bytes
contained in these segments.
Out-of-Order Data [polStatTcpInOutOfOrders]
[polStatTcpInOutOfOrderOctets]
Indicates the number of times TCP received a packet that contained a different sequence number
from the one expected. Out-of-Order Data Packet indicates the number of segments containing
a different sequence number from the one expected. Out-of-Order Data Octet indicates the
number of bytes contained in these segments.
Packets After Window [polStatTcpInDataAftWins]
[polStatTcpInDataAftWinsOctet]
Indicates the number of segments and bytes that arrived after the window has moved to the right.
Packets After Window Packet indicates the number of segments received; Packets After
Window Octet indicates the number of bytes received.
Received After Closed [polStatTcpInAftCloseRcvs]
Indicates the number of segments received after the TCP connection was closed.
Window Probe [polStatTcpInWinProbes]
Indicates the number of times TCP received a probe packet to see if the window is no longer
closed.
Window Update [polStatTcpInWinUpdates]
Indicates the number of times TCP changed the window size by moving the right edge of the
window to the right.
11-26
IAN150/IPP MT
6/30/97
TCP Transmit Statistics
The TCP Transmit Statistics screen provides information about TCP data packets the IAN-150
has originated. To select the TCP Transmit Statistics screen, from the Main Menu, follow the
path:
4. Routing
3. TCP
5. TCP Transmit Statistics
or type SRTX or 1435 from the command line of any menu or screen and press Enter. The
1.4.3.5 [SRTX] TCP Transmit Statistics
Packet
Octet
Data Packets
Data Retransmits
0
0
0
0
ACK Packets
ACK Packets Delayed
0
0
Urgent Packets
0
Window Probe Packets
Window Update Packets
0
0
Control Packets
0
Retransmit Timeouts
Persist Timeouts
0
0
Keep-alive Timeouts
Keep-alive Probe Sent
0
0
Figure 11-20. TCP Transmit Statistics Screen
The following paragraphs describe TCP Transmit Statistics parameters. Corresponding MIB
> or Esc.
Data Packets [tcpOutSegs] [polStatTcpOutOctets]
Indicates the total number of TCP data packets sent by the IAN-150. Data Packets Packet
indicates the actual number of TCP data packet transmitted; Data Packets Octet indicates the
number of bytes contained in these segments.
Data Retransmits [tcpRetransSegs] [polStattTcpOutRetransOctets]
Indicates the total number of data packets and bytes that the IAN-150 had to retransmit. Data
Retransmits Packet indicate the number of segments that TCP had to retransmit; Data
Retransmits Octet indicate the number of bytes contained in these segments.
IAN150/IPP MT
6/30/97
11-27
ACK Packets [polStatTcpOutAckSegs]
Indicates the total number of acknowledgment packets transmitted that contained new
acknowledgment information.
ACK Packets Delayed [polStatTcpOutAckDelays]
Indicates the number of acknowledgment packets that were not sent in response to a received
data packet one for one.
Urgent Packets [polStatTcpOutUrgentSegs]
Indicates how many times the IAN-150 sent a data packet containing an urgent pointer valid flag
in its header.
Window Probe Packets [polStatTcpOutWinProbes]
Indicates the number of times TCP sent a probe packet to see if the window is no longer closed.
Window Update Packets [polStatTcpOutWinUpdates]
Indicates the number of times TCP sent a packet that updates a neighbor’s window size, causing
the right edge of the window to move to the right.
Control Packets [polStatTcpOutCntrls]
Indicates the total number of control packets—such as SYN, FIN, and/or RST—sent.
Retransmit Timeouts [polStatTcpRetranTos]
Indicates how many times TCP retransmit timer has been evoked.
Persist Timeouts [polStatTcpPersistTos]
Indicates the number of times TCP timer has been evoked due to closed window condition.
Keep-Alive Timeouts [polStatTcpKeepAliveTos]
Indicates the number of times TCP timer has been evoked due to TCP connection inactivity.
Keep Alive Probe Sent [polStatTcpKeepAliveProbes]
Indicates the number of times TCP sent a keep-alive probe during keep-alive timer processing.
11-28
IAN150/IPP MT
6/30/97
RIP Status
The RIP Status screen provides current statistics on IP routing information packets. To access the
RIP Status screen, from the Main Menu, follow the path:
4. Routing
5. RIP
or type SRR or 145 from the command line of any menu or screen and press Enter. The system
1.4.5 [SRR] RIP Status
Packets In
0
Packets Out
0
Bad Version
Bad Size
Bad Family
Own Address
Non-Zero
Bad Port
0
0
0
0
0
0
Bad
Bad
Bad
Bad
Bad
0
0
0
0
0
Metric
Address
Command
Class
Neighbor
Figure 11-21. RIP Status Screen
The following paragraphs describe RIP Status parameters. Corresponding MIB values, where
Packets In [polStatRipInPkts]
Indicates the number of routing information packets received.
Packets Out [polStatRipOutPkts]
Indicates the number of routing information packets transmitted.
Bad Version [polStatRipBadVersions]
Indicates the number of routing information packets received with version 0.
Bad Metric [polStatRipBadMetrics]
Indicates the number of routing information packets received with metric greater than 16.
Bad Size [polStatRipBadSizes]
Indicates the number of routing information packets received with incorrect size.
Bad Address [polStatRipBadAddrs]
Indicates the number of routing information packets received with bad source address.
Bad Family [polStatRipBadFamilys]
Indicates the number of routing information packets received with family other than DoD
internet.
IAN150/IPP MT
6/30/97
11-29
Bad Command [polStatRipBadCommands]
Indicates the number of routing information packets received with neither Request nor Response
command.
Own Address [polStatRipOwnAddrs]
Indicates the number of routing information packets received with local interface source address.
Bad Class [polStatRipBadClass]
Indicates the number of routing information packets received with advertised address class D or
class E.
Non-Zero [polStatRipNonZeros]
Indicates the number of routing information packets received with a non-zero value in the must
be zero or zero field.
Bad Neighbor [polStatRipBadNbrs]
Indicates the number of routing information packets received with source address inconsistent
with interface address.
Bad Port [polStatRipBadPorts]
Indicates the number of response routing information packets received with source port not equal
to 520.
OSPF Status
The OSPF Status menu provides access to the OSPF protocol monitoring features supported by
the IAN-150. To access the OSPF Status menu, from the Main Menu, follow the path:
4. Routing
6. OSPF
or type SRO or 146 from the command line of any menu or screen and press Enter. The system
1.4.6 [SRO] OSPF Status
1. Protocol
2. Interface Data Table
3. Link State Database Status
4. Neighbor Data Table
5. Virtual Link Data Table
6. Virtual Neighbor Data Table
Figure 11-22. OSPF Status Menu
11-30
IAN150/IPP MT
6/30/97
OSPF Status information consists of six different displays:
•
Protocol - shows the number of Open Shortest Path First packets sent and received, and any
OSPF errors detected.
•
Interface Data Table - lists information about OSPF interfaces.
•
Link State Database Status - lists the tables the IAN-150 offers that provide status
information on the six different link state advertisement types.
•
Neighbor Data Table - lists information about OSPF neighbors.
•
Virtual Link Data Table - lists information about the virtual links connecting the IAN-150
to a non-adjacent OSPF backbone router.
•
Virtual Neighbor Data Table - lists information about non-adjacent neighbors connected by
virtual links.
OSPF Protocol Status
The OSPF Protocol Status screen shows the number of Open Shortest Path First packets sent and
received, and any OSPF errors detected. To access the OSPF Protocol Status screen, from the
Main Menu, follow the path:
4. Routing
6. OSPF
1. Protocol
or type SROT or 1461 from the command line of any menu or screen and press Enter. The
1.4.6.1 [SROT] OSPF Protocol Status
PACKETS
Hello
DB Desc
LS Req
IN
0
0
0
ERRORS
OSPF Pkt Too Small
Own OSPF Pkt In
Bad OSPF Pkt Type
Bad OSPF Version
Bad OSPF Checksum
Bad IP Protocol ID
Bad IP Dest Addr
Bad IP Source Addr
Area ID Mismatch
Auth Type Mismatch
Hello Timer Mismatch
E-Option Mismatch
Net Mask Mismatch
Dead Timer Mismatch
OUT
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
LS Upd
LS Ack
IN
0
0
Unk Virt Link Rtr ID
NBMA:
Unk Nbr
DB Desc: Unk Nbr
LS Req: Unk Nbr
LS Upd: Unk Nbr
LS Ack: Unk Nbr
DB Desc: Low Nbr State
LS Req: Low Nbr State
LS Upd: Low Nbr State
LS Ack: Low Nbr State
Empty LS Req Pkt
LS Req: LSA Not Found
Bad LSA Checksum
Less Recent LSA In
OUT
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Figure 11-23. OSPF Protocol Status Screen
IAN150/IPP MT
6/30/97
11-31
The following paragraphs describe OSPF Protocol Status parameters. Corresponding MIB
> or Esc.
PACKETS: The following items relate to OSPF packets:
Hello [polStatOspfInHellos] [polStatOspfOutHellos]
Indicates the number of OSPF Hello packets either sent or received. Hello IN indicates the
number of OSPF packets received. Hello OUT indicates the number of OSPF Hello packets sent.
LS Upd [polStatOspfLSUpds] [polStatOspfOutLSUpds]
Indicates the number of OSPF Link State Update packets either sent or received. LS Upd IN
indicates the number of Link State Update packets received. LS Upd OUT indicates the number
of Link State Update packets sent.
DB Desc [polStatOspfInDBDescs] [polStatOspfOutDBDescs]
Indicates the number of OSPF Database Description packets either sent or received. DB Desc IN
indicates the number of Database Description packets received. DB Desc OUT indicates the
number of Database Description packets sent.
LS Ack [polStatOspfInLSAcks] [polStatOspfOutLSAcks]
Indicates the number of OSPF Link State Acknowledgment packets either sent or received. LS
Ack IN indicates the number of Link State Acknowledgment packets received. LS Ack OUT
indicates the number of Link State Acknowledgment packets sent.
LS Req [polStatOspfInLSReqs] [polStatOspfOutLSReqs]
Indicates the number of OSPF Link State Request packets either sent or received. LS Req IN
indicates the number of Link State Request packets received. LS Req OUT indicates the number
of Link State Request packets sent.
ERRORS: The following items relate to OSPF error messages:
OSPF Pkt Too Small [polStatOspfPktTooSmalls]
Indicates the number of OSPF packets received whose size was less 24 bytes, which is the
minimum OSPF packet size. The IAN-150 will discard these packets.
Unk Virt Link Rtr ID [polStatOspfUnkVirtLinks]
Indicates the number of Hello packets with a backbone Area ID of 0 received on a non-backbone
port. Receiving such a packet is valid only if the source router has been configured as an endpoint of a virtual link. This error occurs when the router from which the packet was received was
not configured as a Virtual Link neighbor for the area associated with the receiving port.
Own OSPF Pkt In [polStatOspfRcvdOwn Pkts]
Indicates the number of OSPF packets received that were generated by this IAN-150. The IAN150 will discard these packets.
11-32
IAN150/IPP MT
6/30/97
NBMA: Unk Nbr [polStatOspfNBMAUnkNbrs]
Indicates the number of Hello packets received on a Nonbroadcast Multiaccess (NBMA) port
from an unknown neighbor. The IAN-150 will discard these packets. For NBMA interfaces, you
must specify the IP addresses of all the OSPF devices on the NBMA network. For all other
interface types, neighbors are learned through the receipt of Hello packets.
Bad OSPF Pkt Type [polStatOspfBadPktTypes]
Indicates the number of OSPF packets received whose type cannot be identified. The IAN-150
will discard these packets.
DB Desc: Unk Nbr [polStatOspfDBDescUnkNbrs]
Indicates the number of Database Description packets received from an unknown neighbor. The
IAN-150 will discard these packets.
Bad OSPF Version [polStatOspfBadVersions]
Indicates the number of OSPF packets received with an invalid version number. The current
OSPF version number is Version 2. The IAN-150 will discard these packets.
LS Req: Unk Nbr [polStatOspfLSReqUnkNbrs]
Indicates the number of Link State Request packets received from an unknown neighbor. The
Bad OSPF Checksum [polStatOspfBadChecksums]
Indicates the number of OSPF packets where a checksum error was detected. The IAN-150 will
discard these packets.
LS Upd: Unk Nbr [polStatOspfLSUpdUnkNbrs]
Indicates the number of Link State Update packets received from an unknown neighbor. The
Bad IP Protocol ID [polStatOspfBadIPProtIDs]
Indicates the number of packets received where the Protocol ID in the IP header is not the correct
value for OSPF. The IAN-150 will discard these packets.
LS Ack: Unk Nbr [polStatOspfLSAckUnkNbrs]
Indicates the number of Link State Acknowledgment packets received from an unknown
neighbor. The IAN-150 will discard these packets.
Bad IP Dest Addr [polStatOspfBadIPDestAddrs]
Indicates the number of packets received where the IP Destination Address in the IP Header is
not the IP address of this IAN-150 nor is it an OSPF Multicast address. The IAN-150 will
discard these packets.
DB Desc: Low Nbr State [polStatOspfDBDescLowNbrs]
Indicates the number of Database Description packets received from a neighbor whose state is
Down or Attempt. The IAN-150 will discard these packets.
Bad IP Source Addr [polStatOspfBadIPSrcAddrs]
Indicates the number of packets received where the IP Source Address in the IP Header is not
valid for the port on which it was received. The network portion of the address must match the
network address of the port. The IAN-150 will discard these packets.
IAN150/IPP MT
6/30/97
11-33
LS Req: Low Nbr State [polStatOspfLSReqLowNbrs]
Indicates the number of Link State Request packets received from a neighbor whose state is other
than Exchange, Loading, or Full. The IAN-150 will discard these packets.
Area ID Mismatch [polStatOspfAreaIDmis]
Indicates the number of packets received where the Area ID in the packet does not match the
Area ID configured for the port on which the packet was received. The IAN-150 will discard
these packets.
LS Upd: Low Nbr State [polStatOspfLSUpdLowNbrs]
Indicates the number of Link State Update packets received from a neighbor whose state is less
than Exchange. The IAN-150 will discard these packets.
Auth Type Mismatch [polStatOspfAuthTypeMis]
Indicates the number of packets where the Authorization Type in the packet does not match the
Authorization Type configured for the area. The IAN-150 will discard these packets.
LS Ack: Low Nbr State [polStatOspfLSAckLowNbrs]
Indicates the number of Link State Acknowledgment packets received from a neighbor whose
state is less than Exchange. The IAN-150 will discard these packets.
Hello Timer Mismatch [polStatOspfHelloTimerMis]
Indicates the number of Hello packets where the Hello Interval in the packet does not match the
Hello Interval configured for the port on which the packet was received. Two devices will not
become neighbors unless they agree on the Hello Interval.
Empty LS Req Pkt [polStatOspfEmptyLSReqPkts]
Indicates the number of Link State Request packets received that did not contain any requests for
Link State Advertisements.
E-Option Mismatch [polStatOspfEOptionMis]
Indicates the number of Hello packets where the E-bit in the packet does not match the
configured stub area option for the port on which the packet was received. The IAN-150 will set
the E-bit in a Hello packet if it has an external routing capability for the area associated with the
port; that is, it is not a stub area. Two devices will not become neighbors unless they agree on the
state of the E-bit.
LS Req: LSA Not Found [polStatOspfLSReqNotFounds]
Indicates the number of Link State Request packets that contained a request for a Link State
Advertisement not in the IAN-150’s Link State Database.
Net Mask Mismatch [polStatOspfNetMaskMis]
Indicates the number of Hello packets where the Network Mask in the packet does not match the
network mask for the port on which the packet was received. Two devices will not become
neighbors unless they agree on the Network Mask.
Bad LSA Checksum [polStatOspfBadLsaChksums]
Indicates the number of Link State Advertisements in which an invalid checksum was detected.
The IAN-150 will discard these Link State Advertisements.
11-34
IAN150/IPP MT
6/30/97
Dead Timer Mismatch [polStatOspfDeadTimerMis]
Indicates the number of Hello packets where the Dead Interval in the packet does not match the
Dead Interval configured for the port on which the packet was received. Two devices will not
become neighbors unless they agree on the Dead Interval.
Less Recent LSA In [polStatOspfRcvdLessLsas]
Indicates the number of Link State Advertisement received that are less recent than the
Corresponding Link State Advertisements in the IAN-150’s Link State Database. The IAN-150
will discard these Link State Advertisements.
OSPF Interface Data Table
The OSPF Interface Data Table lists status information on Open Shortest Path First interfaces.
To access the OSPF Internal Routing Table screen from the Main Menu, follow the path:
4. Routing
6. OSPF
2. Interface Data Table
or type SROI or 1462 from the command line of any menu or screen and type Enter. The system
1.4.6.2 [SROI] OSPF Interface Data Table
AREA
INTERFACE
TYPE STATE COST DR
BDR
============================================================================
000.000.000.000 000.000.000.000
00000 000.000.000.000 000.000.000.000
000.000.000.000 000.000.000.000
00000 000.000.000.000 000.000.000.000
000.000.000.000 000.000.000.000
00000 000.000.000.000 000.000.000.000
000.000.000.000 000.000.000.000
00000 000.000.000.000 000.000.000.000
Figure 11-24. OSPF Interface Data Table Screen
The following paragraphs describe OSPF Interface Data parameters. Corresponding MIB values,
current values for a specific OSPF interface not shown on page one of the table, enter the area
identifier and/or internet address of the interface you want to see, then refresh the screen by
AREA [polStatOspfIntfAreaID]
OSPF area identifier of the port.
INTERFACE [polStatOspfIntfIPAddr]
Internet address associated with the port.
IAN150/IPP MT
6/30/97
11-35
TYPE [polStatOspfIntfType]
OSPF network type associated with this port. There are three values possible for this field:
Bcast
Indicates a broadcast network, which is a network that supports
more than two routers and has the capability to address a single
physical message to all of the attached routers.
NBMA
Indicates a non-broadcast network, which is a network that
supports more than two attached routers but has no broadcast
capabilities.
PtoP
Indicates a point-to-point network, which is a network that
connects a single pair of routers
STATE [polStatOspfIntfState]
OSPF state of the port, where:
DR
BkDR
Oth
Down
Indicates the designated router for the network.
Indicates the backup designated router for the network.
Indicates neither DR nor BKUPDR.
Indicates the interface is down at the driver level.
COST [polStatOspfIntfCost]
Indicates OSPF cost for the interface.
DR [polStatOspfIntfDR]
Indicates IP address of the designated router for the network.
BDR [polStatOspfIntfBDR]
Indicates IP address of the backup designated router for the network.
11-36
IAN150/IPP MT
6/30/97
OSPF Link State Database Status
The OSPF Link State Database Status screen is a menu listing the tables the IAN-150 offers that
provide status information on the six different link state advertisement types. To access the OSPF
Link State Database Status menu from the Main Menu, follow the path:
4. Routing
6. OSPF
or type SROL or 1463 from the command line of any menu or screen and press Enter. The
1.4.6.3 [SROL] OSPF Link State Database Status
1. OSPF Link State Database Table - STUB Type
2. OSPF Link State Database Table - RTR Type
3. OSPF Link State Database Table - NET Type
4. OSPF Link State Database Table - NET SUM Type
5. OSPF Link State Database Table - AS SUM Type
6. OSPF Link State Database Table - EXT Type
Figure 11-25. OSPF Link State Database Status Menu
The OSPF Link State Database Status menu provides access to the following six displays:
•
OSPF Link State Database Table - STUB Type - lists STUB-type OSPF link state
advertisements.
•
OSPF Link State Database Table - RTR Type - lists OSPF router link advertisements.
•
OSPF Link State Database Table - NET Type - lists OSPF network link advertisements.
•
OSPF Link State Database Table - NET SUM Type - lists OSPF Type 3 summary link
advertisements.
•
OSPF Link State Database Table - AS SUM Type - lists OSPF Type 4 summary link
advertisements.
•
OSPF Link State Database Table - EXT Type - lists OSPF AS external link
advertisements.
IAN150/IPP MT
6/30/97
11-37
OSPF Link State Database Table - STUB Type
This OSPF Link State Database Table lists STUB-type OSPF link state advertisements. STUB
signifies a stub network (internally generated). To access the OSPF Link State Database Table STUB Type screen, from the Main Menu follow the path:
4. Routing
6. OSPF
1. OSPF Link State Database Table - STUB Type
or type SROLS or 14631 from the command line of any menu or screen and press Enter. The
1.4.6.3.1 [SROLS] OSPF Link State Database Table - STUB Type
AREA
LS ID
ADV ROUTER
COST
AGE
LEN
SEQ #
==============================================================================
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
Figure 11-26. OSPF Link State Database Table - STUB Type Screen
The following paragraphs describe OSPF Link State Database Table - STUB parameters.
Enter. To view the current values for a specific link state advertisement not displayed on page
one of the table, enter the area identifier and/or network number or network address of the entry
you want to see, then refresh the screen by issuing a Read Next command. The screen displays
the statistics that applied when the command was executed. To exit the screen, press < \ > or Esc.
AREA [polStatOspfLsdbAreaID]
OSPF area identifier associated with the link state advertisement.
LS ID [polStatOspfLsdbLinkID]
Link ID for the link state advertisement.
ADV ROUTER [polStatOspfLsdbAdvRtr]
Advertising router ID that initiated the link state advertisement.
COST [polStatOspfLsdbMetric]
Dynamically determined value associated with the link state advertisement.
AGE [polStatOspfLsdbAge]
Age, in seconds, of the advertisement.
11-38
IAN150/IPP MT
6/30/97
LEN [polStatOspfLsdbHdrLen]
Length, in bytes, of the advertisement.
SEQ # [polStatOspfLsdbHdrSeq]
Sequence number of the advertisement.
OSPF Link State Database Table - RTR Type
The OSPF Link State Database Table - RTR Type lists OSPF router link advertisements. Router
link advertisements are originated by routers and IAN-150s within the OSPF topology. To access
the OSPF Link State Database Table - RTR Type screen, from the Main Menu follow the path:
4. Routing
6. OSPF
2. OSPF Link State Database Table - RTR Type
or type SROLR or 14632 from the command line of any menu or screen and press Enter. The
1.4.6.3.2 [SROLR] OSPF Link State Database Table - RTR Type
AREA
LS ID
ADV ROUTER
COST
AGE
LEN
SEQ #
==============================================================================
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
Figure 11-27. OSPF Link State Database Table - RTR Type Screen
The following paragraphs describe OSPF Link State Database Table - RTR parameters.
Enter. To view the current values for a specific router link advertisement not displayed on page
Indicates the OSPF area identifier associated with the link state advertisement.
IAN150/IPP MT
6/30/97
11-39
Indicates the dynamically determined value associated with the link state advertisement.
Indicates age, in seconds, of the advertisement.
Indicates length, in bytes, of the advertisement.
Indicates sequence number of the advertisement.
OSPF Link State Database Table - NET Type
The OSPF Link State Database Table - NET Type lists OSPF network link advertisements.
Network link advertisements are originated by the network device acting as the designated router
within the OSPF topology. To access the OSPF Link State Database Table - NET Type screen,
from the Main Menu follow the path:
4. Routing
6. OSPF
3. OSPF Link State Database Table - NET Type
or type SROLN or 14633 from the command line of any menu or screen and press Enter. The
1.4.6.3.3 [SROLN] OSPF Link State Database Table - NET Type
AREA
LS ID
ADV ROUTER
COST
AGE
LEN
SEQ #
==============================================================================
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
Figure 11-28. OSPF Link State Database Table - NET Type Screen
The following paragraphs describe OSPF Link State Database Table - NET parameters.
Enter. To view the current values for a specific network link advertisement not displayed on
page one of the table, enter the area identifier and/or network number or network address of the
entry you want to see, then refresh the screen by issuing a Read Next command. The screen
> or Esc.
11-40
IAN150/IPP MT
6/30/97
OSPF Link State Database Table - NET SUM Type
The OSPF Link State Database Table - NET SUM Type lists OSPF Type 3 summary link
advertisements. Type 3 summary link advertisements are used when the destination is an IP
network. Type 3 summary link advertisements are originated by network devices acting as border
area routers within the OSPF topology. To access the OSPF Link State Database Table - NET
SUM Type screen, from the Main Menu, follow the path:
4. Routing
6. OSPF
4. OSPF Link State Database Table - NET SUM Type
or type SROLU or 14634 from the command line of any menu or screen and press Enter. The
1.4.6.3.4 [SROLU] OSPF Link State Database Table - NET SUM Type
AREA
LS ID
ADV ROUTER
COST
AGE
LEN
SEQ #
==============================================================================
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
Figure 11-29. OSPF Link State Database Table - NET SUM Type Screen
IAN150/IPP MT
6/30/97
11-41
The following paragraphs describe OSPF Link State Database Table - NET SUM
parameters.Corresponding MIB values, where applicable, appear in brackets next to the
parameter names. To view the current data on this table, issue a Read Next command by typing
< . > N and pressing Enter. To view the current values for a specific summary link
advertisement not displayed on page one of the table, enter the area identifier and/or network
number or network address of the entry you want to see, then refresh the screen by issuing a
11-42
IAN150/IPP MT
6/30/97
OSPF Link State Database Table - AS SUM Type
The OSPF Link State Database Table - AS SUM Type screen lists OSPF Type 4 summary link
advertisements. Type 4 summary link advertisements are used when the destination is an
autonomous system (AS) boundary router. Type 4 summary link advertisements are originated
by network devices acting as border area routers within the OSPF topology. To access the OSPF
Link State Database Table - AS SUM Type screen, from the Main Menu follow the path:
4. Routing
6. OSPF
5. OSPF Link State Database Table - AS SUM Type
or type SROLA or 14635 from the command line of any menu or screen and press Enter. The
1.4.6.3.5 [SROLA] OSPF Link State Database Table - AS SUM Type
AREA
LS ID
ADV ROUTER
COST
AGE
LEN
SEQ #
==============================================================================
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
Figure 11-30. OSPF Link State Database Table - AS SUM Type Screen
The following paragraphs describe OSPF Link State Database Table - AS SUM parameters.
Enter. To view current values for a specific summary link advertisement not displayed on page
IAN150/IPP MT
6/30/97
11-43
OSPF Link State Database Table - EXT Type
The OSPF Link State Database Table - EXT Type lists OSPF AS external link advertisements.
AS external link advertisements are originated by the network devices acting as AS boundary
routers within the OSPF topology. To access the OSPF Link State Database Table - EXT Type
screen, from the Main Menu follow the path:
4. Routing
6. OSPF
6. OSPF Link State Database Table - EXT Type
or type SROLE or 14636 from the command line of any menu or screen and press Enter. The
1.4.6.3.6 [SROLE] OSPF Link State Database Table - EXT Type
AREA
LS ID
ADV ROUTER
COST
AGE
LEN
SEQ #
==============================================================================
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
000.000.000.000 000.000.000.000 000.000.000.000 00000000 00000 0000 00000000
Figure 11-31. OSPF Link State Database Table - EXT Type Screen
The following paragraphs describe OSPF Link State Database Table - EXT parameters.
Enter. To view the current values for a specific external link advertisement not displayed on
page one of the table, enter the area identifier and/or network number or network address of the
entry you want to see, then refresh the screen by issuing a Read Next command. The screen
> or Esc.
11-44
IAN150/IPP MT
6/30/97
OSPF Neighbor Data Table
The OSPF Neighbor Data Table lists information about OSPF neighbors. To access the OSPF
Neighbor Data Table screen, from the Main Menu, follow the path:
4. Routing
6. OSPF
4. Neighbor Data Table
or type SRON or 1464 from the command line of any menu or screen and press Enter. The
1.4.6.4 [SRON] OSPF Neighbor Data Table
AREA
NBR IP ADDR
ROUTER ID
INTERFACE
STATE MODE PRI
============================================================================
000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
000
000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
000
000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
000
000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
000
000.000.000.000 000.000.000.000 000.000.000.000 000.000.000.000
000
Figure 11-32. OSPF Neighbor Data Table Screen
The following paragraphs describe OSPF Neighbor Data Table parameters. Corresponding MIB
values, where applicable, appear in brackets next to the parameter names. To view the current
data on this table, issue a Read Next command by typing < . > N and pressing Enter. To view
current values for a specific OSPF neighbor not displayed on page one of the table, enter the area
identifier and/or IP address of the neighbor you want to see, then refresh the screen by issuing a
AREA [polStatOspfNbrAreaID]
Identifiews the OSPF area identifier of the neighbor.
NBR IP ADDR [polStatOspfNbrIpAddr]
Indicates IP address of the OSPF neighbor.
IAN150/IPP MT
6/30/97
11-45
ROUTER ID [polStatOspfNbrID]
Indicates router identifier of the OSPF neighbor.
INTERFACE [polStatOspfNbrIfIpAddr]
Indicates the internet address associated with the interface of the neighbor.
STATE [polStatOspfNbrState]
Indicates the OSPF state of the neighbor. Values for this field are:
Down
Initial state of a neighbor. It indicates there has been no recent
information received from this neighbor.
Init
Indicates that Hello packets have been recognized from this neighbor
but that bi-directional communication has not yet been established.
ExSt
First step to create an adjacency with this neighbor; the IAN-150 and
this neighbor decide who will be master and slave.
Exch
Indicates the neighbor is describing its entire link state database by
sending Database Description packets to the IAN-150.
Load
Indicates the neighbor is sending Link State Request packets to the
IAN-150, asking for the more recent advertisements that it discovered
in the Exchange state but has not yet received.
Full
Indicates the neighboring devices are now fully adjacent.
2Wy
Indicates that communication between the IAN-150 and this neighbor
is bi-directional.
MODE [polStatOspfNbrMode]
OSPF mode of the neighbor. When two neighbors are exchanging databases, they form a
master/slave relationship. Values for this field are:
Master
Indicates this neighbor sends the first Database Description packet and is the
only device that can retransmit information.
Slave
Indicates this neighbor can only respond to the Database Description packets
sent by the IAN-150.
None
Indicates this neighbor is neither master nor slave.
PRI [polStatOspfNbrPri]
Indicates the priority associated with the neighbor.
11-46
IAN150/IPP MT
6/30/97
OSPF Virtual Link Data Table
The OSPF Virtual Link Data Table lists information about OSPF virtual links connecting nonadjacent OSPF backbone routers. To access the OSPF Virtual Link Data Table screen, from the
Main Menu, follow the path:
4. Routing
6. OSPF
5. Virtual Link Data Table
or type SROV or 1465 from the command line of any menu or screen and press Enter. The
1.4.6.5 [SROV] OSPF Virtual Link Data Table
TR AREA
NBR ID
TYPE
STATE COST
NBR IP ADDRESS
============================================================================
000.000.000.000 000.000.000.000
00000 000.000.000.000
000.000.000.000 000.000.000.000
00000 000.000.000.000
000.000.000.000 000.000.000.000
00000 000.000.000.000
000.000.000.000 000.000.000.000
00000 000.000.000.000
000.000.000.000 000.000.000.000
00000 000.000.000.000
Figure 11-33. OSPF Virtual Link Data Table Screen
The following paragraphs describe OSPF Virtual Link Data Table parameters. Corresponding
MIB values, where applicable, appear in brackets next to the parameter names. To view the
current data on this table, issue a Read Next command by typing < . > N and pressing Enter. To
view the current values for a specific virtual link not displayed on page one of the table, enter the
transit area ID or the ID of the virtual neighbor you want to see, then refresh the screen by
TR AREA [polStatOspfVLnkAreaID]
Indicates transit area ID of the area adjacent to the OSPF backbone, through which the virtual
link passes.
NBR ID [polStatOspfVLnkNbrID]
Indicates ID of the virtual neighbor, which is the destination OSPF backbone router.
IAN150/IPP MT
6/30/97
11-47
TYPE [polStatOspfVLnkType]
Indicates OSPF type of the virtual neighbor. There are four values possible for this field:
Bcast
Indicates a broadcast network, which is a network that supports
more than two routers and has the capability to address a single
physical message to all of the attached routers.
NBMA
Indicates a non-broadcast network, which is a network that
supports more than two attached routers but has no broadcast
capabilities.
PtoP
Indicates a point-to-point network, which is a network that joins a
single pair of routers
Indicates a virtual network.
Virt
STATE [polStatOspfVLnkState]
Dynamic displayed state of the OSPF virtual neighbor. Values for this field are:
Down
Initial state of a neighbor. It indicates that there has been no recent
DR
Indicates the designated router for the network.
BkDR
Indicates the backup designated router for the network.
Oth
Indicates neither designated nor backup designated router for the
network.
COST [polStatOspfVLnkCost]
Indicates the dynamically configured value attached to the virtual link.
NBR IP ADDRESS [polStatOspfVLnkNbrIP]
Indicates IP address of the OSPF virtual neighbor.
11-48
IAN150/IPP MT
6/30/97
OSPF Virtual Neighbor Data Table
The OSPF Virtual Neighbor Data Table lists information about OSPF virtual neighbors. To
access the OSPF Virtual Neighbor Data Table screen, from the Main Menu, follow the path:
4. Routing
6. OSPF
6. Virtual Neighbor Data Table
or type SROR or 1466 from the command line of any menu or screen and press Enter. The
1.4.6.6 [SROR] OSPF Virtual Neighbor Data Table
VIRT INTERFACE
ROUTER ID
NBR IP ADDR
STATE MODE
PRI
============================================================================
000.000.000.000 000.000.000.000 000.000.000.000
000
000.000.000.000 000.000.000.000 000.000.000.000
000
000.000.000.000 000.000.000.000 000.000.000.000
000
000.000.000.000 000.000.000.000 000.000.000.000
000
000.000.000.000 000.000.000.000 000.000.000.000
000
000.000.000.000 000.000.000.000 000.000.000.000
000
Figure 11-34. OSPF Virtual Neighbor Data Table Screen
The following paragraphs describe OSPF Virtual Neighbor Data Table parameters.
Enter. To view the current values for a specific virtual neighbor not displayed on page one of the
table, enter the physical port number through which the virtual link is made, and/or the ID or IP
address of the virtual neighbor you want to see, then refresh the screen by issuing a Read Next
VIRT INTERFACE [polStatOspfVirtNbrIfIpAddr]
Indicates the physical port through which the virtual link is made to the destination OSPF
backbone router.
ROUTER ID [polStatOspfVirtRtrID]
Indicates the ID of the virtual neighbor, which is the destination OSPF backbone router.
NBR IP ADDR [polStatOspfVirtNbrIpAddr]
Indicates IP address of the OSPF virtual neighbor.
IAN150/IPP MT
6/30/97
11-49
STATE [polStatOspfVirtNbrState]
Indicates OSPF state of the virtual neighbor. Values for this field are:
Down
Initial state of a neighbor. It indicates that there has been no recent
Init
Indicates that Hello packets have been recognized from this neighbor
but that bi-directional communication has not yet been established.
ExSt
First step to create an adjacency with this neighbor; the IAN-150 and
this neighbor decide who will be master and slave.
Exch
Indicates the neighbor is describing its entire link state database by
sending Database Description packets to the IAN-150.
Load
Indicates the neighbor is sending Link State Request packets to the
IAN-150, asking for the more recent advertisements that it discovered
in the Exchange state but has not yet received.
Full
Indicates the neighboring devices are now fully adjacent.
2WY
Indicates that communication between the IAN-150 and this neighbor
is bi-directional.
MODE [polStatOspfVirtNbrMode]
Indicates OSPF mode of the virtual neighbor. Values for this field are:
Master
Indicates this neighbor sends the first Database Description packet and is the
only device that can retransmit information.
Slave
Indicates this neighbor can only respond to the Database Description packets
sent by the IAN-150.
None
Indicates this neighbor is neither master nor slave.
PRI [polStatOspfVirtNbrPri]
Indicates the priority associated with the virtual neighbor.
11-50
IAN150/IPP MT
6/30/97
EGP Status
The EGP Control and Status menu provides access to the EGP protocol monitoring features
supported by the IAN-150. To access the EGP Control and Status menu, from the Main Menu,
follow the path:
4. Routing
7. EGP
or type SRE or 147 from the command line of any menu or screen and press Enter. The system
1.4.7 [SRE] EGP Control and Status
1. EGP Statistics
2. EGP Neighbor Table
Figure 11-35. EGP Control and Status Menu
EGP Control and Status information consists of two different displays:
•
EGP Statistics - provides current status and statistics on Exterior Gateway Protocol
operations.
•
EGP Neighbor Table - lists status information for Exterior Gateway Protocol.
IAN150/IPP MT
6/30/97
11-51
EGP Statistics
The EGP Statistics screen provides current status and statistics on Exterior Gateway Protocol
operations. To access the EGP Statistics screen, from the Main Menu, follow the path:
4. Routing
7. EGP
1. EGP Statistics
or type SRES or 1471 from the command line of any menu or screen and press Enter. The
1.4.7.1 [SRES] EGP Statistics
Auto System Number
Number Trusted Neighbors
Number Neighbors Recommended
Max Neighbors
Messages
Errors
0
0
0
0
IN
0
0
OUT
0
0
Figure 11-36. EGP Statistics Screen
The following paragraphs describe EGP Statistics parameters. Corresponding MIB values, where
Auto System Number [egpAs]
Indicates EGP identification number of interior system to which this gateway device is
connected. This is not a network address.
Number Trusted Neighbors [polEgpTrustedNeighbors]
Indicates the number of neighboring EGP processes that the EGP can acquire; the range is from 0
to Max Neighbors.
Number Neighbors Recommended [polEgpTrustedNeighbors]
Indicates recommended number of neighboring EGP processes with which EGP may attempt to
establish communications; the range is from 0 to Number Trusted Neighbors.
Max Neighbors [polEgpMaxNeighbors]
Indicates maximum number of EGP neighbors permitted for this gateway.
Messages [egpInMsgs] [egpOutMsgs]
Messages IN indicates the number of EGP messages received without error. Messages OUT
indicates the number of locally generated EGP messages.
Errors [egpInErrors] [egpOutErrors]
Errors IN indicate Number of EGP messages received with errors. Errors OUT indicate the
number of locally generated EGP messages not sent due to local resource limitations.
11-52
IAN150/IPP MT
6/30/97
EGP Neighbor Table
The EGP Neighbor Table lists status information for Exterior Gateway Protocol neighbor
gateways. To access the EGP Neighbor Table screen, from the Main Menu, follow the path:
4. Routing
7. EGP
2. EGP Neighbor Table
or type SRET or 1472 from the command line of any menu or screen and press Enter. The
1.4.7.2 [SRET] EGP Neighbor Table
Neigh.Address:
Neighbor State:
Auto.Sys. No.:
Neighbor Mode:
Event Trigger:
Hello Interval:
Poll Interval:
000.000.000.000
IDLE
0
ACTIVE
START
0
0
Neigh. Address:
Neigh. State:
Auto. Sys. No.:
Neighbor Mode:
Event Trigger:
Hello Interval:
Poll Interval:
000.000.000.000
IDLE
0
ACTIVE
START
0
0
Message:
Errors:
Err Msgs:
IN
0
0
0
State:
Message:
Errors:
Err Msgs:
State:
OUT
0
0
0
UPS
0
DOWNS
0
IN
0
0
OUT
0
0
0
0
UPS
0
DOWNS
0
Figure 11-37. EGP Neighbor Table Screen
The following paragraphs describe EGP Neighbor parameters. Corresponding MIB values, where
applicable, appear in brackets next to the parameter names. To view the current data on this table,
issue a Read Next command by typing < . > N and pressing Enter. To view current values for a
specific neighbor gateway not displayed on page one of the table, enter the IP address of the EGP
neighbor you want to see, then refresh the screen by issuing a Read Next command. The screen
> or Esc.
Neigh. Address [egpNeighAddr]
Indicates the internet address of an EGP neighbor for which status information is listed.
Neighbor State [egpNeighState]
Indicates the EGP state of this neighbor. Possible states include:
IAN150/IPP MT
6/30/97
IDLE
Indicates the neighbor is idle.
ACQUISITION
Indicates the neighbor is in the process of acquiring to become a
neighbor.
DOWN
Indicates the neighbor is not functioning.
UP
Indicates the neighbor is operational.
CEASE
Indicates the neighbor is requesting termination of the neighbor
relationship.
11-53
Message [egpNeighInMsgs] [egpNeighOutMsgs]
Indicates the number of EGP error-free messages either received from or generated for this
neighbor. Message In indicates the number of EGP messages received without error from this
neighbor. Message Out indicates the number of EGP messages locally generated and sent to this
EGP peer.
Auto. Sys No. [egpNeighAs]
Indicates the autonomous system number for this neighbor.
Errors [egpNeighInErrs] [egpNeighOutErrs]
Errors In indicates the number of EGP messages received with error from this neighbor. Errors
Out indicates the number of locally generated EGP messages not sent due to resource limitations
in this EGP entity.
Neighbor Mode [egpNeighMode]
Indicates the polling mode for this neighbor. There are two modes:
PASSIVE Indicates this neighbor is a Passive EGP router.
ACTIVE Indicates this neighbor is an Active EGP router.
Err Msgs [egpNeighInErrMsgs] [egpNeighOutErrMsgs]
Indicates the number of EGP-defined error messages either received from this peer or sent to this
peer. Err Msgs In indicates the number of error messages received from this peer. Err Msgs
Out indicates the number of error messages sent to this peer.
Event Trigger [egpNeighEventTrigger]
Indicates the status of the event trigger for this neighbor.
STOP
START
Indicates the neighbor’s state is UP.
Indicates the neighbor’s state is either IDLE, ACQUISITION, DOWN, or
CEASE.
Hello Interval [egpNeighIntervalHello]
Indicates the minimum interval, in hundredths of a second, between receipt of successive hello
messages from neighbor gateways on the exterior network. A typical reading is 30. This
represents the T1 timer defined in RFC 904 .
Poll Interval [egpNeighIntervalPoll]
Indicates the minimum interval, in hundredths of a second, between receipt of successive poll
messages from neighbor gateways on the exterior network. A typical reading is 60. This
represents the T3 timer defined in RFC 904.
State [egpNeighStateUps] [egpNeighStateDowns]
State Ups indicates the number of EGP state transitions to the Up state. State Downs indicates
the number of EGP state transitions from the Up state to any other state with this peer.
11-54
IAN150/IPP MT
6/30/97
BOOTP Protocol
The BOOTP Status screen provides statistics about BOOTP requests and replies. To access the
BOOTP Status screen from the Main Menu, follow the path:
4. Routing
8. BOOTP
or type SRB or 148 from the command line of any menu or screen and press Enter. The system
1.4.8 [SRB] BOOTP Status
In Requests
In Replies
Out Forwarded
Max Hops Exceeded
Below Timeout
Bad Opcode
Bad Length
0
0
0
0
0
0
0
Figure 11-38. BOOTP Status Screen
The following paragraphs describe BOOTP Status parameters. Corresponding MIB values,
> or Esc.
In Requests [polStatBootpInRequests]
Indicates the number of BOOTP request packets received.
In Replies [polStatBootpInReplies]
Indicates the number of BOOTP reply packets received.
Out Forwarded [polStatBootpOutForwardeds]
Indicates the number of BOOTP packets forwarded.
Max Hops Exceeded [polStatBootpMaxHopsExceededs]
Indicates the number of BOOTP packets discarded because their hop counter exceeded the
Maximum Forwarding Hops value.
Below Timeout [polStatBootpBelowTimeouts]
Indicates the number of BOOTP packets discarded because their Delay Forwarding Time (Secs)
field value was smaller than the hold time.
Bad Opcode [polStatBootpBadOpcodes]
Indicates the number of BOOTP packets discarded because of a bad packet op code.
Bad Length [polStatBootpBadLengths]
Indicates the number of BOOTP packets discarded because of a smaller than minimal BOOTP
header length.
IAN150/IPP MT
6/30/97
11-55
Chapter
12
IPX Monitoring
NOTE:
noted.
The IAN 150 provides extensive capabilities, through the use of various informational displays,
to help you monitor IPX routing. This chapter describes these capabilities.
IPX Monitoring Tips
and press Enter.
To end the Monitor process and remain at this screen,
press < . >.
To exit the screen, press < \ > or Esc.
IAN150/IPP MT
6/30/97
12-1
Chapter 12, IPX Monitoring
IPX Status
The IPX Status screens provide monitoring information about the IPX routing protocol. To select
the IPX Status menu, from the Main Menu, follow the path:
4. Routing
2. IPX
or enter SRX or 142 from the command line of any menu or screen and press Enter. The system
1.4.2 [SRX] IPX Status
1. Protocol
2. SAP
3. Routing Table
4. SAP Table
Figure 12-1. IPX Status Menu
From this menu, you can access the individual status displays and tables.
12-2
IAN150/IPP MT
6/30/97
IPX Protocol Status
The IPX Protocol Status screen provides datagram transmission and discard information, echo
message, error message, and RIP message information about the IPX routing protocol. The
values shown on this screen represent the cumulative totals for all ports running IPX for this
IAN-150. To select the IPX Protocol Status screen from the Main Menu, follow the path:
4. Routing
2. IPX
1. Protocol
or enter SRXP or 1421 from the command line of any menu or screen and press Enter. The
1.4.2.1 [SRXP] IPX Protocol Status
Total Datagrams In
Total Datagrams Out
Routing Table Entries
Static Routes Defined
Dgrams Addrsd to Local Device
Total Error Msgs Generated
Header Error Discards
Datagrams Forwarded
Datagrams Unable to be Routed
Unknown Error Types
Unknown Message Types
Number Times Rcvd Own RIP Msg
Discarded Dgrams (Filtered)
Routes W/Max Hops Too Big
Err Type|Bcast In Msgs W/Errs
Message Size Errors
Num Rts Found on First Try
Rte Entries Discarded (Resrc)
Rte Entries W/Bad NW Numbers
3
28
7
0
3
0
0
0
0
0
0
0
0
0
0
0
9
0
0
ECHO MESSAGES
Unsupported Socket In
Echo Type Messages In
Reply Messages In
Reply Messages Out
ERROR MESSAGES
Unspecified
Checksum
Socket
No Resources
No Host
Max Hops
Size Too Big
RIP MESSAGES
Pkt In W/No Route
Source Not a Neighbor
Unknown Routing Type
0
0
0
0
IN
0
0
0
0
0
0
0
OUT
0
0
0
0
0
0
0
0
0
0
Figure 12-2. IPX Protocol Status Screen
The following paragraphs describe IPX Protocol Status parameters. Corresponding MIB values,
> or Esc.
Total Datagrams In [polStatIpxInPkts]
Indicates the total number of data packets received by this IAN-150, including errors.
Total Datagrams Out [polStatIpxOutSends]
Indicates the total number of datagrams transmitted by this IAN-150.
Routing Table Entries [polStatIpxNumRts]
Indicates the total number of entries, both dynamic and static, included in the IPX routing table.
IAN150/IPP MT
6/30/97
12-3
Static Routes Defined [polStatIpxNumStatRts]
Indicates the total number of configured IPX static routes.
Dgrams Addrsd to Local Device [polStatIpxInLcl]
Indicates the number of messages addressed to this IAN-150.
Total Error Msgs Generated [polStatIpxErrOutMsgs]
Indicates the total number of output error messages generated by this IAN-150. Values for this
field will be generated only if the Error Protocol Status parameter from IPX Port Configuration
screen (2.4.2.2) is set to ENABLED.
Header Error Discards [polStatIpxInHdrErrors]
Indicates the number of data packets discarded due to errors in the packet header.
Datagrams Forwarded [polStatIpxDgmsForwarded]
Indicates the number of data packets successfully forwarded.
Datagrams Unable to be Routed [polStatIpxOutNoRoute]
Indicates the number of outbound data packets that could not be routed.
Unknown Error Types [polStatIpxUnknErrType]
Indicates the number of error input messages received with an error type not recognized by the
Error protocol.
Unknown Message Types [polStatIpxUnknMsgType]
Indicates the number of input messages with unknown packet type.
Number Times Rcvd Own RIP Msg [polStatIpxOwnAddr]
Indicates the number of times an IPX port on this IAN-150 received its own RIP message.
Discarded Dgrams (Filtered) [polStatIpxDiscardFilter]
Indicates the number of messages discarded by filtering.
Routes W/Max Hops Too Big [polStatIpxDiscardBadMetric]
Indicates the number of routing message entries in a RIP packet where the maximum hop value
of 16 has been exceeded.
Err Type|Bcast In Msgs W/Errs [polStatIpxErrOutErrs]
Indicates the number of error or broadcast input messages that contained errors.
Message Size Errors [polStatIpxErrBadSize]
Indicates the total number of input messages that were either too small or too large.
Num Rts Found on First Try [polStatIpxRtFnd1stTry]
Indicates the number of times a route was located in the IPX route table on the first try.
Rte Entries Discarded (Resrc) [polStatIpxRtDiscard]
Indicates the number of times a route could not be saved due to lack of resources.
Rte Entries W/Bad NW Numbers [polStatIpxRtBadNw]
Indicates the number of routing message entries with bad network numbers.
12-4
IAN150/IPP MT
6/30/97
ECHO MESSAGES - The following items relate to echo messages:
Unsupported Socket In [polStatIpxInEchoReqs]
Indicates the number of echo messages received for an unsupported socket.
Echo Type Messages In [polStatIpxErrInEchos]
Indicates the number of echo type messages received by this IAN-150.
Reply Messages In [polStatIpxInEchoReplies]
Indicates the number of echo reply messages received by this IAN-150.
Reply Messages Out [polStatIpxOutEchoReplies]
Indicates the number of echo replies sent by this IAN-150.
ERROR MESSAGES - The following items relate to Error Protocol messages:
Unspecified [polStatIpxErrInUnspec] [polStatIpxErrOutUnspec]
Indicates the number of error messages of type unspecified either sent out or received. There are
two kinds of unspecified error messages: 0, which means that an unspecified error is detected at
destination, and 200H, which means that an unspecified error occurred before reaching
destination.
Checksum [polStatIpxErrInCksum] [polStatIpxErrOutCksum]
Indicates the number of error messages of type checksum either sent out or received. There are
two kinds of checksum error messages: 1, which means that the checksum is incorrect, or that the
packet has some other serious inconsistency detected at destination, and 201H, which means that
the checksum is incorrect, or that the packet has some other serious inconsistency before reaching
destination.
Socket [polStatIpxErrInSocket] [polStatIpxErrOutSocket]
Indicates the number of error messages of type socket either sent out or received. Socket error
messages (Error number 2) indicate that the specified socket does not exist at the specified
destination host.
No Resources [polStatIpxErrInRescs] [polStatIpxErrOutRescs]
Indicates the number of error messages of type no resources either sent out or received. No
resources error messages (Error number 3) indicate that the destination cannot accept the packet
due to resource limitations.
No Host [polStatIpxInErrNoHost] [polStatIpxErrOutNoHost]
Indicates the number of error messages of type nohost either sent out or received. No Host error
messages (Error number 202H) indicate that the destination host cannot be reached from this
port.
Max Hops [polStatIpxErrInMaxHops] [polStatIpxErrOutMaxHops]
Indicates the number of error messages of type maxhop either sent out or received. Max Hops
error messages (Error number 203H) indicate that the packet has passed through 15 internet
routers without reaching its destination.
IAN150/IPP MT
6/30/97
12-5
Size Too Big [polStatIpxErrInSizeTooBig] [polStatIpxErrOutSizeTooBig]
Indicates the number of error messages of type sizetoobig either sent out or received. Size Too
Big error messages (Error number 204H) indicate that the packet is too large to be forwarded
through some intermediate network.
RIP MESSAGES - The following items relate to RIP messages:
Pkt In W/No Route [polStatIpxRipNoRt]
Indicates the number of RIP messages received with no routes.
Source Not a Neighbor [polStatIpxRipBadSrc]
Indicates the number of RIP messages received from sites that are not neighbors.
Unknown Routing Type [polStatIpxRipBadType]
Indicates the number of RIP messages received with unknown routing type.
IPX Service Advertising Protocol Status
The IPX Service Advertising Protocol (SAP) screen provides monitoring information about the
Service Advertising Protocol. To select the IPX SAP Status screen, from the Main Menu, follow
the path:
4. Routing
2. IPX
2. SAP
or enter SRXS or 1422 from the command line of any menu or screen and press Enter. The
1.4.2.2 [SRXS] IPX SAP Status
Service Advertisement Protocol (SAP) Status
SAP table entries
SAP messages received with no service
SAP messages entries with intermediate hops too big
New service resource allocation failures
SAP messages received from a site that is not a neighbor
SAP messages with unknown service message type
Service message entries with bad network number
Times this device received its own SAP message
0
0
0
0
0
0
0
0
Figure 12-3. IPX SAP Status Screen
The following paragraphs describe IPX SAP Status parameters. Corresponding MIB values,
> or Esc.
12-6
IAN150/IPP MT
6/30/97
SAP table entries [polStatIpxNumSaps]
Indicates the total number of entries in the SAP table.
SAP messages received with no service [polStatIpxSapNoServ]
Indicates the number of SAP messages received with no service entry.
SAP messages entries with intermediate hops too big
[polStatIpxSapBadMetric]
Indicates the number of messages received that have a hop count parameter greater than the
maximum, which is 16 hops.
New service resource allocation failures [polStatIpxSapBadAlloc]
Indicates the number of service entries not retained in the SAP Table because the number of
entries exceeded the dynamic allocation limit as defined by the SAP Table Dynamic Allocation
Limit parameter from (2.4.2.1) IPX Protocol Configuration display.
SAP messages received from a site that is not a neighbor
[polStatIpxSapBadNeighbor]
Indicates the number of SAP messages received from a network that is not directly connected.
SAP messages with unknown service message type
[polStatIpxSapBadCommand]
Indicates the number of SAP messages received from an unknown service type.
Service message entries with bad network number
[polStatIpxSapBadAddr]
Indicates the number of SAP messages received with bad network numbers.
Times this device received its own SAP message [polStatIpxSapOwnAddr]
Indicates the number of self-generated SAP messages received by this IAN-150.
IAN150/IPP MT
6/30/97
12-7
IPX Routing Table
The IPX Routing Table provides information on both static and dynamic IPX routes. To select
the IPX Routing Table screen, from the Main Menu, follow the path:
4. Routing
2. IPX
3. Routing Table
or enter SRXR or 1423 from the command line of any menu or screen and press Enter. The
1.4.2.3 [SRXR] IPX Routing Table
DESTINATION
NETWORK
============
0x00000017
0x00000018
0x00000078
0x00000134
0x00000140
LOCAL
NETWORK
===========
0x00000017
0x00000017
0x00000017
0x00084212
0x00000017
LOCAL
HOST ADDRESS
================
10:00:D0:BC:33:33
10:00:D0:BC:04:80
10:00:D0:BC:E4:80
08:00:0B:3D:01:01
10:00:D0:BC:E4:80
PORT
====
01
01
01
02
01
COST
H/T
TYPE
==== =============
01/01 ATTACHED PORT
03/03
DYNAMIC
02/02
DYNAMIC
02/10
DYNAMIC
03/03
DYNAMIC
Figure 12-4. IPX Routing Table Screen
The following paragraphs describe IPX Routing parameters. Corresponding MIB values, where
applicable, appear in brackets next to the parameter names. To view current values for a specific
destination network, enter the hexadecimal destination network address, then refresh the screen
by typing < . > N (for Read Next) and pressing Enter. The screen displays the statistics that
applied when the command was executed. To exit the screen, press < \ > or Esc.
DESTINATION NETWORK [polStatIpxRtTblNet]
Indicates the hexadecimal destination network address.
LOCAL NETWORK [polStatIpxRtTblGwNet]
Indicates the hexadecimal network address of the gateway used to route to the destination.
LOCAL HOST ADDRESS [polStatIpxRtTblGwHost]
Indicates the hardware or MAC address of the gateway port used to route to the destination.
PORT [polStatIpxRtTblPort]
Indicates the number of the port used to reach the destination.
COST H/T [polStatIpxRtTblCost]
Indicates the cost to reach destination in hops (H) and ticks (T). Hops indicate the number of
routers between source and destination. Ticks indicates how much time (or number of ticks) it
takes for the packet takes to reach the destination. A tick is approximately 1/18 of a second.
TYPE [polStatIpxRtTblType]
Indicates the type of route. The IAN-150 supports five types of IPX routes: Override, Static,
Dynamic, Attached Port, and Default.
12-8
IAN150/IPP MT
6/30/97
IPX Service Advertising Protocol Table
The SAP Table provides route information to IPX servers. To select the IPX SAP Table screen,
4. Routing
2. IPX
4. SAP Table
or enter SRXT or 1424 from the command line of any menu or screen and press Enter. The
1.4.2.4 [SRXT] IPX Service Advertisement Protocol (SAP) Table
SERVER NAME
===========
V311
NETWORK
==========
0x12341234
HOST ADDRESS
SOCKET
================= ========
00:00:00:00:00:01 0x00451
PORT
====
01
COST
====
04
TYPE
=======
0x0278H
0x00000000
00:00:00:00:00:00
0x00000
00
00
0x00000
0x00000000
00:00:00:00:00:00
0x00000
00
00
0x00000
0x00000000
00:00:00:00:00:00
0x00000
00
00
0x00000
Figure 12-5. IPX Service Advertising Protocol Table Screen
The following paragraphs describe IPX Service Advertising Protocol parameters. Corresponding
MIB values, where applicable, appear in brackets next to the parameter names. To view current
values for a specific entry, enter the appropriate information in the SERVER NAME,
NETWORK, HOST ADDRESS, and/or SOCKET key fields, then refresh the screen by typing
< . > N (for Read Next) and pressing Enter. The screen displays the statistics that applied when
SERVER NAME [polStatIpxSapTblName]
Indicates the name of the Novell server.
NETWORK [polStatIpxSapTblNet]
Indicates the network number of the Novell server.
HOST ADDRESS [polStatIpxSapTblNode]
Indicates the MAC address of the Novell server.
SOCKET [polStatIpxSapTblSocket]
Indicates the socket on which the Novell server will receive requests.
PORT [polStatIpxSapTblPort]
Indicates the number of the port used to reach the service.
IAN150/IPP MT
6/30/97
12-9
COST [polStatIpxSapTableCost]
Indicates the number of hops to reach the Novell server.
TYPE [polStatIpxSapTblType]
Indicates the type of Novell server. There are literally hundreds of server types and more are
being offered with each new release of NetWare. For more information, refer to the applicable
NetWare documentation.
12-10
IAN150/IPP MT
6/30/97
Chapter
13
Bisync Monitoring
NOTE:
noted.
BSC (Binary Synchronous Communication) allows the IAN-150 to communicate with IBM
cluster controllers and their IBM Host, using BSC 3270 Protocol. BSC 3270 expands
transmission capabilities with its ability to accommodate a variety of transmission codes.
The IAN-150 provides information to help monitor and troubleshoot Bisync applications. It
offers screens to monitor the status of BSC ports and circuits, the flow state and transmission of
BSC packets, and the status of BSC calls. This chapter describes the following BSC monitoring
screens:
•
Port Status and Control (Screen 1.2.1)
•
Bisync Status (Screen 1.5.1)
•
Circuit Status (Screen 1.5.5)
•
Cleared Circuit Status (Screen 1.5.6)
The screens used for Bisync troubleshootingEIA Modem Lead Status (Screen 1.2.4) and
Hardware Type Display (Screen 1.1.2)are described in Chapter 3 of this manual.
Bisync Monitoring Tips
display or table, the system displays the values in the default template. To view current values,
values for statistical displays, type < . > R and press Enter. To view current values for tables,
type < . > N and press Enter.
IAN150/IPP MT
6/30/97
13-1
Chapter 13, Bisync Monitoring
Bisync Port Status and Control
After you configure BSC ports and activate them using the Cycle command, you can check the
status of the ports from the Port Status and Control screen (Screen 1.2.1.). To select this screen
2. Port
1. Port
or type SPP or 121 from the command line of any menu or screen and press Enter. To check the
status of a specific port, enter the port number in the Port field and press Enter, then refresh the
screen by typing < . > R (for Read) and pressing Enter. The screen displays the port statistics
that applied when the command was executed.
The Port Status and Control screen provides general information on the following topics:
•
Port type, such as Ethernet, Token Ring, or Frame Relay
•
Routing protocols that are active for this port
•
Frame size and throughput data rate for this port
•
MAC and/or IP address of this port
•
Operational status of this port and the date and time when the operational state changed to
the current condition
•
The number of packets transmitted and received over this port, including unicast packets,
multicast packets, discards, errors, packets with unrecognized protocols, and packets queued
for transmission
For more information about the Port Status and Control screen and a complete description of the
displayed parameter values, see Chapter 3 of this manual.
13-2
IAN150/IPP MT
6/30/97
Bisync Status
The Bisync Status screen provides general statistics on port operation. To select this screen from
5. Packet Switching
1. Bisync
or enter SSI or 151 from the command line of any menu or screen and press Enter. The system
1.5.1 [SSI] Bisync Status
Port
001
Logical Circuit
0000
Port Type
Device State
TPAD
INACTIVE
CU Address
Device Address
01
01
Characters
Messages
IN
0
0
OUT
0
0
Figure 13-1. Bisync Status Screen
The following paragraphs describe Bisync Status parameters. Corresponding MIB values, where
Port [polStatWansSmbIntNum]
Identifies the physical port for which you wish Bisync status information.
Logical Circuit [polStatWansSmbLcn]
Identifies the circuit being examined and/or controlled. Valid values: 0 through 999.
Port Type [polStatWansBscPortType]
Indicates the type of port you are monitoring. Available types are:
TPAD Terminal Packet Assembler/Disassembler
HPAD Host Packet Assembler/Disassembler
CU Address [polStatWansBscCuAdr]
Indicates the hexadecimal address of the remote controller unit. Allowed CU Address values are
shown in the following table.
IAN150/IPP MT
6/30/97
13-3
Table 13-1. CU Address Values
CU or Device ASCII CU or
Number
Device Address
EBCDIC CU or
Device Address
CU or Device ASCII CU or
Number
Device Address
EBCDIC CU or
Device Address
0
40
17
4A
D1
20
1
41
C1
18
4B
D2
2
42
C2
19
4C
D3
3
43
C3
20
4D
D4
4
44
C4
21
4E
D5
5
45
C5
22
4F
D6
6
46
C6
23
50
D7
7
47
C7
24
51
D8
8
48
C8
25
52
D9
9
49
C9
26
5D
5A
10
5B
4A
27
24
5B
11
2E
4B
28
2A
5C
12
3C
4C
29
29
5D
13
28
4D
30
3B
5E
14
2B
4E
31
5E
5F
15
21
4F
General Poll
22
7F
16
26
50
Device State [polStatWansBscDState]
Indicates the operational state of the identified device. Bisync device states allowed by the IAN150 are listed below.
INACTIVE
Device is not responding to communication from the IAN-150.
(not polling-HPAD; not responding to poll-TPAD). This is the
default setting.
ACTIVE
Device is active, but not connected (being polled or responding to
poll).
PENDING
Device is trying to connect over network. (Call outstanding)
CONNECTED
Device is connected to another device in the network. It is in full
operation and is communicating. (Fully operational)
SUSPENDED
Device is a dual-session device and the selected device is not active.
Device Address [polStatWansBscDevAdr]
Indicates the address for the remote controller device. This setting is the ASCII-decimal value of
the address. Allowed Device Address values are shown under the CU Address parameter
description.
Characters IN [polStatWansBscChrRcvs]
Characters OUT [polStatWansBscChrTxmts]
Indicates the current number of characters received and transmitted by the Bisync port.
Characters IN indicates the number of characters received; Characters OUT indicate the
number of characters transmitted.
13-4
IAN150/IPP MT
6/30/97
Messages IN [polStatWansBscMsgRcvs]
Messages OUT [polStatWansBscMsgTxmts]
Indicates the current number of messages received and transmitted by the Bisync port. Each
message consists of several frames. Messages IN indicates the number of messages received;
Messages OUT indicates the number of messages transmitted.
Bisync Circuit Status
The Circuit Status screen provides information about the state of a selected circuit and the
characteristics of the data sent across it. To access the Circuit Status screen, from the Main
5. Packet Switching
5. Circuit
or type SSC or 155 at any command line prompt and press Enter. A typical Circuit Status screen
for a call from Port 3 to Port 4 is shown below.
1.5.5 [SSC] Circuit Status
Source Addr
03-000
Dest Addr
00001-004-000
Call State
PVC State
Throughput
Window Size
Estab Time
Clear Time
Called Addr
DATA XFER
READY
9600
0007
06-12-95 22:12:20
06-12-95 22:12:20
3000
Reset State
READY
Packet Size
Timeout (min)
Direction
Duration
Calling Addr
128
NO
IN
0000:00:00
4000
Retransmit PDUs
DTE Resets
DCE Resets
Octets
PDUs
Interrupts
Segments
RNRs
REJs
0
0
0
IN
109,252
109,240
0
0
0
0
Data Timeouts
Interrupt Timeouts
Reset Timeouts
0
0
0
OUT
109,238
109,238
0
0
Figure 13-2. Typical Circuit Status Screen
The following paragraphs describe Circuit Status parameters. Corresponding MIB values, where
circuit, enter the source address of the X.25 circuit you want to monitor, then refresh the screen
by typing < . > R and pressing Enter. The screen displays the statistics that applied when the
command was executed. To exit the screen, press < \ > or Esc.
Source Addr [polStatCircSrcPort] [polStatCircScrLcn]
Identifies the port and circuit number of the circuit you are monitoring.
Dest Addr [polStatCircDstNode] [polStatCircDstPort] [polStatCircDstLcn]
Identifies the node, port, and circuit number of the other end of this call.
IAN150/IPP MT
6/30/97
13-5
Call State [polStatCircP4State]
The status of the call at the time the Read command was executed. If the call has been
established, and no call clearing or restart procedure has been initiated, the Call State will be
DATA XFER (the p4 state). Other potential call states are:
CLOSED
Displayed when the logical channel is unavailable. This state can exist
for a variety of reasons including physical port failure, network-level
protocol failure or network operator-initiated OFFLINE commands. This
state is defined as the p0 state.
READY
Indicates there is no call in existence at the present time. (p1)
DTE WAIT
Indicates the calling DTE has transmitted a Call Request packet across
the DTE/DCE interface. (p2)
DCE WAIT
The DCE has indicated that there is an incoming call by sending an
Incoming Call packet across the DTE/DCE interface. (p3)
COLLISION
Indicates the DTE and DCE have simultaneously transmitted a Call
Request packet and an Incoming Call packet by specifying the same
logical channel. The DCE will proceed with the call request and cancel
the incoming call. (p5)
DTE_CLEAR
Indicates the DTE has transmitted a Clear Request packet across the
DTE/DCE interface. (p6)
DCE_CLEAR
Indicates the DCE has transmitted a Clear Indication packet across the
Reset State [polStatCircR1State]
Indicates the reset state of the virtual call for this circuit after restart packets have been
exchanged. Possible entries in this field are:
READY
Indicates the Flow Control Ready (d1) state. A DTE or DCE Restart
Confirmation packet has been transmitted across the DTE/DCE interface.
The following two states are used to track the events associated with the processing of a Packet
Level Reset that has been generated by equipment attached to the IAN-150.
DTE RESET
Indicates the DTE has requested a restart by transmitting a Reset Request
packet across the DTE/DCE interface. (d2)
DCE RESET
Indicates the DCE has indicated a restart by transmitting a Reset
Indication packet across the DTE/DCE interface. (d3)
The following three states are used to track the events associated with the processing of a Packet
Level Reset that the IAN-150 generated as a result of an error condition.
13-6
WAIT LOCAL
Indicates the Wait Local Confirm (d5) state. A Reset packet has been sent
to the locally attached device; the IAN-150 is waiting for a response.
WAIT
REMOTE
Indicates the Wait Remote Confirm (d6) state. A Reset packet has been
sent to the remote end of the virtual circuit; the IAN-150 is waiting for a
response.
WAIT BOTH
Indicates the Wait Both Confirm (d4) state. Reset packets have been sent
to both the local and remote ends of the virtual circuit. The IAN-150 is
waiting for responses from both ends of the virtual circuit.
IAN150/IPP MT
6/30/97
PVC State [polStatCircPvcState]
This parameter is not valid for this protocol.
Throughput [polStatCircThroughput]
Indicates the data transmission rate in bits per second. Valid values:
75
600
4800
48000
150
1200
9600
64000
300
2400
19200
Packet Size [polStatCircPktSiz]
Describes the packet size that has been established for this call. Valid values:
1
16
256
4096
2
32
512
8192
4
64
1024
16384
8
128
2048
Window Size [polStatCircWindow]
Describes the maximum number of unacknowledged packets established for this call.
Timeout (min) [polStatCircTimeout]
Indicates the maximum amount of time, in minutes, that can pass between ANY two polls on this
circuit. Valid values:
2
20
60
180
5
25
90
210
10
30
120
240
15
45
150
NO
Estab Time [polStatCircEstablishTime]
Indicates the date and time this circuit was established.
Direction [polStatCircDirection]
Describes the direction in which the call was made.
PVC
IN
OUT
Indicates that this circuit is a PVC; therefore no calls can be made.
Call was accepted relative to this source address.
Call was made relative to this source address.
Clear Time [polStatCircClearTime]
Indicates the date and time this circuit was cleared.
Duration [polStatCircCallDuration]
Indicates the length of time, in hours:minutes:seconds, that this call has been established. For an
ongoing call, it indicates the time from the beginning of the call (or from the time when the
circuit statistics were last reset) to the time the Read command was executed. For a completed
call, the duration is the time from the beginning to the end of the call.
Called Address [polStatCircCalledDteAddress]
Indicates the X.121 address of the called DTE, which is contained in the Call Request packet.
IAN150/IPP MT
6/30/97
13-7
Calling Address [polStatCircCallingDteAddress]
Indicates the X.121 address of the calling DTE, which is contained in the Call Request packet.
Retransmit PDUs [polStatCircRetransmitPackets]
Indicates the number of packets that needed to be retransmitted due to any reason.
Data Timeouts [polStatCircRetranTimeouts]
Internal timer that counts the number of data, interrupt, and reset packets that are retransmitted
between two IAN-150’s when two IAN-150’s are communicating.
DTE Resets [polStatCircDteResets]
Indicates the number of times the DTE sends out a Reset Request packet.
Interrupt Timeouts [polStatCircInterruptTimeouts]
Internal timer that counts the number of interrupt packets that are retransmitted between two
IAN-150’s when two IAN-150’s are communicating.
DCE Resets [polStatCircDceResets]
Indicates the number of times a DCE sends out a Reset Request packet.
Reset Timeouts [polStatCircResetTimeouts]
Internal timer that counts the number of reset packets that are retransmitted between two IAN150’s when two IAN-150’s are communicating.
Octets [polStatCircInOctets] {polStatCircOutOctets]
Indicates the number of octets transmitted (Octets OUT) or received (Octets In) over this
circuit.
PDUs [polStatCircInPdus] [polStatCircOutPdus]
Indicates the total number of packets transmitted (PDUs OUT) or received (PDUs IN) over this
circuit.
Interrupts [polStatCircInInterrupts] [polStatCircOutInterrupts]
Indicates the number of Interrupt packets transmitted (Interrupts OUT) or received (Interrupts
IN) over this circuit.
Segments [polStatCircInSegments] [polStatCircOutSegments]
Indicates the number of segments transmitted (Segments IN) or received (Segments OUT) over
this circuit.
RNRs [polStatCircInRNRs]
Indicates the number of Receive Not Ready packets received (RNRs IN) over this circuit.
REJs [polStatCircInREJs]
Indicates the number of Reject packets received (REJs IN) over this circuit.
13-8
IAN150/IPP MT
6/30/97
Bisync Cleared Circuit Status
The Cleared Circuit Status screen provides information and statistics for the Switched Virtual
Circuits (SVCs) that have been cleared. The IAN-150 can save up to 16 cleared circuit records in
the Cleared Circuit Status table; the actual number of entries that will be included in the table is
defined in the Circuit Count parameter from the X25 Port Configuration screen ( 2.5.7.1). To
access the Cleared Circuit Status screen, from the Main Menu, follow the path:
5. Packet Switching
6. Cleared Circuits
or type SSL or 156 from the command line of any screen and press Enter. The system displays
the following screen:
1.5.6 [SSL] Cleared Circuit Status
Index
000
Newest Index
000
Source Addr
Called Addr
00-000
Dest Addr
Calling Addr
00000-000-000
Estab Time
Cause Code
PDUs In
05-24-96 11:32:30
000
0
Clear Time
Diagnostic
PDUs Out
05-24-96 11:32:30
000
0
Facilities
Figure 13-3. Cleared Circuit Status Screen
The following paragraphs describe Cleared Circuit Status parameters. Corresponding MIB
for a specific circuit, enter the index number for the circuit you want to monitor, then refresh the
screen by typing < . > N (for Read Next) and pressing Enter. The screen displays the statistics
that applied when the command was executed. To exit the screen, press < \ > or Esc.
Index [polStatClearedCircuitIndex]
Identifies the cleared circuit for which you want status information.
Newest Index [polStatClearedCircuitMostRecentIndex]
Identifies the index number for the last cleared circuit that was entered into the Cleared Circuit
Status table.
Each cleared circuit is given an index number and is stored in a database. When you execute the
first Read Next command, the most recent cleared circuit status is displayed. This will have the
highest index number of all the index numbers that are stored in the database. Each time you
execute another Read Next command, the next most recent cleared circuit status is displayed in
sequential order. The Newest Index remains the same, but the Index field decreases by one.
Source Addr [polStatClearedCircuitPleIndex]
[polStatClearedCircuitChannel]
Identifies the port and circuit number of the entity that initiated the connection.
IAN150/IPP MT
6/30/97
13-9
Dest Addr [polStatClearedCircuitDstNode] [polStatClearedCircuitDstPort]
[polStatClearedCircuitDstLcn]
Identifies the node, port and circuit number of the other end of the connection.
Called Addr [polStatClearedCircuitCalledAddress]
For incoming calls, this is the X.121 called address from the Call Indication packet. For outgoing
calls, it is the X.121 called address from the Call Request packet. For PVCs, this parameter will
be zero.
Calling Addr [polStatClearedCircuitCallingAddress]
For incoming calls, this is the X.121 calling address from the Call Indication packet. For
outgoing calls, it is the X.121 calling address from the Call Request packet. For PVCs, this
parameter will be zero.
Estab Time [polStatClearedCircuitTimeEstablished]
Indicates the date and time that this circuit was established. A circuit is established when a Call
Confirmation packet has been received by the source address.
Clear Time [polStatClearedCircuitTimeCleared]
Indicates the date and time that this circuit was cleared. A circuit is cleared when the device
handler gets out of phase or loses contact with the attached device, or when a Clear Request or
Clear Indication packet is processed by the circuit.
Cause Code [polStatClearedCircuitClearingCause]
Identifies numerically the reason that the circuit was cleared. The following table gives the
possible circuit-clearing causes and their numeric codes.
Table 13-2. Circuit Clearing Causes
Cause
13-10
Description
Integer Value
ACCESS BARRED
Call not accepted.
11
DTE ORIGIN
Call cleared by DTE.
FAST SELECT
Fast select acceptance not subscribed.
41
INCOMPATIBLE
Call placed on incompatible DTE.
33
INVALID FACILITY
Facility not used or accepted, or incorrectly coded.
LOCAL PROCEDURE ERROR
Terminal in incorrect state.
0
3
19
NETWORK CONGESTED
Communication delay is too large.
NO REVERSE CHARGING
Destination does not accept reverse charging.
25
5
NOT OBTAINABLE
Node being called is offline.
13
NUMBER BUSY
Number is in use.
1
OUT OF ORDER
Destination port is offline, or checksumming
corrupted data block.
9
OUTGOING CALLS BARRED
Terminal not permitted to make outgoing calls.
3
REMOTE PROCEDURE
ERROR
State error, or destination port does not exist, or
suspended camped call cleared by user.
17
RPOA
RPOA out of order.
21
SHIP ABSENT
For ship at sea.
57
CLEAR, CAUSE UNKNOWN
Call cleared but reason unknown.
DTE ORIGINATED (PRIVATE)
DTE reports private clear code.
143 - 255
IAN150/IPP MT
6/30/97
Diagnostic [polStatClearedCircuitDiagnosticCode]
Provides additional information on what caused the circuit to be cleared. The Bisync diagnostic
codes supported by the IAN-150 are listed in the following table:
Table 13-3. IAN-150 Bisync Diagnostic Codes
Code
Description
Code
Description
238
ASCII/EBCDIC ss code $2041/$40c1
247
H/T PAD did not acknowledge command
239
ASCII/EBCDIC ss code $2026/$4050
248
BSC station timeout
240
ASCII/EBCDIC ss code $202d/$4060
249
Excessive data from BSC stations
241
ASCII/EBCDIC ss code $482d/$4840
250
Call cleared
242
ASCII/EBCDIC ss code $4841/$c8c1
251
BSC station down
243
ASCII/EBCDIC ss code $204a/$40d1
252
BSC transmission halted
244
ASCII/EBCDIC ss code $4441/$c4c1
254
Insufficient memory available to establish
call
245
255
Protocol mismatch
246
PDUs In [polStatClearedCircuitInPdus]
Displays the number of Protocol Data Units that were received while the circuit was in operation.
PDUs Out [polStatClearedCircuitOutPdus]
Displays the number of Protocol Data Units that were sent while the circuit was in operation.
Facilities [polStatClearedCircuitFacilities]
Indicates which of the X.25 facilities listed below were invoked while the circuit was in
operation:
WIN
PAC
THR
REV
NUI
IAN150/IPP MT
6/30/97
Window Size
Packet Size
Throughput
Reverse Charging
Network User Identification
13-11
Chapter
14
BPS Monitoring
NOTE:
noted.
The IAN-150 provides information to help monitor and troubleshoot Burroughs Poll Select
(BPS) applications. It provides displays to monitor the status of BPS ports and circuits, the flow
state and transmission of BPS packets, and the status of BPS calls. This chapter describes the
following BPS monitoring screen:
•
•
Burroughs Poll Select Status (Screen 1.5.2)
•
Circuit Status (screen 1.5.5)
•
Cleared Circuit Status (1.5.6)
The screens used for BPS troubleshootingEIA Modem Lead Status (Screen 1.2.4) and
BPS Monitoring Tips
IAN150/IPP MT
6/30/97
14-1
Chapter 14, BPS Monitoring
BPS Port Status and Control
After you configure BPS ports and activate them using the Cycle command, you can check the
status of the ports from the Port Status and Control screen (Screen 1.2.1). To select this screen
2. Port
1. Port
•
•
•
•
•
•
Port type, such as Ethernet, Token Ring, or Frame Relay.
Routing protocols that are active for this port.
Frame size and throughput data rate for this port.
MAC and/or IP address of this port.
the current condition.
for transmission.
displayed parameter values, see Chapter 3 of this manual.
14-2
IAN150/IPP MT
6/30/97
BPS Status
The Burroughs Poll Select Status screen provides general statistics on BPS port operation. To
select the Burroughs Poll Select Status screen from the Main Menu, follow the path:
5. Packet Switching
2. Burroughs
or enter SSU or 152 from the command line of any menu or screen and press Enter. The system
1.5.2 [SSU] Burroughs Poll Select Status
Port
001
Logical Circuit
0000
Port Type
TPAD
Device State
INACTIVE
Address 1
Address 2
01
01
Group Address 1
Group Address 2
01
01
Characters
Messages
IN
0
0
OUT
0
0
Figure 14-1. Burroughs Poll Select Status Screen
The following paragraphs describe Burroughs Poll Select Status parameters. Corresponding MIB
Port [polStatWansSmbIntNum]
Identifies the physical port for which you wish BPS status information.
Logical Circuit [polStatWansSmbLcn]
Identifies the circuit being examined and/or controlled. Valid values: 0 through 999.
Port Type [polStatWansBpsPortType ]
Indicates the type of port you are monitoring. Available types:
TPAD Terminal Packet Assembler/Disassembler
HPAD Host Packet Assembler/Disassembler
IAN150/IPP MT
6/30/97
14-3
Device State [polStatWansBpsDState ]
Indicates the state of the identified device. BPS device states allowed by the IAN-150 are listed
below.
INACTIVE
Device is not polling-HPAD and/or not responding to poll-TPAD.
This is the default setting.
ACTIVE
Device is active, but not connected, meaning that it is not being
polled or responding to poll.
PENDING
Call outstanding, trying to connect over network.
CONNECTED
Device is connected to another device at other end of network. It is
in full operation and is communicating.
SUSPENDED
Device is a dual session device and indicates the selected device is
not active.
Address 1 [polStatWansBpsDevAdr1]
Identifies, for a BPS multidrop circuit, the ASCII-Decimal address of the first device at the
TPAD that is connected by the circuit.
Group Address 1 [polStatWansBpsGrpAdr1]
Identifies group address one for the specified BPS circuit. Valid values: 0 to 255.
Address 2 [polStatWansBpsDevAdr2]
Identifies, for a BPS multidrop circuit, the ASCII-Decimal address of the second device at the
TPAD that is connected by the circuit.
Group Address 2 [polStatWansBpsGrpAdr2]
Identifies group address two for the specified BPS circuit. Valid values: 0 to 255.
Characters In [polStatWansBpsChrRcvs]
Characters Out [polStatWansBpsChrTxmts]
Indicates the current number of characters received and transmitted by the BPS port. Characters
IN indicates the number of characters received; Characters OUT indicate the number of
characters transmitted.
Messages In [polStatWansBpsMsgRcvs]
Messages Out [polStatWansBpsMsgTxmts]
Indicates the current number of messages received and transmitted by the BPS port. Each
message consists of several frames. Messages IN indicates the number of messages received;
Messages OUT indicates the number of messages transmitted.
14-4
IAN150/IPP MT
6/30/97
BPS Circuit Status
The BPS Circuit Status screen provides information about the state of a selected circuit and the
characteristics of the data sent across it. To access the BPS Circuit Status screen from the Main
5. Packet Switching
5. Circuit
or type SSC or 155 at any command line prompt and press Enter. A typical Circuit Status screen
for a call from Port 4 to Port 2 is shown below.
Source Addr
03-000
Dest Addr
00001-004-000
Call State
PVC State
Throughput
Window Size
Estab Time
Clear Time
Called Addr
DATA XFER
READY
9600
0007
06-12-95 22:12:20
06-12-95 22:12:20
3000
Reset State
READY
Packet Size
Timeout (min)
Direction
Duration
Calling Addr
128
NO
IN
0000:00:00
4000
Retransmit PDUs
DTE Resets
DCE Resets
Octets
PDUs
Interrupts
Segments
RNRs
REJs
0
0
0
IN
109,252
109,240
0
0
0
0
Data Timeouts
Interrupt Timeouts
Reset Timeouts
0
0
0
OUT
109,238
109,238
0
0
Figure 14-2. Typical Circuit Status screen
IAN150/IPP MT
6/30/97
14-5
Indicates the status of the call at the time the Read command was executed. If the call has been
CLOSED
READY
There is no call in existence at the present time. (p1)
DTE WAIT
The calling DTE has transmitted a Call Request packet across the
DCE WAIT
COLLISION
The DTE and DCE have simultaneously transmitted a Call Request
packet and an Incoming Call packet by specifying the same logical
channel. The DCE will proceed with the call request and cancel the
incoming call. (p5)
DTE_CLEAR
The DTE has transmitted a Clear Request packet across the DTE/DCE
interface. (p6)
DCE_CLEAR
The DCE has transmitted a Clear Indication packet across the DTE/DCE
interface. (p7)
READY
The Flow Control Ready (d1) state. A DTE or DCE Restart Confirmation
packet has been transmitted across the DTE/DCE interface.
14-6
DTE RESET
The DTE has requested a restart by transmitting a Reset Request packet
across the DTE/DCE interface. (d2)
DCE RESET
The DCE has indicated a restart by transmitting a Reset Indication packet
IAN150/IPP MT
6/30/97
WAIT LOCAL
The Wait Local Confirm (d5) state. A Reset packet has been sent to the
locally attached device; the IAN-150 is waiting for a response.
WAIT
REMOTE
The Wait Remote Confirm (d6) state. A Reset packet has been sent to the
remote end of the virtual circuit; the IAN-150 is waiting for a response.
WAIT BOTH
The Wait Both Confirm (d4) state. Reset packets have been sent to both
the local and remote ends of the virtual circuit. The IAN-150 is waiting
for responses from both ends of the virtual circuit.
75
600
4800
48000
150
1200
9600
64000
300
2400
19200
Describes the packet size that has been established for this call. Valid values:
1
16
256
4096
2
32
512
8192
4
64
1024
16384
8
128
2048
IAN150/IPP MT
6/30/97
2
20
60
180
5
25
90
210
10
30
120
240
15
45
150
NO
14-7
PVC
Indicates that this circuit is a PVC; therefore no calls can be made.
IN
Call was accepted relative to this source address.
OUT
Call was made relative to this source address.
Number of packets that needed to be retransmitted due to any reason.
Internal timer that counts the number of data, interrupt, and reset packets that are retransmitted
between two IAN-150’s when two IAN-150’s are communicating.
Number of times the DTE sends out a Reset Request packet.
Internal timer that counts the number of interrupt packets that are retransmitted between two
IAN-150’s when two IAN-150’s are communicating.
Number of times a DCE sends out a Reset Request packet.
Internal timer that counts the number of reset packets that are retransmitted between two IAN150’s when two IAN-150’s are communicating.
Octets [polStatCircInOctets] [polStatCircOutOctets]
circuit.
14-8
IAN150/IPP MT
6/30/97
circuit.
this circuit.
Indicates the number of Receive Not Ready packets received (RNRs IN) over this circuit.
BPS Cleared Circuit Status
The Cleared Circuit Status provides information and statistics for the Switched Virtual Circuits
(SVCs) that have been cleared. The IAN-150 can save up to 16 cleared circuit records in the
Cleared Circuit Status table; the actual number of entries that will be included in the table is
defined in the Circuit Count parameter from the X25 Port Configuration Screen (Screen 2.5.7.1).
To access the Cleared Circuit Status screen, from the Main Menu, follow the path:
5. Packet Switching
6. Cleared Circuits
Index
000
Newest Index
000
Source Addr
Called Addr
00-000
Dest Addr
Calling Addr
00000-000-000
Estab Time
Cause Code
PDUs In
05-24-96 11:32:30
000
0
Clear Time
Diagnostic
PDUs Out
05-24-96 11:32:30
000
0
Facilities
Figure 14-3. Clear Circuit Status Screen
IAN150/IPP MT
6/30/97
14-9
The following paragraphs describe Cleared Circuit Status parameters. Corresponding MIB
values, where applicable, appear in brackets next to the parameter names. To see current values
screen by typing < . > N and pressing Enter. The screen displays the statistics that applied when
Status table.
be zero.
Indicates the date and time that this circuit was established. A circuit is established when a Call
Identifies numerically the reason that the circuit was cleared. Table 14-1 gives the possible
circuit-clearing causes and their numeric codes.
14-10
IAN150/IPP MT
6/30/97
Cause
Description
Integer Value
ACCESS BARRED
Call not accepted.
11
DTE ORIGIN
FAST SELECT
41
INCOMPATIBLE
33
INVALID FACILITY
0
3
19
NETWORK CONGESTED
NO REVERSE CHARGING
25
5
NOT OBTAINABLE
13
NUMBER BUSY
Number is in use.
1
OUT OF ORDER
9
REMOTE PROCEDURE
ERROR
17
3
RPOA
RPOA out of order.
21
SHIP ABSENT
For ship at sea.
57
143 - 255
Provides additional information on what caused the circuit to be cleared. For a list of valid
diagnostic codes and their meanings, see Table 14-2 below.
operation:
WIN
PAC
THR
REV
NUI
IAN150/IPP MT
6/30/97
Window Size
Packet Size
Throughput
Reverse Charging
14-11
Table 14-2. IAN-150 Diagnostic Codes
14-12
Code
Description
Code
Description
0
No additional information
76
Facility not provided when expected
1
Invalid P(S)
77
Invalid ITU-T-specified DTE facility
2
Invalid P(R)
78
Max number of redirections exceeded
16
Packet type invalid
84
Bad NUI facility
17
For state r1
129
Console called from external node
18
For state r2
132
Virtual circuit interrupted by NMS
19
For state r3
135
Pkt size exceeded storage capacity of
concatenation buffer
20
For state p1
136
Expect XID response from remote PAD
21
For state p2
138
Permanent virtual circuit failed
22
For state p3
139
Remote DTE logged off network
23
For state p4
140
Remote DTE cleared the call
24
For state p5
141
Remote DTE received an inv to clear
25
For state p6
144
Camp-on timed out and cleared call
26
For state p7
147
Station is offline
27
For state d1
149
A QDM or QDC packet was to be sent
28
For state d2
150
NMS offline est
29
For state D3
155
Invalid destination password
32
Packet not allowed
156
Invalid dest. Net/Group/User code
33
Unidentifiable packet
157
Invalid checksum/encrypt/compress code
34
Call on one-way logical channel
158
Port handler placed in restart state
35
Invalid packet type on a PVC
159
Transmission failure to physical port
36
Packet on unassigned logical channel
166
Reselect received
37
Reject not subscribed to
171
NMS issued exit command
38
Packet too short
180
Port handler in shutdown state
39
Packet too long
193
BPS station down
40
Invalid general format identifier
200
Port handler in disconnect state
41
Restart or registration packet contains
illegal non-zero bits
201
DSR/DTR not active
42
Packet type not compatible with facility
204
COP handler received illegal X.25 packet
in the online state
43
Unauthorized interrupt confirmation
205
COP receive error
44
Unauthorized interrupt
206
COP handler placed in restart state
45
Unauthorized reject
207
Sensed modem leads dropped
48
Time expired
211
T10 timeout
49
For incoming call
212
Restart expected on LCN 0
50
For clear indication
213
Invalid source calling address
51
For reset indication
214
Invalid destination calling address
52
For restart indication
215
Invalid X.25 data packet received in the
link opening state
53
For call deflection
216
Invalid state in QLLC Hpad
65
Facility/registration code not allowed
217
Invalid state in SDLC Hpad
66
Facility parameter not allowed
218
Invalid state in QLLC Tpad
IAN150/IPP MT
6/30/97
Table 14-2. IAN-150 Diagnostic Codes (Cont’d)
67
Invalid called DTE address
219
68
Invalid calling DTE address
220
Timeout count exceeded for either call
requests or SNRMs
69
Invalid facility/registration length
221
Indicates the Clear Request was
originated from QLLC
70
Incoming call barred
222
originated from SDLC
71
No logical channel available
223
Clear was caused by a Reset command
72
Call collision
224
Clear was generated because Call
Request was not acknowledged
73
Duplicate facility requested
225
QLLC received a Level 3 Inop command
74
Non-zero address length
226
QLLC timeout value expired before TO
75
Non-zero facility length
IAN150/IPP MT
6/30/97
14-13
Chapter
15
SDLC Packet Switch Monitoring
NOTE:
noted.
The IAN-150 provides information to help monitor and troubleshoot Synchronous Data Link
Control (SDLC) applications. It provides displays to monitor the status of SDLC ports and
circuits, flow state and transmission of SDLC packets, and status of SDLC calls. This chapter
describes the following SDLC monitoring screens:
•
•
SDLC Status (Screen 1.5.3)
•
Circuit Status (Screen 1.5.5)
•
Cleared Circuit Status (Screen 1.5.6)
The screens used for SDLC troubleshootingEIA Modem Lead Display (Screen 1.2.4) and
SDLC Monitoring Tips
The IAN-150 uses templates for each of its statistical displays and tables; when you first access a
display or table, the values in the default template appear. To view current values, refresh the
and press Enter.
Each table can be sorted by key fields, which are located in the first line of every table. To
display information about a specific table entry, refresh the screen, enter the appropriate
IAN150/IPP MT
6/30/97
15-1
Chapter 15, SDLC Monitoring
SDLC Port Status and Control
After you configure SDLC ports and activate them using the Cycle command, you can check the
status of the ports from the Port Status and Control screen (Screen 1.2.1). To select this screen
2. Port
1. Port
•
Port type, such as Ethernet, Token Ring, or Frame Relay
•
Routing protocols that are active for this port
•
Frame size and throughput data rate for this port
•
MAC (Medium Access Control) address of this port
•
the current condition
•
for transmission
displayed parameter values, see Chapter 3 in this manual.
15-2
IAN150/IPP MT
6/30/97
SDLC Station Status
SDLC Station Status screen displays status information about SDLC data transmission. To select
the SDLC Station Status screen from the Main Menu, follow the path:
5. Packet Switching
3. SDLC
or type SSS at any command line prompt and press Enter. The system displays the SDLC
Station Status screen:
1.5.3 [SSS] SDLC Station Status
Port
SDLC State
QLLC State
FRMR Cause In
FRMR Cause Out
XID In
Frames discarded
004
CONNECT
INOPERATIVE
NONE
NONE
00000000
0
Logical Circuit
SDLC SubState
QLLC SubState
Contents
Contents
XID Out
Poll Retries
IN
0
0
0
0
0
0
0
0
0
0
Info Frames
Info Bytes
SNRMs
DISC/RDs
DMs
FRMRs
RNRs
REJs
XIDs
TESTs
0000
TEST PENDING
CALLS ALLOWED
00000000
00000000
00000000
0
OUT
0
0
0
0
0
0
0
0
0
0
Figure 15-1. SDLC Station Status Screen
The following paragraphs describe SDLC Station Status parameters. Corresponding MIB values,
> or Esc.
Port [polStatWansSdlcIntNum]
Logical Circuit [polStatWansSdlcLcn]
Identifies the circuit being examined and/or controlled.
SDLC State [polStatWansSdlcSdState]
Indicates the state of the identified QLLC station. Possible states are:
IAN150/IPP MT
6/30/97
INOPERATIVE
Station is offline.
DISCONNECT
Station is online but has not received mode-setting command.
CONNECT
Station is in normal response mode.
15-3
When a station is brought online, the Station State changes from INOPERATIVE to
DISCONNECT. After a virtual circuit is connected and the QLLC mode-setting is completed, the
Station State goes to CONNECT and data transfer can begin.
When a station in the CONNECT state is placed offline, the virtual circuit is cleared and the
Station State goes to INOPERATIVE.
SDLC Substate [polStatWansSdlcSdSub]
Indicates the current SDLC substate for this station. Possible SDLC substates are: NO
SUBSTATE, XID PENDING, TEST PENDING, DISC PENDING, SNRM PENDING,
POLL NO FLOW, POLL PHYS FLOW, POLL NET FLOW, POLL BOTH FLOW, IDLE
NO FLOW, IDLE PHYS FLOW, IDLE BOTH FLOW, SIM PENDING, QXID PENDING,
QTEST PENDING, DISC PENDING, UA PENDING, TEST/XID PENDG, HOST DATA
FLOW, NTWK DATA FLOW, HOST/NTWK FLOW, and FRMR MODE.
QLLC State [polStatWansSdlcQlState ]
Indicates the QLLC state of the station. Possible QLLC states are listed below.
INOPERATIVE
Waiting virtual circuit connection.
CLOSED
Virtual circuit established; waiting for link ready.
OPENING
Virtual circuit established and link ready; waiting for mode-setting
command.
OPEN
In normal response mode and able to transfer data.
CLOSING
Virtual circuit being disconnected.
RECOVER
Station waiting clearing of virtual circuit. This state is not used at host
end of circuit.
For TPAD stations, the QLLC state goes from INOPERATIVE to OPENING once a virtual
circuit is connected. When a mode-setting QLLC command arrives, the QLLC state goes to
OPEN.
For HPAD stations, the QLLC state goes to CLOSED once a virtual circuit is connected. After a
mode-setting command is received from the host, converted, and sent to the remote end of the
call, the QLLC state becomes OPENING. When a positive QLLC response arrives and is
converted and returned to the host, the QLLC state becomes OPEN.
QLLC Substate [polStatWansSdlcQlSub]
Indicates the current QLLC substate for this station. Possible QLLC substates are:
NO SUBSTATE, CALLS ALLOWED, OUTGOING XID PEND, OUTGOING TEST
PEND, CONTACT TERM PEND, WAITING TO GO UP, WAITING TO GO DOWN,
ELSE, ELSE HOST FLOW CNTL, INCOMING TEST PEND, ITRP HOST FLOW
CNTL, INCOMING XID PEND, IXRP HOST FLOW CNTL, HOST FLOW CONTROL,
and QFRMR MODE.
15-4
IAN150/IPP MT
6/30/97
FRMR Cause In [polStatWansSdlcFrmrInCause]
The cause (control field) of the last Frame Rejected (FRMR) packet received by the station.
Valid values:
NONE
UNDEFINED
LENGTH ERROR
MTU EXCEEDED
INVALID NR
number.
Contents [polStatWansSdlcFrmrInData]
Displays the four bytes of the control field of the last FRMR packet received by the station.
FRMR Cause Out [polStatWansSdlcFrmrOutCause]
Indicates the cause (control field) of the last Frame Rejected (FRMR) packet sent by the station.
Valid values:
NONE
UNDEFINED
Indicates there was a problem with the transmitted packet not
LENGTH ERROR
Indicates the size of the packet exceeded acceptable values
MTU EXCEEDED
Indicates the data unit size has exceeded acceptable values.
INVALID NR
Indicates there was an invalid transmitter receive sequence number.
Contents [polStatWansSdlcFrmrOutData]
Displays the four bytes of the control field of the last FRMR packet sent by the station.
XID In [polStatWansSdlcXidInData]
Displays the first four bytes of the I-field (Information field) of the last XID (exchange
Identification) received by the station.
XID Out [polStatWansSdlcXidOutData]
Displays the first four bytes of the I-field of the last XID sent by the station.
Frames Discarded [polStatWansSdlcFrmDiscs]
Indicates the number of frames received and discarded by the station.
Poll Retries [polStatWansSdlcRetries]
Displays the accumulated count of retried polls by the TPAD on this station.
Info Frames [polStatWansSdlcFrmIns] [polStatWansSdlcFrmOuts]
Indicates the number of Information (I) frames received (Info Frames IN) and transmitted (Info
Frames OUT).
IAN150/IPP MT
6/30/97
15-5
Info Bytes [polStatWansSdlcByteIns] [polStatWansSdlcByteOuts]
Indicates the number of information bytes received (Info Bytes IN) and transmitted (Info Bytes
OUT).
SNRMs [polStatWansSdlcSnrmIns] [polStatWansSdlcSnrmOuts]
Indicates the number of Set Normal Response Mode (SNRM) frames received (SNRMs IN) and
transmitted (SNRMs OUT).
DISC/RDs [polStatWansSdlcDiscIns] [polStatWansSdlcDiscOuts]
Indicates the number of Disconnect/Request Disconnect (DISC/RD) frames received (DISC/RDs
IN) and transmitted (DISC/RDs OUT).
DMs [polStatWansSdlcDmIns] [polStatWansSdlcDmOuts]
Indicates the number of Disconnect Mode (DM) frames received (DMs IN) and transmitted
(DMs OUT).
FRMRs [polStatWansSdlcFrmrIns] [polStatWansSdlcFrmrOuts]
Indicates the number of Frame Rejected (FRMR) frames received (FRMRs IN) and transmitted
(FRMRs OUT).
RNRs [polStatWansSdlcRnrIns] [polStatWansSdlcRnrOuts]
Indicates the number of Receiver Not Ready (RNR) frames received (RNRs IN) and transmitted
(RNRs OUT).
REJs [polStatWansSdlcRejIns] [polStatWansSdlcRejOuts]
Indicates the number of Rejected (REJ) frames received (REJs IN) and transmitted (REJs
OUT).
RRs [polStatWansSdlcRrIns] [polStatWansSdlcRrOuts]
Indicates the number of Ready to Receive (RR) frames received (RRs IN) and transmitted (RRs
OUT).
XIDs [polStatWansSdlcXidIns] [polStatWansSdlcXidOuts]
Indicates the number of XID frames received (XIDs IN) and transmitted (XIDs OUT).
TESTs [polStatWansSdlcTestIns] [polStatWansSdlcTestouts]
Indicates the number of Test frames received (TESTs IN) and transmitted (TESTs OUT).
15-6
IAN150/IPP MT
6/30/97
SDLC Circuit Status
The SDLC Circuit Status screen provides information about the state of a selected circuit and the
characteristics of the data sent across it. To access the SDLC Circuit Status screen from the Main
5. Packet Switching
5. Circuit
or type SSC or 155 at any command line prompt and press Enter. A typical SDLC Circuit Status
screen for a call from Port 3 to Port 4 is shown below:
Source Addr
03-000
Dest Addr
00001-004-000
Call State
PVC State
Throughput
Window Size
Estab Time
Clear Time
Called Addr
DATA XFER
READY
9600
0007
06-12-95 22:12:20
06-12-95 22:12:20
3000
Reset State
READY
Packet Size
Timeout (min)
Direction
Duration
Calling Addr
128
NO
IN
0000:00:00
4000
Retransmit PDUs
DTE Resets
DCE Resets
Octets
PDUs
Interrupts
Segments
RNRs
REJs
0
0
0
IN
109,252
109,240
0
0
0
0
Data Timeouts
Interrupt Timeouts
Reset Timeouts
0
0
0
OUT
109,238
109,238
0
0
Figure 15-2. Typical SDLC Circuit Status Screen
Displays the status of the call at the time the Read command was executed. If the call has been
IAN150/IPP MT
6/30/97
15-7
CLOSED
READY
There is no call in existence at the present time. (p1)
DTE WAIT
The calling DTE has transmitted a Call Request packet across the
DCE WAIT
COLLISION
The DTE and DCE have simultaneously transmitted a Call Request
packet and an Incoming Call packet by specifying the same logical
channel. The DCE will proceed with the call request and cancel the
incoming call. (p5)
DTE_CLEAR
The DTE has transmitted a Clear Request packet across the DTE/DCE
interface. (p6)
DCE_CLEAR
The DCE has transmitted a Clear Indication packet across the DTE/DCE
interface. (p7)
READY
The Flow Control Ready (d1) state. A DTE or DCE Restart Confirmation
packet has been transmitted across the DTE/DCE interface.
DTE RESET
The DTE has requested a restart by transmitting a Reset Request packet
DCE RESET
The DCE has indicated a restart by transmitting a Reset Indication packet
15-8
WAIT LOCAL
The Wait Local Confirm (d5) state. A Reset packet has been sent to the
locally attached device; the IAN-150 is waiting for a response.
WAIT
REMOTE
The Wait Remote Confirm (d6) state. A Reset packet has been sent to the
remote end of the virtual circuit; the IAN-150 is waiting for a response.
WAIT BOTH
The Wait Both Confirm (d4) state. Reset packets have been sent to both
the local and remote ends of the virtual circuit. The IAN-150 is waiting
for responses from both ends of the virtual circuit.
IAN150/IPP MT
6/30/97
75
600
4800
48000
150
1200
9600
64000
300
2400
19200
Describes the packet size, in bytes, established for this call. Valid values:
1
16
256
4096
2
32
512
8192
4
64
1024
16384
8
128
2048
2
20
60
180
5
25
90
210
10
30
120
240
15
45
150
NO
IAN150/IPP MT
6/30/97
PVC
Indicates this is a PVC (Permanent Virtual Circuit); therefore no calls can be
made.
IN
Indicates this source address accepted a call.
OUT
Indicates this source address initiated a call.
15-9
Indicates the number of packets that needed to be retransmitted due to any reason.
Internal timer that counts the number of data, interrupt, and reset packets retransmitted between
two IAN-150s when two IAN-150’s are communicating.
Indicates the number of times the DTE sends out a Reset Request packet.
Internal timer that counts the number of interrupt packets retransmitted between two IAN-150s
when two IAN-150’s are communicating.
Indicates the number of times a DCE sends out a Reset Request packet.
Internal timer that counts the number of reset packets retransmitted between two IAN-150s when
two IAN-150’s are communicating.
Octets [polStatCircInOctets] {polStatCircOutOctets]
circuit.
circuit.
this circuit.
15-10
IAN150/IPP MT
6/30/97
Indicates the number of Receiver Not Ready packets received (RNRs IN) over this circuit.
SDLC Cleared Circuit Status
SDLC Cleared Circuit Status provides information and statistics for the Switched Virtual
Circuits (SVCs) that have been cleared. The IAN-150 can save up to 16 cleared circuit records in
the Cleared Circuit Status table, as configured in the Cleared Circuit Table in the Node Parameter
Configuration screen (2.1.1). To access the Cleared Circuit Status screen from the Main Menu,
follow the path:
5. Packet Switching
6. Cleared Circuits
Index
000
Newest Index
000
Source Addr
Called Addr
00-000
Dest Addr
Calling Addr
00000-000-000
Estab Time
Cause Code
PDUs In
05-24-96 11:32:30
000
0
Clear Time
Diagnostic
PDUs Out
05-24-96 11:32:30
000
0
Facilities
Figure 15-3. Cleared Circuit Status Screen
The Cleared Circuit Status parameters are described in the following paragraphs. Corresponding
MIB values, where applicable, appear in brackets next to the parameter names. To view current
values for a specific circuit, enter the index number for the circuit you want to monitor, then
refresh the screen by typing < . > N and pressing Enter. The screen displays the statistics that
IAN150/IPP MT
6/30/97
15-11
Status table.
Indicates the port and circuit number of the entity that initiated the connection.
Indicates the node, port, and circuit number of the other end of the connection.
be zero.
Indicates the date and time this circuit was established. A circuit is established when a Call
Identifies numerically the reason that the circuit was cleared. Table 15-1 lists the possible circuitclearing causes and their numeric codes.
15-12
IAN150/IPP MT
6/30/97
Cause
Description
Integer Value
ACCESS BARRED
Call not accepted.
11
DTE ORIGIN
FAST SELECT
41
INCOMPATIBLE
33
INVALID FACILITY
0
3
19
NETWORK CONGESTED
NO REVERSE CHARGING
25
5
NOT OBTAINABLE
13
NUMBER BUSY
Number is in use.
1
OUT OF ORDER
9
REMOTE PROCEDURE
ERROR
17
3
RPOA
RPOA out of order.
21
SHIP ABSENT
For ship at sea.
57
143 - 255
Provides additional information on what caused the circuit to be cleared. For a list of valid
diagnostic codes and their descriptions, see Table 15-2 below.
Displays the number of Protocol Data Units received while the circuit was in operation.
Displays the number of Protocol Data Units sent while the circuit was in operation.
operation:
WIN
PAC
THR
REV
NUI
IAN150/IPP MT
6/30/97
Window Size
Packet Size
Throughput
Reverse Charging
15-13
15-14
Code
0
1
2
16
17
18
19
20
21
22
23
24
25
Description
Invalid P(S)
Invalid P(R)
Packet type invalid
For state r1
For state r2
For state r3
For state p1
For state p2
For state p3
For state p4
For state p5
For state p6
Code
70
71
72
73
74
75
76
77
78
84
129
132
135
26
27
28
29
32
33
34
35
36
37
38
39
40
41
136
138
139
140
141
144
147
149
150
155
156
157
158
159
42
43
44
45
48
49
50
For state p7
For state d1
For state d2
For state D3
Packet not allowed
Packet too short
Packet too long
Unauthorized reject
Time expired
For incoming call
166
171
180
193
200
201
204
51
52
53
65
66
67
68
69
For call deflection
205
206
207
211
212
213
214
215
Description
Call collision
Facility not provided when expected
Invalid ITU-T specified DTE facility
Bad NUI facility
Station is offline
NMS offline est
Reselect received
BPS station down
DSR/DTR not active
in the online state
COP receive error
T10 timeout
link opening state
IAN150/IPP MT
6/30/97
Code
216
Description
Code
Description
222
217
223
218
224
219
225
220
requests or SNRMs
226
221
IAN150/IPP MT
6/30/97
15-15
Chapter
16
X.25 Monitoring
NOTE:
noted.
The Synchrony IAN-150 provides displays to monitor the status of X.25 ports and circuits, the
flow state and transmission of X.25 packets, and the status of X.25 calls. The screens most often
used for X.25 monitoring are:
•
Port Status and Control (1.2.1)
•
X.25 Status (1.5.4)
•
Circuit Status (1.5.5)
•
Cleared Circuit Status (1.5.6)
The screens used for X.25 troubleshootingEIA Modem Lead Status (Screen 1.2.4) and
X.25 Monitoring Tips
Each table can be sorted by key field(s) located in the first line of every table. To display
IAN150/IPP MT
6/30/97
16-1
Chapter 16, X.25 Monitoring
X.25 Port Status and Control
After you configure X.25 ports and activate them using the Cycle command, you can check the
status of the ports by executing the Read and Read Next commands from the Port Status and
Control screen (1.2.1). Enter the port number of the first X.25 port, press < . > to access the
command line, type R and press Enter. A typical X.25 port status screen is shown below.
Port
003
Port Type
Active Protocols
MTU Size
Speed
Admin State
Operational State
Operational Since
Address
X.25
128
9600
UP
UP
JUL08-96 12:54:19
00:00:00:00:00:00 (C)
Octets
Unicast Packets
Multicast Packets
Discards
Errors
Unknown Protos
Queue Length
IN
0
0
0
0
0
0
00:00:00:00:00:00 (N)
OUT
0
0
0
0
0
Line Util %:
Last Sec
15 Secs
IN
0
0
OUT
0
0
0
Figure 16-1. Typical X.25 Port Status and Control Screen
The top portion of the screen indicates the MTU size and data rate for the selected port, the
operational state of the port and the date and time when the operational state changed to the
current condition. The bottom portion of the screen gives the following data transmission
information as of the time the Read command was executed. To receive automatic updates of
this information, access the command line, type MON followed by a space and the number of
seconds you want the screen to be suspended between updates; then press Enter. The default
time interval is 5 seconds. To stop the automatic updates, press < . >.
Octets [IfInOctets] [IfOutOctets]
The total number of bytes received (IN) and transmitted (OUT) by this port, including Frame
Check Sequence (FCS) bytes.
Unicast Packets [IfInUcastPkts] [IfOutUcastPkts]
The number of packets having a unicast address that have been received from and transmitted to
a higher layer interface by this port.
Multicast Packets [IfInNucastPkts] [IfOutNucastPkts]
The number of packets having a multicast address that have been received and transmitted by this
port.
16-2
IAN150/IPP MT
6/30/97
Discards [IfInDiscards] [IfOutDiscards]
The number of received frames discarded, and the number of frames to be sent that have been
dropped due to internal conditions (such as lack of buffering).
Errors [IfInErrors] [IfOutErrors]
The number of invalid frames received, and the number of transmissions that failed because they
were considered invalid by the receiver. This number has no relationship to the number of REJ or
RNR frames sent or received.
Unknown Protos [IfInUnknownProtos]
The number of packets received by this port and discarded because they were unknown to the
protocol in use.
Queue Length [polStatComnifOutQLen]
The number of packets in the output packet queue awaiting transmission.
Line Util %
Indicates the percent of the data rate achieved, not including retransmissions. IN represents the
total number of frames and data bytes received at the port error free. OUT represents the total
number of frames and data bytes transmitted across the link.
Last Sec [polStatComnIfLineUtilInLastSec]
[polStatComnIfLineUtilOutLastSec]
Indicates the Line Util % IN and OUT achieved during the last second of communication across
the link. See Line Util %, above.
15 Secs [polStatComnIfLineUtilInLast15Sec]
[polStatComnIfLineUtilOutLast15Sec]
Indicates the Line Util % IN and OUT achieved during the last 15 second period of
communication across the link. See Line Util %, above.
IAN150/IPP MT
6/30/97
16-3
X.25 Status
To check the status of X.25 data transmission, from the Main Menu follow the path:
5. Packet Switching
4. X.25
or type SSX or 154 at any command line prompt and press Enter. Enter the port number of the
X.25 port you want to monitor and issue a Read command. A typical X.25 Status screen is
shown.
1.5.4 [SSX] X25 Status
Port
Flow
Flow
Flow
FRMR
FRMR
Busy
003
State
State Reason
State Changes
Cause In
Cause Out
Defers
INFO TRANSFER
ABM ENTERED
00000003
NONE
NONE
0
IN
1
0
0
0
1
0
0
132,634
SABMs
UAs
Rejects
RNRs
Disconnects
DMs
FRMR
Frames
Contents
Contents
T1 Timeouts
00000000
00000000
2
OUT
0
2
0
0
0
0
0
159,016
Figure 16-2. Typical X.25 Status Screen
The following paragraphs describe the X.25 Status parameters shown on this screen.
Corresponding MIB values, where applicable, appear in brackets next to the parameter names.
Flow State [lapbFlowCurrentMode]
The current status of this port with respect to the transmission of X.25 packets. Possible flow
states and their descriptions are:
16-4
DISCONNECT
The initial state before any frames or information has been transferred.
A DISC frame has been received by this port.
LINKSETUP
A Set Asynchronous Balanced Mode (SABM) frame has been sent by
this port.
FRAMEREJECT
An invalid frame has been received and a FRMR response has been
sent.
DISCONNECT RQ
A DISC frame has been sent by this port.
INFO TRANSFER
The normal information transfer state. A SABM(E) has been sent and
a UA received; or a SABM(E) has been received and a UA sent.
REJ SENT
An invalid sequence number has been received and a REJ frame has
been sent.
WAIT ACKNOW
The T1 timer has expired and a RR frame has been sent by this port.
IAN150/IPP MT
6/30/97
STATION BUSY
A Receive Not Ready (RNR) frame has been sent by this port.
REMOTE BUSY
A RNR frame has been received by this port from the remote device.
BOTH BUSY
A RNR frame has been received and also sent by this port.
WAIT ACK BUSY
The T1 timer has expired and an RNR frame has been sent out.
WAIT ACK RBSY
The T1 timer has expired and an RNR frame has been received.
WAIT ACK BBSY
The T1 timer has expired and an RNR frame has been sent and also
received.
REJ SENT RBSY
A REJ frame has been sent by this port and an RNR frame has been
received.
XID SENT
An XID frame has been sent by this port.
ERROR
An error state other than one described above has occurred.
OTHER
A condition or state not described above has occurred.
Flow State Reason [lapbFlowChangeReason]
Indicates the reason for the most recent change in flow state. Possible entries in this field include
ABM(E) ENTERED, ABM(E) RESET, DM RECEIVED, DM SENT, DISC RECEIVED,
DISC SENT, FRMR RECEIVED, FRMR SENT, N2 EXHAUSTED, UA RECEIVED, T1,
T2, or T3 EXPIRED, SABM(E) RECEIVED, RNR RECEIVED, NS ERROR RECEIVED,
ACK RECEIVED, OTHER, and NONE.
Flow State Changes [lapbFlowStateChanges]
Indicates the number of LAPB state changes that have occurred on this port, including link
resets.
FRMR Cause In [polStatWansX25FrmrFrameRx]
Indicates the reason the last Frame Reject Response (FRMR) was received. Possible entries in
this field are LENGTH ERROR, MTU EXCEEDED, INVALID NR, UNDEFINED, and
NONE.
FRMR Cause Out [polStatWansX25FrmrCodeTx]
Indicates the reason the last FRMR was transmitted. The possible entries are the same as for
FRMR Cause In.
Contents [polStatWansX25FrmrFrameTx]
Indicates the Information Field of the last Frame Reject Response received and transmitted.
Busy Defers [lapbFlowBusyDefers]
Indicates the number of times this port has been unable to transmit a frame due to a perceived
remote busy condition.
T1 Timeouts [lapbFlowT1Timeouts]
The T1 timer specifies how long the interface will wait before retransmitting frames that have not
been acknowledged. The number of T1 timeouts indicates how many times frames have had to be
retransmitted.
IAN150/IPP MT
6/30/97
16-5
Frame Traffic
The X.25 Status screen shows eight types of frame traffic statistics, as listed below.
16-6
SABMs
Number of received and transmitted Set Asynchronous Balanced Mode
frames. [polStatWansX25SabmIns] [polStatWansX25SabmOuts]
UAs
Number of received and transmitted Unnumbered Acknowledgement
frames. [polStatWansX25UaIns] [polStatWansX25UaOuts]
Rejects
Number of REJ frames received and transmitted by this port.
[lapbFlowRejInPkts] [lapbFlowRejOutPkts]
RNRs
Number of received and transmitted Receive Not Ready frames.
[polStatWansX25RnrIns] [polStatWansX25RnrOuts]
Disconnects
Number of received and transmitted Disconnects.
[polStatWansX25DiscIns] [polStatWansX25DiscOuts]
DMs
Number of received and transmitted Disconnected Mode frames.
[polStatWansX25DmIns] [polStatWansX25DmOuts]
FRMRs
Number of received and transmitted Frame Reject Response frames. The
FRMR unnumbered response is used by the DCE or DTE to report an error
condition not recoverable by retransmission of the identical frame.
[polStatWansX25FrmrIns] [polStatWansX25FrmrOuts]
Frames
The total number of received and transmitted frames.
[polStatWansX25FramesIns] [polStatWansX25FramesOuts]
IAN150/IPP MT
6/30/97
X.25 Circuit Status
To verify if a call has been established, go to the Circuit Status screen
(Screen 1.5.5). From the Main Menu follow the path:
5. Packet Switching
5. Circuit
or type SSC or 155 at any command line prompt and press Enter. Enter the source address of the
X.25 circuit you want to monitor and issue a Read command. A typical X.25 Circuit Status
screen for a call from Port 4 to Port 3 is shown below.
Source Addr
03-000
Dest Addr
00001-004-000
Call State
PVC State
Throughput
Window Size
Estab Time
Clear Time
Called Addr
DATA XFER
READY
9600
0007
JUL12-96 10:12:20
JUL12-96 10:19:43
3000
Reset State
READY
Packet Size
Timeout (min)
Direction
Duration
Calling Addr
128
NO
IN
0000:00:00
4000
Retransmit PDUs
DTE Resets
DCE Resets
Octets
PDUs
Interrupts
Segments
RNRs
REJs
0
0
0
IN
109,252
109,240
0
0
0
0
Data Timeouts
Interrupt Timeouts
Reset Timeouts
0
0
0
OUT
109,238
109,238
0
0
Figure 16-3. Typical X.25 Circuit Status Screen
The following paragraphs describe X.25 Circuit Status parameters. Corresponding MIB values,
where applicable, appear in brackets next to the parameter names.
Source Addr [polStatCircSrcPort] [polStatCircSrcLcn]
Indicates the port and circuit number of the circuit you are monitoring.
Indicates the Dispatch DLCI, port, and circuit number of the other end of this call.
IAN150/IPP MT
6/30/97
16-7
Indicates the status of the call at the time the Read command was executed. If the call has been
CLOSED
Displayed when the logical channel is unavailable. This state can exist for a
variety of reasons including physical port failure, network-level protocol
failure or network operator-initiated OFFLINE commands. This state is
defined as the p0 state.
READY
Indicates there is no call in existence at the present time. (p1)
DTE WAIT
Indicates the calling DTE has transmitted a Call Request packet across the
DCE WAIT
Indicates the DCE has indicated that there is an incoming call by sending an
COLLISION
Indicates the DTE and DCE have simultaneously transmitted a Call Request
packet and an Incoming Call packet by specifying the same logical channel.
The DCE will proceed with the call request and cancel the incoming call. (p5)
DTE_CLEAR
Indicates the DTE has transmitted a Clear Request packet across the
DCE_CLEAR
Indicates the DCE has transmitted a Clear Indication packet across the
READY
Indicates the Flow Control Ready (d1) state. A DTE or DCE Restart
Confirmation packet has been transmitted across the DTE/DCE interface.
DTE RESET
Indicates the DTE has requested a restart by transmitting a Reset Request
packet across the DTE/DCE interface. (d2)
DCE RESET
Indicates the DCE has indicated a restart by transmitting a Reset
Indication packet across the DTE/DCE interface. (d3)
16-8
WAIT LOCAL
Indicates the Wait Local Confirm (d5) state. A Reset packet has been sent
to the locally attached device; the IAN-150 is waiting for a response.
WAIT
REMOTE
Indicates the Wait Remote Confirm (d6) state. A Reset packet has been
sent to the remote end of the virtual circuit; the IAN-150 is waiting for a
response.
WAIT BOTH
Indicates the Wait Both Confirm (d4) state. Reset packets have been sent
to both the local and remote ends of the virtual circuit. The IAN-150 is
waiting for responses from both ends of the virtual circuit.
IAN150/IPP MT
6/30/97
Indicates the Flow Control Ready (d1) states that can occur for a permanent virtual circuit that is
in the Data Transfer state. Valid values:
READY
Displayed when the PVC is in the Flow Control Ready (d1) state.
DCE RESET
Indicates the DCE has indicated a reset by transmitting to the DTE a Reset
Indication packet.
OPERATIONAL
Indicates the DCE has reset the PVC with the cause network operational
because the network is again able to handle data traffic.
The internal statement machines uses the following two states to track the processing associated
with the establishment of a virtual connection required to support a PVC circuit.
D1 IGNORE
Indicates the DCE has reset the PVC with the cause network congestion
because of a momentary failure within the network.
D3 IGNORE
Indicates the DCE has reset the PVC with the cause network out of order
because of the network’s temporary inability to handle data traffic.
Indicates the throughput class that is currently configured for this circuit.
Indicates the MTU size that is currently configured for this circuit.
Indicates the current window size for this circuit.
Indicates the setting of the Timeout Min parameter for this circuit as configured on the Circuit
Configuration screen.
Indicates the date and time when the current call was established.
Indicates the direction of the call. For a called circuit, the direction is IN; for a calling circuit, the
direction is OUT.
Indicates the date and time when the last call was cleared.
Indicates the time in hours, minutes, and seconds since the call has been extablished for this
circuit.
Called Addr [polStatCircCalledDteAddress]
be zero.
IAN150/IPP MT
6/30/97
16-9
Calling Addr [polStatCircCallingDteAddress]
Indicates the number of Protocol Data Units that have been retransmitted on this circuit.
Indicates the number of times a data packet has been transmitted but not acknowledged on this
circuit.
Indicates the number of DTE-initiated packet level resets that have occurred on this circuit.
Indicates the number of times an interrupt packet has been transmitted but not acknowledged on
this circuit.
Indicates the number of DCE-initiated packet level resets that have occurred on this circuit.
Indicates the number of times a reset packet has been transmitted but not acknowledged on this
circuit.
Octets [polStatCircInOctets] [polStatCircOutOctets]
Indicates the total number of bytes of data that have been received and transmitted by this end of
the circuit.
Indicates the number of Protocol Data Units that have been received and transmitted by this end
of the circuit.
Indicates the number of incoming and outgoing interrupt packets for this circuit.
Indicates the number of incoming and outgoing segments for this circuit.
RNRs [polStatCircInRnrs]
Indicates the number of Receive Not Ready packets that have been received by this end of the
circuit.
REJs [polStatCircInRejs]
Indicates the number of Reject packets that have been received by this end of the circuit.
16-10
IAN150/IPP MT
6/30/97
X.25 Cleared Circuit Status
If you suspect that a call has been involuntarily cleared either during or after the setup phase,
check the 1.5.6 Cleared Circuit Status screen. To access this screen, from the Main Menu follow
the path:
5. Packet Switching
6. Cleared Circuits
or type SSL or 156 at any command line prompt and press Enter. From the command line, type
N to issue a Read Next command, then press Enter. A sample Cleared Circuit Status screen is
shown below.
Index
009
Newest Index
009
Source Addr
Called Addr
04-000
2000
Dest Addr
Calling Addr
00000-000-000
Estab Time
Cause Code
PDUs In
JUL08-96 12:54:19
013
0
Clear Time
Diagnostic
PDUs Out
JUL08-96 12:54:19
180
0
Facilities
Figure 16-4. X.25 Cleared Circuit Status Screen
The following paragraphs describe X.25 Cleared Circuit Status parameters. Corresponding MIB
screen by typing < . > N (for Read Next) and pressing Enter. The screen displays the statistics
that applied when the command was executed. To exit the screen, press < \ > or Esc.
Status table.
IAN150/IPP MT
6/30/97
16-11
be zero.
Identifies the date and time this circuit was established. A circuit is established when a Call
Identifies the date and time this circuit was cleared. A circuit is cleared when the device handler
gets out of phase or loses contact with the attached device, or when a Clear Request or Clear
Indication packet is processed by the circuit.
Identifies numerically the reason that the circuit was cleared. The table below gives the possible
circuit-clearing causes and their numeric codes.
Cause
16-12
Description
Integer Value
ACCESS BARRED
Call not accepted.
11
DTE ORIGIN
FAST SELECT
41
INCOMPATIBLE
33
INVALID FACILITY
0
3
19
NETWORK CONGESTED
NO REVERSE CHARGING
25
5
NOT OBTAINABLE
13
NUMBER BUSY
Number is in use.
1
OUT OF ORDER
9
3
REMOTE PROCEDURE
ERROR
17
RPOA
RPOA out of order.
21
SHIP ABSENT
For ship at sea.
57
143 - 255
IAN150/IPP MT
6/30/97
Provides additional information on what caused the circuit to be cleared. The X.25 diagnostic
codes supported by the IAN-150 are listed in Table 16-2 below.
operation:
WIN
PAC
THR
REV
NUI
Window Size
Packet Size
Throughput
Reverse Charging
Code
Description
Code
Description
0
39
Packet too long
1
Invalid P(S)
40
2
Invalid P(R)
41
16
Packet type invalid
42
17
For state r1
43
18
For state r2
44
19
For state r3
45
Unauthorized reject
20
For state p1
48
Time expired
21
For state p2
49
For incoming call
22
For state p3
50
23
For state p4
51
24
For state p5
52
25
For state p6
53
For call deflection
26
For state p7
65
27
For state d1
66
28
For state d2
67
29
For state D3
68
32
Packet not allowed
69
33
70
34
71
35
72
Call collision
36
73
37
74
38
Packet too short
75
IAN150/IPP MT
6/30/97
16-13
16-14
Code
Description
Code
Description
76
Packet too long
193
BPS station down
77
Invalid ITU-T-specified DTE facility
200
78
201
DSR/DTR not active
84
Bad NUI facility
204
in the online state
129
205
COP receive error
132
206
135
207
136
211
T10 timeout
138
212
139
213
140
214
141
215
link opening state
144
216
147
Station is offline
217
149
218
150
NMS offline est
219
155
220
requests or SNRMs
156
221
157
222
158
223
159
224
166
Reselect received
225
171
226
180
IAN150/IPP MT
6/30/97
Chapter
17
Frame Relay Monitoring
NOTE:
Processor (IPP) module an well as to the Synchrony IAN-150. All
noted.
to help you monitor Frame Relay. This chapter describes these capabilities.
Frame Relay Monitoring Tips
and press Enter.
information about a specific table entry, enter the appropriate identifying data in the first line of
the table after you have refreshed the screen, then execute a Read command. The screen displays
the number of seconds between screen updates. The default time interval is 5 seconds. Press
< . >, then type MON or MON x and press Enter. To end the Monitor process and remain at this
screen, press < . >.
IAN150/IPP MT
6/30/97
17-1
Chapter 17, Frame Relay Monitoring
Frame Relay Port Status
The Frame Relay Port Status display provides current general statistics on Frame Relay port
operation. To select the Frame Relay Port Status screen from the Main Menu, follow the path:
6. Frame Switching
1. Port
or enter SFP or 161 from the command line of any menu or screen and press Enter. The system
1.6.1 [SFP] Frame Relay Port Status
Port
011
Port Type
Local State
Local DLCI
PVC Count
Local Trunk Cost
Local Trunk ID
LAP
UP
0999
0000
00000
00000
Activity
Remote State
Remote Network
Remote Node
Remote Port
Remote Trunk ID
INACTIVE
UNKNOWN
00000
00000
000
00000
LMI Enqiries Out
LMI Responses In
LMI Timeouts
0
0
0
LMI Enqiries In
LMI Responses Out
LMI Protocol Errors
0
0
0
Total Discards
Congestion Discards
0
0
Sequence Discards
DLCI Discards
0
0
Figure 17-1. Frame Relay Port Status Screen
The following paragraphs describe Frame Relay Port Status parameters. Corresponding MIB
values, where applicable, appear in brackets next to the parameter names. To see current values
Port [tl1frIfIndex]
This parameter identifies the port to be examined.
Port Type [tl1frIfPortType]
Identifies the frame relay port type. Valid port types for the IAN-150 are:
NETWORK
TRUNK
GATEWAY
USER
HDLC
LAP
UNKNOWN
Activity [tl1frIfState]
Describes the status of the port. Valid values: ACTIVE, INACTIVE, and INVALID.
17-2
IAN150/IPP MT
6/30/97
Local State [tl1frIfLinkState]
Current operating state of the port. Possible states are:
UP
DOWN
Indicates the port is active and lmi messages are being exchanged
Indicates the port is down. Either the lmi messages are being
discarded or the physical link is down.
DISABLED Indicates the link is disabled.
INIT
Indicates the link is coming up and lmi protocol has not fully set up.
LOOPBACK Indicates the other end of the line also terminates on the local node.
Typically this happens if the local and remote nodes have the same node ID.
UNKNOWN The state of the local end of the trunk is not known.
Remote State [tl1frIfRemoteState]
The operational state of the remote end of this frame relay connection. The frame relay
connection can be a physical or virtual trunk, or a permanent virtual circuit (PVC). The possible
values are the same as the local states.
Local DLCI [tl1frIfLocalDlci]
The Data Link Connection Identifier (DLCI) for the local port.
Remote Network [tl1frIfRemoteNetworkId]
The network ID number assigned to the remote end.
PVC Count [tl1frIfNumPvcs]
The number of PVCs coming into this port.
Remote Node [tl1frIfRemoteNodeID]
The node ID of the remote frame relay switch.
Remote Port [tl1frIfRemoteIfIndex]
The number of the port on the remote end of this virtual or physical trunk.
Local Trunk Cost [tl1frIfTrunkCost]
The total cost metric to reach this node out of this port.
Remote Trunk ID [tl1frIfRemoteTrunkID]
The trunk ID number assigned to the trunk port at the remote end of this virtual or physical trunk.
Local Trunk ID [tl1frIfTrunkID]
The ID number assigned to this end of the virtual or physical trunk.
LMI Enquiries Out [tl1frIfSentLmiEnqs]
Total number of status enquiries transmitted.
LMI Enquiries In [tl1frIfReceivedLmiEnqs]
The total number of status enquiries received.
LMI Responses In [tl1frIfReceivedLmiResps]
Total number of status responses received.
IAN150/IPP MT
6/30/97
17-3
LMI Responses Out [tl1frIfSentLmiResps]
The total number of status responses transmitted.
LMI Timeouts [tl1FtIfLmiTimeouts]
Total number of protocol timeouts that have occurred.
LMI Protocol Errors [tl1frIfLmiProtocolErrors]
The total number of frames with protocol errors such as invalid information elements.
Total Discards [tl1frIfFramesTotalDiscards]
Total number of frames discarded by the port.
Sequence Discards [tl1frIfFramesSeqDiscards]
The total number of frames discarded because they are out of sequence. This field applies only to
trunk ports.
Congestion Discards [tl1frIfFramesCongDiscards]
Total number of frames discarded by the port due to congestion.
DLCI Discards [tl1frIfDlciDiscards]
The number of frames discarded by the port because they are illegal frames or because they are
designated for a DLCI that is unavailable.
Frame Relay Virtual Trunk Status
The Frame Relay Virtual Trunk Status display provides general information and statistics for
Frame Relay virtual trunk permanent virtual circuits. To select the Frame Relay Virtual Trunk
Status screen from the Main Menu, follow the path:
6. Frame Switching
2. Virtual Trunk
or enter SFV or 162 from the command line of any menu or screen and press Enter. The system
1.6.2 [SFV] Frame Relay Virtual Trunk Status
Port
000
Trunk DLCI
0000
Port Type
Local State
Virtual Interface
UNKNOWN
DOWN
000
Local Trunk Cost
Local Trunk ID
00000
00000
Activity
Remote State
Remote Network
Remote Node
Remote Port
Remote Trunk ID
INACTIVE
UNKNOWN
00000
00000
000
00000
LMI Enquiries Out
LMI Responses In
LMI Timeouts
0
0
0
LMI Enquiries In
LMI Responses Out
LMI Protocol Errors
0
0
0
Figure 17-2. Frame Relay Virtual Trunk Status Screen
17-4
IAN150/IPP MT
6/30/97
The following paragraphs describe Frame Relay Virtual Trunk Status parameters. Corresponding
MIB values, where applicable, appear in brackets next to the parameter names. To see current
values for a specific port, enter the port number in the Port field, then refresh the screen by
typing < . > R and pressing Enter. The screen displays the statistics that applied when the
Port [tl1frVTStatIfIndex]
This parameter identifies the port where the virtual trunk is configured.
Trunk DLCI [tl1frVTStatDlci]
Identifies the data link connection identifier (DLCI) for the virtual trunk permanent virtual circuit
(PVC).
Port Type [tl1frVTStatPortType]
Identifies the Frame Relay port type. Valid port types for the IAN-150 are:
NETWORK
TRUNK
GATEWAY
USER
HDLC
LAP
UNKNOWN
Activity [tl1frVTStatState]
Describes the status of the port. Valid values: ACTIVE, INACTIVE, and INVALID.
Local State [tl1frVTStatLinkState]
The operational state of the local end of this virtual trunk. Possible states:
UP
DOWN
Indicates the virtual trunk is active and lmi messages are being exchanged
Indicates the virtual trunk is down. Either the lmi messages are being
discarded or the physical link is down.
DISABLED Indicates the link is disabled.
INIT
Indicates the link is coming up and lmi protocol has not fully set up.
LOOPBACK Indicates the other end of the virtual trunk also terminates on the local node.
Typically this happens if the local and remote nodes have the same node ID.
UNKNOWN The state of the local end of the virtual trunk is not known.
Remote State [tl1frVTStatRemoteState]
The operational state of the remote end of this virtual trunk. The possible states are the same as
the local states.
Virtual Interface [tl1frVTStatVtIndex]
The internal reference number assigned to the virtual trunk interface.
Remote Network [tl1frVTStatRemoteNetworkID]
The network number assigned to the remote end of this virtual trunk.
Remote Node [tl1frVTStatRemoteNodeID]
The node ID of the remote Frame Relay switch.
IAN150/IPP MT
6/30/97
17-5
Local Trunk Cost [tl1frVTStatTrunkCost]
Cost metric of this virtual trunk for routing purposes.
Remote Port [tl1frVTStatRemoteIfIndex]
Logical port number of this virtual trunk port at the remote end of this virtual trunk.
Local Trunk ID [tl1frVTStatTrunkID]
The trunk ID number assigned to the trunk port at the local end of this virtual trunk.
Remote Trunk ID [tl1frVTStatRemoteTrunkID]
The trunk ID number assigned to the trunk port at the remote end of this virtual trunk.
LMI Enquiries OUT [tl1frVTStatSentLmiEnqs]
Each end of a serial trunk sends heartbeat requests; this number indicates the number of requests
sent by this trunk port since the link was created.
LMI Enquiries IN [tl1frVTStatReceivedLmiEnqs]
Each end of a serial trunk receives heartbeat requests; this number indicates the number of
requests received by this trunk port since the link was created.
LMI Responses IN [tl1frVTStatReceivedLmiResps]
This number indicates the number of responses received by this trunk port to heartbeat requests
since this link was created.
LMI Responses OUT [tl1frVTStatSentLmiResps]
This number indicates the number of responses sent by this trunk port to heartbeat requests since
this link was created.
LMI Timeouts [tl1frVTStatLmiTimeouts]
Indictaes the number of timeouts that have occurred on this trunk connection since the link was
created.
LMI Protocol Errors [tl1frVTStatLmiProtocolErrors]
Indicates the number of protocol errors that have occurred on this trunk connection since the link
was created.
17-6
IAN150/IPP MT
6/30/97
Frame Relay PVC Status
The Frame Relay PVC Status display provides current general statistics on Frame Relay PVC
operation. It is also possible to Install, Evacuate, or Cycle a PVC from the command line of this
screen. To select the Frame Relay PVC Status screen from the Main Menu, follow the path:
6. Frame Switching
3. PVC
or enter SFC or 163 from the command line of any menu or screen and press Enter. The system
1.6.3 [SFC] Frame Relay PVC Status
Port
000
PVC DLCI
0000
Circuit Type
Priority Level
Sequence Num Out
Sequence Num In
Offered Load (Kbps)
UNKNOWN
4
000
000
0
External Status
Internal Status
Since Creation
Since Update
**-***-***-***
**-***-***-***
0000:00:00.00
0000:00:00.00
Total
Dropped
Bandwidth
Congestion
Sequence
BECN
FECN
DE Rcv
DE Set
FRAMES IN
0
0
0
0
0
0
0
0
0
BYTES IN
0
0
0
(C)
FRAMES OUT
0
BYTES OUT
0
0
0
0
0
0
0
0
0
Figure 17-3. Frame Relay PVC Status Screen
The following paragraphs describe Frame Relay PVC status parameters. Corresponding MIB
Port [tl1frUserConnStatIfIndex]
This parameter identifies the port where the permanent virtual circuit (PVC) is configured.
PVC DLCI [tl1frUserConnStatDlci]
The Data Link Connection Identifier (DLCI) of this PVC. The letter C shown in parentheses next
to the PVC DLCI indicates that this PVC is Configured. The letter L shown in parentheses next
to the PVC DLCI indicates that this PVC is Learned.
IAN150/IPP MT
6/30/97
17-7
Circuit Type [tl1frUserConnStatType]
Describes the type of circuit configured for this PVC. Valid circuit types are:
NETWORK
GATEWAY
VIR TRUNK
MULTICAST
UNKNOWN
External Status [tl1frUserConnStatExtLmiState]
The status of this PVC from the vantage point of the external circuit to which this PVC is
connected.
Priority Level [tl1frUserConnStatPri]
The Frame Relay priority level for the data stream on this PVC. Valid priority levels are from 1
to 8, with 1 being the highest priority and 8 being the lowest.
Internal Status [tl1frUserConnStatIntLmiState]
This field is applicable only to internetwork PVCs. It is the status of the PVC as viewed
internally between the Frame Relay switch point and the PVC.
Sequence Num Out [tl1frUserConnStattxSeqNum]
This field applies to virtual trunks, which use sequence numbers to ensure the integrity of
transmitted data.
Since Creation [tl1frUserConnStatCreationTime]
Displays the time in hours,minutes, and seconds that this PVC has been active.
Sequence Num In [tl1frUserConnStatRxSeqNum]
This field applies to virtual trunks, which use sequence numbers to ensure the integrity of
received data.
Since Update [tl1frUserConnStatLastTimeChange]
Displays the time in hours, minutes, and seconds since the last change in status occurred on this
PVC.
Offered Load [tl1frUserConnStatOfferedLoad]
This is normally the sum of the Committed Information Rate (CIR) and the Excess Information
Rate (EIR), expressed in Kbps. If congestion management is in effect, and if congestion is
occurring, the offered load will be less than the sum of CIR + EIR.
Total
Total number of frames either sent or received over this PVC.
Total FRAMES IN [tl1frUserConnStatReceivedFrames] indicates the number of frames
received over this PVC.
Total BYTES IN [tl1frUserConnStatReceivedOctets] indicates the number of bytes received
over this PVC.
Total FRAMES OUT [tl1frUserConnStatSentFrames] indicates the number of frames
transmitted over this PVC.
Total BYTES OUT [tl1frUserConnStatSentOctets] indicates the number of bytes transmitted
over this PVC.
17-8
IAN150/IPP MT
6/30/97
Dropped
The number of incoming frames [tl1frUserConnStatTotalFrameDiscards] and bytes
[tl1frUserConnStatTotalOctetDiscards] discarded by this PVC.
Bandwidth
FRAMES/BYTES IN: The total number of frames/bytes dropped on receive due to bandwidth
limit. [tl1frUserConnStatRcvdBwDiscardFrames] [tl1frUserConnStatRcvdBwDiscardOctets]
FRAMES/BYTES OUT: The total number of frames/bytes sent in error due to bandwidth limit.
[tl1frUserConnStatSentBwDiscardFrames] [tl1frUserConnStatSentBwDiscardOctets]
Congestion
The number of incoming frames [tl1frUserConnStatCongFrameDiscards] and packets
[tl1frUserConnStatCongOctetDiscards] with the DE bit set that were dropped due to congestion.
Sequence
The number of frames and bytes arriving at this PVC from the internal Frame Relay switch point
out of sequence. [tl1frUserConnStatSeqFrameDiscards] [tl1frUserConnStatSeqOctetDiscards]
BECN
The number of backward explicit congestion notification bits sent [tl1frUserConnStatSentBecns]
and received [tl1frUserConnStatReceivedBecns] over this PVC.
FECN
The number of forward explicit congestion notification bits sent [tl1frUserConnStatSentFecns]
and received [tl1frUserConnStatReceivedFecns] over this PVC.
DE Rcv
The total number of frames received [tl1frUserConnStatReceivedDes] or sent
[tl1frUserConnStatSentDes] with the Discard Eligibility (DE) bit set.
DE Set
The total number of frames received [tl1frUserConnStatReceivedSetDes] or transmitted
[tl1frUserConnStatSentSetDes] with the DE bit set that were discarded while the port was
congested or exceeded the excess burst size.
IAN150/IPP MT
6/30/97
17-9
Frame Relay Route Topology Status
The Frame Relay Route Topology Status display provides current statistics on the Frame Relay
route manager database. To select the Frame Relay Route Topology Status screen from the Main
6. Frame Switching
4. Route Topology
or enter SFR or 164 from the command line of any menu or screen and press Enter. The system
1.6.4 [SFR] Frame Relay Route Topology Status
Node
00000
Proximity
Device Count
UNKNOWN
0
Since Connection
Since Update
Device List:
0000
0000
0000
0000
Primary Interface
Hop List:
0000
0000
0000:00:00.00
0000:00:00.00
0000
0000
0000
0000
0000
0000
0000
0000
0000
0000
000 V00
0000 0000
0000 0000
Hop Count
0000 0000
0000 0000
0
0000
0000
Cost
0000
0000
0000
0000
00000
0000
0000
Secondary Interface
Hop List:
000 V00
0000 0000
0000 0000
Hop Count
0000 0000
0000 0000
0
0000
0000
Cost
0000
0000
0000
0000
00000
0000
0000
Tertiary Interface
Hop List:
000 V00
0000 0000
0000 0000
Hop Count
0000 0000
0000 0000
0
0000
0000
Cost
0000
0000
0000
0000
00000
0000
0000
Figure 17-4. Frame Relay Route Topology Status Screen
The following paragraphs describe Frame Relay Route Topology Status parameters.
view current values for a specific node, enter the node number in the Node field, then execute a
Read command by typing < . > R and pressing Enter. The screen displays the statistics that
Node [tl1frRouteNodeID]
The node ID for this entry.
Proximity [tl1frRouteProximity]
Proximity of displayed node to local node. Valid values:
UNKNOWN - Doesn’t fall into the below listed categories
LOCAL - Refers to this node.
NEIGHBOR- Node that is directly connected via a trunk or virtual trunk
REMOTE- Node that is not directly connected, meaning that it is at least two hops away.
17-10
IAN150/IPP MT
6/30/97
Since Connection [tl1frRouteCreationTime]
The amount of time since this entry was added to the route table, listed as
hours:minutes:seconds:milliseconds.
Device Count [tl1frRouteDevices]
The number of user devices attached to this node.
Since Update [tl1frRouteLastTimeChanges]
The time since the last update in status for this entry.
Device List [tl1frRouteDevice00]...[tl1frRouteDevice15]
The DLCIs of the user devices on this node.
Primary Interface [tl1frRoute1ifIndex]
The primary interface the route manager will use for frames destined for the node. Virtual
addresses are identified by the letter V and the virtual address number, 0-15. (see Virtual Trunk
Interface, below).
Virtual Trunk Interface [tl1frRoute1VirtIndex]
The virtual interface the route manager will use for frames destined for the node. Virtual
addresses are identified by the letter V and the virtual address number, 0-15.
Hop Count [tl1frRoute1HopCount]
The number of intermediary nodes.
Cost [tl1frRoute1Cost]
The total cost metric to reach the node out of this port.
Hop List [tl1frRoute1Hop00]...[tl1frRoute1Hop15]
The intermediate node list.
NOTE:
IAN150/IPP MT
6/30/97
Secondary and Tertiary interface information will be valid if such
routes exist.
17-11
Chapter
18
ISDN Monitoring
NOTE:
IAN-150.
The IAN-150 provides statistical data and diagnostic reports to help you monitor performance
and status of ISDN Basic Rate Interface (BRI). This chapter describes the screens and menus
associated with ISDN monitoring.
ISDN Monitoring Tips
screen, the values in the default template appear to be set to zero. To view current values, refresh
type < . > N (for Read Next) and press Enter. Any display that contains index number fields are
functionally considered to be tables.
or Esc.
IAN150/IPP MT
6/30/97
18-1
Chapter 18, ISDN Monitoring
ISDN Status
The ISDN Status menu lists the monitoring topics available that relate to ISDN. To access the
ISDN Status menu, from the Main Menu, follow the path:
7. ISDN
or type SI or 17 from the command line of any menu or screen and press Enter. The system
1.7 [SI] ISDN Status
1. D-Channel
2. B-Channel
3. Destination
4. Call History
Figure 18-1. ISDN Status Menu
ISDN Status information is comprised of four different displays:
•
D-Channel Status and Statistics - provides information about ISDN D-channels.
•
B-Channel Status and Statistics - provides information about ISDN Bearer (B) channels.
•
Destination Status and Statistics - provides information about the call destination or
endpoint.
•
Call History - provides information about each ISDN disconnected call.
18-2
IAN150/IPP MT
6/30/97
ISDN D-Channel Status
ISDN uses Link Access Procedure-D (LAPD) over the D-Channel to transport information
between layer 2 entities across the ISDN network. The ISDN D-Channel Status and Statistics
screen provides information about LAPD operation over a specified ISDN port. To select the
ISDN D-Channel Status and Statistics screen, from the Main Menu, follow the path:
7. ISDN
1. D-Channel
or enter SID or 171 from the command line of any menu or screen and press Enter. The system
1.7.1 [SID] ISDN D-Channel Status and Statistics
Port
001
Flow State
FRMR Cause In
FRMR Cause Out
UNKNOWN
NONE
NONE
SABMEs
UAs
Disconnects
DMs
FRMRs
UIs
RNRs
Rejects
Frames
Bytes
Frames Retrans
Bytes Retrans
Discards
Contents
Contents
IN
0
0
0
0
0
0
0
0
0
0
0000000000
0000000000
OUT
0
0
0
0
0
0
0
0
0
0
0
0
0
Figure 18-2. ISDN D-Channel Status and Statistics Screen
The following paragraphs describe ISDN D-Channel Status and Statistics parameters.
view current values for a specific port, enter the port number in the Port field, then refresh the
screen by typing < . > R and pressing Enter. The screen displays the statistics that applied when
IAN150/IPP MT
6/30/97
18-3
Port [polStatIsdnLapdIntfNum]
Flow State [polStatIsdnLapdState]
Describes the current state ISDN is transiting through in its attempt to establish a connection.
Valid values:
18-4
UNKNOWN
Indicates, when the TEI Type configuration parameter from the
ISDN Port Configuration screen (2.7.1) has been set to
DYNAMIC, an unidentified flow state. If the TEI Type parameter
value has been set to STATIC, which is the default value, ISDN
will not reach this state.
TEI ASSIGNED
Indicates the Terminal Endpoint Identifier (TEI) has been
assigned.
TMR REC NORM
Indicates the T200 timer expired while ISDN was in the MFRM
EST NORM state.
TMR REC BUSY
EST BUSY state.
TMR REC REJ
EST REJ state.
MFRM EST BUSY
Indicates the D-channel link has entered the Receive Busy
condition. Receiver Not Ready frames (RNR) have been
transmitted and Information (I) frames will not be accepted.
AWAIT RELEASE
Indicates that ISDN has transmitted Disconnect (DISC) frames
and is now waiting to receive Unnumbered Acknowledgment
(UA) frames.
FRAME REJECT
Indicates an unrecoverable error has been detected. ISDN has
transmitted Frame Rejected (FRMR) frames and is waiting for the
link to be reset.
MFRM EST NORM
Indicates the D-channel has been established.
MFRM EST REJ
Indicates that ISDN has received an Information (I) frame out of
sequence. ISDN has transmitted Rejected (REJ) frames to request
retransmission of the missing frame(s).
AWAIT EST
ISDN has transmitted Set Asynchronous Balanced Mode (SABM)
frames and is waiting to receive Unnumbered Acknowledgment
(UA) frames.
IAN150/IPP MT
6/30/97
FRMR Cause In [polStatIsdnLapdFrmrReceived]
Defines the information ISDN has received in a received Frame Rejected frame, indicating that
ISDN has generated and transmitted a defective packet. Valid values:
NONE
Indicates no FRMR frames have been received.
UNDEFINED
Indicates the control field in the received LAPD frame is not
defined.
LENGTH ERROR
Indicates the size of the supervisory frame exceeded acceptable
values.
MTU EXCEEDED
Indicates data unit size has exceed the value configured in the MTU
Size parameter from the ISDN Port Configuration screen (2.7.1).
INVALID NR
Contents [polStatIsdnLapdFrmrCodeRx]
Displays the information contained in the received FRMR frame.
FRMR Cause Out [polStatIsdnLapdFrmrSent]
Defines the information ISDN has transmitted in a Frame Rejected frame, indicating that ISDN
has received a defective packet. Valid values:
NONE
Indicates no FRMR frames have been received.
UNDEFINED
Indicates the control field in the received LAPD frame is not
defined.
LENGTH ERROR
Indicates the size of the supervisory frame exceeded acceptable
values.
MTU EXCEEDED
Indicates that data unit size has exceed the value configured in the
MTU Size parameter from the ISDN Port Configuration screen
(2.7.1).
INVALID NR
Contents [polStatIsdnLapdFrmrCodeTx]
Displays the information contained in the transmitted FRMR frame.
SABMEs [polStatIsdnLapdSabmIns] [polStatIsdnLapdSabmOuts]
Indicates the number of Set Asynchronous Balanced Mode Extended (SABME) frames received
and transmitted over this connection. SABMEs IN lists the number of SABME frames received.
SABMEs OUT lists the number of SABM frames transmitted.
UAs [polStatIsdnLapdUaIns] [polStatIsdnLapdUaOuts]
Indicates the number of Unnumbered Acknowledgment (UA) frames received and transmitted
over this connection. UAs IN lists the number of UA frames received. UAs OUT lists the
number of UA frames transmitted.
Disconnects [polStatIsdnLapdDiscIns] [polStatIsdnLapdDiscOuts]
Indicates the number of Disconnect (DISC) frames received and transmitted over this connection.
Disconnects IN lists the number of Disconnect frames received. Disconnects OUT lists the
number of Disconnect frames transmitted.
IAN150/IPP MT
6/30/97
18-5
DMs [polStatIsdnLapdDmIns] [polStatIsdnLapdDmOuts]
Indicates the number Disconnect Mode (DM) frames of received and transmitted over this
connection. DMs IN lists the number of DM frames received. DMs OUT lists the number of DM
frames transmitted.
FRMRs [polStatIsdnLapdFrmrIns] [polStatIsdnLapdFrmrOuts]
Indicates the number of Frame Rejected (FRMR) frames received and transmitted over this
connection. FRMRs IN lists the number of FRMR frames received. FRMRs OUT lists the
number of FRMR frames transmitted.
UIs [polStatIsdnLapdUiIns] [polStatIsdnLapdUiOuts]
Indicates the number of Unnumbered Information (UI) frames received and transmitted over this
connection. UI IN lists the number of UI frames received. UI OUT lists the number of UI frames
transmitted.
RNRs [polStatIsdnLapdRnrIns] [polStatIsdnLapdRnrOuts]
Indicates the number of Receiver Not Ready (RNR) frames received and transmitted over this
connection. RNRs IN lists the number of RNR frames received. RNRs OUT lists the number of
RNR frames transmitted.
Rejects [polStatIsdnLapdRejIns] [polStatIsdnLapdRejOuts]
Indicates the number of Rejected frames received and transmitted over this connection. Rejects
IN lists the number of Rejected frames received. Rejects OUT lists the number of Rejected
frames transmitted.
Frames [polStatIsdnLapdFramesIns] [polStatIsdnLapdFramesOuts]
Indicates the total number of I-frames received and transmitted over this connection. Frames IN
lists the number of frames received. Frames OUT lists the number of frames transmitted.
Bytes [polStatIsdnLapdBytesIns] [polStatIsdnLapdBytesOuts]
Indicates the total number of bytes of I-frames received and transmitted over this connection.
Bytes IN lists the number of bytes received. Bytes OUT lists the number of bytes transmitted.
Frames Retrans [polStatIsdnLapdFramesRetrans]
Indicates the total number of I-frames retransmitted over this connection.
Bytes Retrans [polStatIsdnLapdBytesRetrans]
Indicates the total number of bytes of I-frames retransmitted over this connection.
Discards [polStatIsdnLapdFrmDiscards]
Indicates the total number of frames discarded.
18-6
IAN150/IPP MT
6/30/97
ISDN B-Channel Status
The ISDN B-Channel Status screen provides call status and data transmission information about
a specific ISDN bearer channel. To select the ISDN B-Channel Status and Statistics screen, from
7. ISDN
2. B-Channel
or enter SIB or 172 from the command line of any menu or screen and press Enter. The system
1.7.2 [SIB] ISDN B-Channel Status and Statistics
Port
001
B-Channel ID
01
Call State
Peer Address
Destination
Call Reason
Call Setup Time
DEACTIVATE
NCP State
IDLE
000
NO CALL
AUG01-96 09:38:07
Info Xfer Cap
Call Origin
Call Connect Time
UNKNOWN
NO CALL
AUG01-96 09:38:07
Call Disc Time
AUG01-96 09:38:07
Call Duration
0000:00:00
Frames
Octets
IN
0
0
OUT
0
0
Figure 18-3. ISDN B-Channel Status and Statistics Screen
The following paragraphs describe ISDN B-Channel Status and Statistics parameters.
view current values for a specific port, enter the port number in the Port field, then refresh the
screen by typing < . > R and pressing Enter. The screen displays the statistics that applied when
Port [polStatIsdnBearerIfIndex]
Indicates the port (and by default, the B-channel) through which ISDN traffic is being
transmitted. By default, port 6 is identified with B-1 and port 7 is identified with B-2.
B-Channel ID [polStatIsdnBearerChannelNumber]
Identifies the B-channel number. Valid values:
01 B1
02 B2
IAN150/IPP MT
6/30/97
18-7
Call State [polStatIsdnBearerOperStatus]
Describes the current state of the ISDN connection. Valid values:
DEACTIVATE
Indicates that ISDN layer 1 has been deactivated.
WAIT ACTIVATE
Indicates an outgoing call request is pending and ISDN layer 1 is
waiting to be activated.
IDLE
Indicates ISDN layer 1 has been activated but that no calls are
currently connected.
INCOMING CALL
Indicates ISDN layer 1 has been activated and an incoming call
has been accepted but ISDN has not yet received the connect
acknowledgment.
WAIT ACK
Indicates ISDN layer 1 has been activated and an outgoing call
request has been sent to the internal connection manager but
ISDN has not yet received an acknowledgment from the internal
connection manager.
CALLING
Indicates ISDN layer 1 has been activated and the connect
manager has acknowledged the outgoing call request but ISDN
has not yet received the connect acknowledgment.
ACTIVE
Indicates ISDN layer 1 has been activated and the connect
acknowledgment has been received.
CLEARING
Indicates ISDN layer 1 has been activated and the call disconnect
has been transmitted but ISDN has not yet received the clear
confirmation.
NCP State [polStatIsdnBearerNcpState]
Describes the state of the Basic Rate Interface Network Control Protocol (BRI NCP). Valid
values:
IDLE
Indicates no B-channel connection has been established.
WAIT OUT CONN
Indicates an outgoing call has been initiated and ISDN is waiting
to receive a call connect acknowledgment.
WAIT ACK
Indicates an outgoing call connect acknowledgment has been
received and an NCP PDU sent. ISDN is waiting to receive an
acknowledgment packet (NCP ACK PDU).
WAIT PDU
Indicates an incoming call connect acknowledgment has been
received and ISDN is waiting to receive an NCP PDU.
WAIT IN CONN
Indicates an incoming call has been accepted and ISDN is
waiting to receive a call connect acknowledgment.
ACTIVE
Indicates BRI NCP has been established.
Peer Address [polStatIsdnBearerPeerAddress]
Identifies the ISDN call number of the destination.
Destination [polStatIsdnBearerDestId]
Identifies the destination number as defined in the Destination parameter from the ISDN
Destination Configuration screen (2.7.2).
18-8
IAN150/IPP MT
6/30/97
Info Xfer Cap [polStatIsdnBearerInfoType]
Describes the type of information being transmitted over this ISDN connection. Valid values:
UNKNOWN
Unknown call format.
SPEECH
Voice transmission. This option is not supported in the
current release.
UNRESTRICTED 64K
Data transmitted at 64 kilobits per second.
UNRESTRICTED 56K
RESTRICTED DIGITAL
This option is not supported in the current release.
AUDIO 3.1 KHZ
Audio transmission at 3.1 kilohertz. This option is not
supported in the current release.
AUDIO 7 KHZ
Audio transmission at 7 kilohertz. This option is not
VIDEO
Video transmission. This option is not supported in the
current release.
PACKET SWITCHED
Data transmitted using X.25 over B or D channel. This option
is not supported in the current release.
Call Reason [polStatIsdnBearerConnectReason]
Describes the type of ISDN call. Valid values:
NO CALL
Indicates no call is currently connected.
OUT TRAFFIC
OUT MANUAL
Indicates ISDN placed a manual call.
OUT DATE TIME
OUT OVERFLOW
OUT BACKUP
Indicates ISDN is making a call so that it can backup a WAN line.
IN TRAFFIC
IN MANUAL
Indicates ISDN is receiving a manual call.
IN OVERFLOW
IN BACKUP
Indicates a remote device is placing a call to initiate a WAN line
backup.
OUT 128K BACKUP
IN 128K BACKUP
64K LEASED LINE
128K LEASED
LINE
Call Origin [polStatIsdnBearerCallOrigin]
Describes the origin of the most current connection. Valid values:
NO CALL
ORIGINATE Indicates the call was being transmitted from this device.
ANSWER
Indicates the call was being received by this device.
IAN150/IPP MT
6/30/97
18-9
Call Setup Time [polStatIsdnBearerCallSetupTime]
Specifies the date (MMMDD-YY) and time (HH:MM:SS) that the last connection was initiated.
Call Connect Time [polStatIsdnBearerCallConnectTime]
Specifies the date (MMMDD-YY) and time (HH:MM:SS) that the last connection was made.
Call Disc Time [polStatIsdnBearerCallClearTime]
Specifies the date (MMMDD-YY) and time (HH:MM:SS) that the last connection was ended.
Call Duration [polStatIsdnBearerCallDuration]
Specifies the total length of time, in HHHH:MM:SS, of the connection.
Frames [polStatIsdnBearerFramesIns] [polStatIsdnBearerFramesOuts]
Indicates the number of frames received and transmitted over this connection. Frames IN lists
the number of frames received. Frames OUT lists the number of frames transmitted.
Octets [polStatIsdnBearerBytesIns] [polStatIsdnBearerBytesOuts]
Indicates the number of bytes received and transmitted over this connection. Octets IN lists the
number of bytes received. Octets OUT lists the number of bytes transmitted.
ISDN Destination Status
The ISDN Destination Status and Statistics screen provides information about the ISDN endpoint or call destination based on the information configured in the ISDN Destination
Configuration screen (1.7.3) in addition to call connectivity information. To select the ISDN
Destination Status and Statistics screen ,from the Main Menu, follow the path:
7. ISDN
3. Destination
or enter SIN or 173 from the command line of any menu or screen and press Enter. The system
1.7.3 [SIN] ISDN Destination Status and Statistics
Destination
01
ISDN Number Index
01
Description
Call Permission
Max. Retries
Failure Delay (sec)
OUTGOING
000
00000
Info Transfer Speed
Retry Delay (sec)
64K
00000
ISDN Number
B-Channel Port
State
Successful Call Reqs
Accepted Calls
00
FREE
00000
00000
MAC Address
Total Conn Time
Failed Call Reqs
Rejected Calls
Last
Last
Last
Last
NO CALL
000
000
000
Last Call Reason
Last Call Conn Time
Last Call Disc Time
Call
Call
Call
Call
Origin
Disc Cause
Disc Diag
Disc Loc
00:00:00:00:00:00
0000:00:00
00000
00000
NO CALL
AUG01-96 09:38:07
AUG01-96 09:38:07
Figure 18-4. ISDN Destination Status and Statistics Screen
18-10
IAN150/IPP MT
6/30/97
The following paragraphs describe ISDN Destination Status and Statistics parameters.
Corresponding MIB values, where applicable, appear in brackets next to the parameter names.
The IAN-150 uses the first two fields in this screen, Destination and ISDN Number Index, as
key fields. To display current information about a particular destination, refresh the screen by
entering the appropriate Destination number and/or ISDN Number Index, then type < . > R (for
Read) and press Enter. The screen displays the statistics that applied when the command was
In its current IAN-150 implementation, ISDN is used for either manual calls or for WAN backup.
ISDN manual calls are made from the ISDN Destination Status and Statistics screen after ISDN
port and destination parameters have been configured. To initiate a manual call, enter the
appropriate Destination number and ISDN Number Index, then press < . > R to refresh the
screen. Then press < . > SC (Setup Call command). To disconnect or end the call, press < . >
CC (Clear Call command). For more information about configuring ISDN destination and port
parameters, see ISDN Configuration in the Synchrony IAN-l50/IPP Reference Manual.
Destination [polStatIsdnNbrIndex}
Identifies a specific end point or call destination as defined in the Destination parameter from the
ISDN Destination Configuration screen (2.7.2).
ISDN Number Index [polStatIsdnNbrAddressIndex]
Identifies a specific table entry as defined in the ISDN Number Index parameter from the ISDN
Description [polStatIsdnNbrDescr]
Describes the selected destination as defined in the Description parameter from the ISDN
Call Permission [polStatIsdnNbrCallPermission]
Identifies what type of calls are permitted in relation to the selected destination. Valid values:
OUTGOING
Outgoing calls to this destination are permitted.
INCOMING
Incoming calls from this destination are permitted.
BIDIRECT
Both incoming calls from and outgoing calls to this destination are
permitted.
Info Transfer Speed [polStatIsdnNbrSpeed]
Valid values:
64K
64 kilobits per second.
56K
56 kilobits per second.
Max. Retries [polStatIsdnNbrMaxRetries]
Indicates the maximum amount of times ISDN has attempted to retransmit a call. This value will
not exceed the configured value for the Max. Retries parameter from the ISDN Destination
Configuration screen (2.7.2).
Retry Delay (sec) [polStatIsdnNbrRetryDelay]
Indicates the amount of time, in seconds, that ISDN has waited before retrying to transmit a call.
This value will not exceed the configured value for the Retry Delay parameter from the ISDN
IAN150/IPP MT
6/30/97
18-11
Failure Delay (sec) [polStatIsdnNbrFailureDelay]
Indicates the amount of time, in seconds, that ISDN has waited after an unsuccessful series of
retries before starting a new series of attempts to reach the destination. This value will not exceed
the configured value for the Failure Delay parameter from the ISDN Destination Configuration
screen (2.7.2).
ISDN Number [polStatIsdnNbrAddress]
Indicates the ISDN call number for the destination as configured in the ISDN parameter from the
ISDN Destination Configuration screen (2.7.2).
B-Channel Port [polStatIsdnNbrBChanIfIndex]
Indicates the B-Channel port over which a call to this destination is either sent or received. Valid
values:
Port 06 - Indicates B 1.
Port 07 - Indicates B 2.
MAC Address [polStatIsdnNbrMacAddress]
Indicates the MAC address of the destination, as defined.
State [polStatIsdnNbrState]
Describes the state of the connection between the IAN-150 and the destination. Valid values:
FREE
Indicates the line to this destination is clear and ready to accept or place a
call.
INVALID
Indicates the line to this destination is out of order.
USED
Indicates the line to this destination is in use; that the call is currently in
progress.
BUSY
Indicates the line to this destination is transitioning to the FREE state. No
call will be made or accepted on this line.
Total Conn Time [polStatIsdnNbrConnectTime]
Screens the total amount of connection time, in hours:minutes:seconds, to/from this destination
since the system comes up.
Successful Call Reqs [polStatIsdnNbrSuccessfulCalls]
Number of successful call requests that have been placed to this destination.
Failed Call Reqs [polStatIsdnNbrFailedCalls]
Number of unsuccessful call requests that have been placed to this destination.
Accepted Calls [polStatIsdnNbrAcceptCalls]
Number of accepted ISDN calls that have been placed to this destination.
Rejected Calls [polStatIsdnNbrRejectCalls]
Number of calls that have been rejected by this destination.
Last Call Origin [polStatIsdnNbrLastCallOrigin]
Provides information regarding the last ISDN connection with this destination. Valid values:
NO CALL
Indicates no call is currently active.
ORIGINATE Indicates the call originated from this particular IAN-150.
18-12
IAN150/IPP MT
6/30/97
ANSWER
Indicates the IAN-150 received this call from the destination.
Last Call Reason [polStatIsdnNbrLastCallReason]
Describes the type of ISDN call during the last ISDN connection with this destination. Valid
values:
NO CALL
OUT TRAFFIC
OUT MANUAL
Indicates that ISDN placed a manual call.
OUT DATE TIME
OUT OVERFLOW
OUT BACKUP
Indicates that ISDN is making a call so that it can backup a WAN
line.
IN TRAFFIC
IN MANUAL
Indicates that ISDN is receiving a manual call.
IN OVERFLOW
IN BACKUP
Indicates that a remote device is placing a call to initiate a WAN
line backup.
OUT 128K BACKUP
IN 128K BACKUP
64K LEASED LINE
128K LEASED
LINE
Last Call Disc Cause [polStatIsdnNbrLastDiscCause]
Lists the information contained in the cause field of the Cause information element. Valid values:
External Cause Codes (defined in ITU-T Q.931):
01
Unallocated number
02
No route to specified transit network
03
No route to destination
06
Channel unacceptable
07
Call awarded and being delivered in an established channel
16
Normal call clearing
17
User busy
18
No user responding
19
No answer from user (user alerted)
21
Call rejected
22
Number changed
26
Non-selected user clearing
27
Destination out of order
28
Invalid number format
29
Facility rejected
30
Response to STATUS ENQUIRY
31
Normal, unspecified
34
No circuit/channel available
IAN150/IPP MT
6/30/97
18-13
38
41
42
43
44
47
49
50
57
58
63
65
66
69
70
79
81
82
83
84
85
86
88
91
95
96
97
98
99
100
101
102
111
127
Network out of order
Temporary failure
Switching equipment congestion
Access information discarded
Request circuit/channel not available
Resources unavailable, unspecified
Quality of service unavailable
Requested facility not subscribed
Bearer capability not authorized
Bearer capability not presently
Service or option not available, unspecified
Bearer capability not implemented
Channel type not implemented
Requested facility not implemented
Only restricted digital information bearer
Service or option not implemented, unspecified
Invalid call reference value
Identified channel does not exist
A suspended call exists, but this call identity does not
Call identity in use
No call suspended
Call having the requested call identity has been cleared
Incompatible destination
Invalid transit network selection
Invalid message, unspecified
Mandatory information element is missing
Message type non-existent or not implemented
Message not compatible with call state, message type non-existent or not
implemented.
Information element non-existent or not implemented
Invalid information element contents
Message not compatible with call state
Recovery on timer expired
Protocol error, unspecified
Interworking, unspecified
Last Call Conn Time [polStatIsdnNbrLastSetupTime]
Indicates the date (in MMMDD-YY) and time (in hours:minutes:seconds) the last call to this
destination was connected.
18-14
IAN150/IPP MT
6/30/97
Last Call Disc Diag [polStatIsdnNbrLastDiscDiag]
Indicates the internal diagnostic code that corresponds to the reason that the last call to this
destination was disconnected
Internal Diagnostic Codes:
128
No B-channel available
129
No corresponding ISDN destination entry
130
Incoming/outgoing call not permitted
131
Invalid B-channel ID in the call acknowledgment
132
Receive call disconnect with invalid call reference number (CRN)
133
Receive call acknowledgment with invalid CRN
134
Disconnect the connection due to port being offline
135
Disconnect due to port interface being deactivated
136
Outgoing call request timeout
137
No acknowledgment from the internal connection manager for call request
138
Call setup message with existing CRN
139
NCP handshaking failed
140
ISDN destination table is locked due to database modification
141
Disconnect connection at user’s request
142
VN4 Called Address is too long, max. 21 digits
143
Outgoing Call cleared due to Call Collision
Last Call Disc Time [polStatIsdnNbrLastDiscTime]
Indicates the date (in MMMDD-YY) and time (in hours:minutes:seconds) the last call to this
destination was ended.
Last Call Disc Loc [polStatIsdnNbrLastDiscLocation]
Lists the information contained in the location field (octet 3) of the Cause information element.
Valid values:
0
1
2
3
4
5
7
10
IAN150/IPP MT
6/30/97
User
Private network serving the local user
Public network serving the local user
Transit network
Public network serving the remote user
Private network serving the remote user
International network
Network beyond internetworking point
18-15
ISDN Call History
The ISDN Call History screen lists the ISDN calls that have been disconnected. Each screen
displays one entry at a time; the ISDN Call History table can hold up to 16 separate entries. To
select the ISDN Call History screen, from the Main Menu, follow the path:
7. ISDN
4. Call History
or enter SIH or 174 from the command line of any menu or screen and press Enter. The system
1.7.4 [SIH] ISDN Call History
Index
001
Newest Index
00
Peer Address
Destination
Info Xfer Type
00
UNKNOWN
ISDN Number Index
B-Channel Port
00
Call Reason
Setup Time
Connect Time
NO CALL
AUG01-96 15:05:25
AUG01-96 15:05:25
Call Origin
NO CALL
Disconnect Cause
Disconnect Time
00
AUG01-96 15:05:25
Disconnect Diag
Disconnect Location
Frames
Octets
IN
0
0
00
000
000
OUT
0
0
Figure 18-5. ISDN Call History Screen
The following paragraphs describe ISDN Call History parameters. Corresponding MIB values,
where applicable, appear in brackets next to the parameter names. To view current values, refresh
the screen by entering the appropriate Index number, then type < . > R (for Read) and press
Enter. The screen displays the statistics that applied when the command was executed. To exit
the screen, press < \ > or Esc.
Index [polStatIsdnCallHistoryIndex]
Indicates the key field for a specific call history.
Newest Index [polStatIsdnCallHistoryNewestIndex]
Lists the last recorded entry in the call history table.
Peer Address [polStatIsdnCallHistoryPeerAddress]
Lists the ISDN call number of the ISDN destination.
18-16
IAN150/IPP MT
6/30/97
Destination [polStatIsdnCallHistoryNbrIndex]
Indicates the destination number of the peer as defined in the Destination parameter from the
ISDN Destination Configuration screen (2.7.2). This value, in combination with the ISDN
Number Index, defines a specific destination and associated ISDN call information.
ISDN Number Index [polStatIsdnCallHistoryAddressIndex]
Indicates the value as configured in the ISDN Number Index field from the ISDN Destination
Configuration screen (2.7.2). This value, in combination with the Destination Index, define a
specific destination and associated ISDN call information.
Info Xfer Type [polStatIsdnCallHistoryInfoType]
Describes the type of information being transmitted over this ISDN connection. Valid values:
UNKNOWN
Unknown call format.
SPEECH
Voice transmission. This option is not supported in the
current release.
UNRESTRICTED 64K
UNRESTRICTED 56K
RESTRICTED DIGITAL
AUDIO 3.1 KHZ
Audio transmission at 3.1 kilohertz. This option is not
AUDIO 7 KHZ
Audio transmission at 7 kilohertz. This option is not
VIDEO
Video transmission. This option is not supported in the
current release.
PACKET SWITCHED
Data transmitted by running X.25 over B or D channel. This
option is not supported in the current release.
B-Channel Port [polStatIsdnCallHistoryLogicalIfIndex]
Indicates the port through which the B-channel transmitted data. Valid values:
06 may use B1 or B2
07 may use B1 or B2
IAN150/IPP MT
6/30/97
18-17
Call Reason [polStatIsdnCallHistoryCallReason]
Describes the type of ISDN call. Valid values:
NO CALL
OUT TRAFFIC
OUT MANUAL
Indicates that ISDN placed a manual call.
OUT DATE TIME
OUT OVERFLOW
OUT BACKUP
Indicates that ISDN is making a call so that it can backup a WAN
line.
IN TRAFFIC
IN MANUAL
Indicates that ISDN is receiving a manual call.
IN OVERFLOW
IN BACKUP
Indicates that a remote device is placing a call to initiate a WAN
line backup.
OUT 128K BACKUP
IN 128K BACKUP
64K LEASED LINE
128K LEASED
LINE
Call Origin [polStatIsdnCallHistoryCallOrigin]
Indicates who initiated the call. Valid values:
NO CALL
Indicates no call is currently active.
ORIGINATE Indicates this device established this call with the peer.
ANSWER
Indicates this device received the call from the peer.
Setup Time [polStatIsdnCallHistorySetupTime]
Indicates the date (in MMMDD-YY) and time (in hours:minutes:seconds) that the call was
initiated.
Connect Time [polStatIsdnCallHistoryConnectTime]
Indicates the date (in MMMDD-YY) and time (in hours:minutes:seconds) that the call was
connected.
Disconnect Cause [polStatIsdnCallHistoryDisconnectCause]
Lists the information contained in the cause field of the Cause information element. Valid values:
External Cause Codes (defined in ITU-T Q.931):
01
Unallocated number
02
No route to specified transit network
03
No route to destination
06
Channel unacceptable
07
Call awarded and being delivered in an established channel
16
Normal call clearing
18-18
IAN150/IPP MT
6/30/97
17
18
19
21
22
26
27
28
29
30
31
34
38
41
42
43
44
47
49
50
57
58
63
65
66
69
70
79
81
82
83
84
85
86
88
91
95
96
97
98
99
100
101
102
111
127
IAN150/IPP MT
6/30/97
User busy
No user responding
No answer from user (user alerted)
Call rejected
Number changed
Non-selected user clearing
Destination out of order
Invalid number format
Facility rejected
Response to STATUS ENQUIRY
Normal, unspecified
No circuit/channel available
Network out of order
Temporary failure
Switching equipment congestion
Access information discarded
Request circuit/channel not available
Resources unavailable, unspecified
Quality of service unavailable
Requested facility not subscribed
Bearer capability not authorized
Bearer capability not presently
Service or option not available, unspecified
Bearer capability not implemented
Channel type not implemented
Requested facility not implemented
Only restricted digital information bearer
Service or option not implemented, unspecified
Invalid call reference value
Identified channel does not exist
A suspended call exists, but this call identify does not
Call identity in use
No call suspended
Call having the requested call identity has been cleared
Incompatible destination
Invalid transit network selection
Invalid message, unspecified
Mandatory information element is missing
Message type non-existent or not implemented
Message not compatible with call state, message type non-existent or not
implemented.
Information element non-existent or not implemented
Invalid information element contents
Message not compatible with call state
Recovery on timer expiry
Protocol error, unspecified
Interworking, unspecified
18-19
Disconnect Diag [polStatIsdnCallHistoryDisconnectDiag]
Lists the information contained in the diag field of the Cause information element. Valid values:
Internal Diagnostic Codes:
128
No B-channel available
129
No corresponding ISDN destination entry
130
Incoming/outgoing call not permitted
131
Invalid B-channel ID in the call acknowledgment
132
Receive call disconnect with invalid call reference number (CRN)
133
Receive call acknowledgment with invalid CRN
134
Disconnect the connection due to port being offline
135
Disconnect due to port interface being deactivated
136
Outgoing call request timeout
137
No acknowledgment from the internal connection manager for call request
138
Call setup message with existing CRN
139
NCP handshaking failed
140
ISDN destination table is locked due to database modification
141
Disconnect connection at user’s request
142
VN4 Called Address is too long, max. 21 digits
143
Outgoing Call cleared due to Call Collision
Disconnect Time [polStatIsdnCallHistoryDisconnectTime]
Indicates the date (in MMMDD-YY) and time (in hours:minutes:seconds) the call was ended.
Disconnect Location [polStatIsdnCallHistoryDisconnectLoc]
Lists the information contained in the location field (octet 3) of the Cause information element.
Valid values:
0
1
2
3
4
5
7
10
User
Private network serving the local user
Public network serving the local user
Transit network
Public network serving the remote user
Private network serving the remote user
International network
Network beyond internetworking point
Frames [polStatIsdnCallHistoryTransmitPackets]
[polStatIsdnCallHistoryReceivePackets]
Lists the number of frames either received or transmitted during this call. Frames IN indicates
the number of frames received. Frames OUT indicates the number of frames transmitted.
Octets [polStatIsdnCallHistoryTransmitBytes]
[polStatIsdnCallHistoryReceiveBytes]
Lists the number of bytes either received or transmitted during this call. Octets IN indicates the
number of bytes received. Octets OUT indicates the number of bytes transmitted.
18-20
IAN150/IPP MT
6/30/97
Chapter
19
Backup Monitoring
NOTE:
noted.
The IAN-150 provides statistical data and diagnostic reports to help you monitor performance
and status of a backup port. The port backup capability allows you to designate a port to act as a
standby for a set of primary entities such as ports, circuits, or DLCIs (Data Link Connection
Identifier). This chapter describes the screens and displays associated with Backup monitoring.
Refer to Chapter 19, “Backup Features,” in the Synchrony IAN-150/IPP Reference Manual for
information about backup configuration.
Backup Monitoring Tips
screen, the values in the default template appear to be set to zero. To view current values, refresh
type < . > N (for Read Next) and press Enter. Any display that contains index number fields are
functionally considered to be tables.
or Esc.
IAN150/IPP MT
6/30/97
19-1
Chapter 19, Backup Monitoring
Backup Statistics
The Backup Statistics screen displays the five backup parameters that you can monitor. These
parameters reflect the states of calls only made on the backup port. To access the Backup
Statistics screen, from the Main menu, follow the path:
1. Node Status and Control
4. Backup Statistics
or type SNB or 114 from the command line of any menu or screen and press Enter. The system
1.1.4 [SNB] Backup Statistics
No of Backup Ports on Node
00
No of calls made in Monitoring period
000
Time of Last Call
Jun27-97 12:44:31
Last Call made on Port No
000
Last Call Status
Down
Figure 19-1. Backup Statistics Screen
The following paragraphs describe parameters for Backup Statistics.
No of Backup Ports on Node [polStatBkpTotalPorts]
Indicates the total number of ports that are configured as backup ports.
No of calls made in Monitoring period [polStatBkpTotalCalls]
Indicates the total number of times the backup port has gone online during the monitoring period.
The monitoring period is calculated backward beginning from the time the system executes a
Read command or you issue a Monitor command. Note that once the backup port reaches its
maximum number of online calls during the monitoring period, the backup port will no longer go
online even if the primary port is offline. The duration of the monitoring period and maximum
number of calls are configured using the Backup Timing Configuration screen, described in
Chapter 19, “Backup Features” in the Synchrony IAN-150/IPP Reference Manual.
Time of Last Call [polStatBkpLastCallPortNo]
Indicates the time of the last call on the backup port.
Last Call made on Port No [polStatBkpLastCallPortNo]
Indicates the backup port number on which the last call was made.
Last Call Status [polStatBkpLastCallStatus]
Indicates whether the last call is still on backup or the primary entity it backups has recovered.
Valid values: Up or Down. Up indicates the primary entity has not recovered. Down indicates
the primary entity has recovered, the call has been teared down and is no longer on the backup
port.
19-2
IAN150/IPP MT
6/30/97
Appendix
A
Replacement and Upgrade Procedures
NOTE:
The information in this appendix applies to the Synchrony IAN150; however, the upgrade information contained in Procedures
A-5 and A-6 also applies to the IPP module. For replacement
procedures relating to the IPP module, see the Synchrony ST1000/ER-5 Internetworking Installation and Maintenance
Manual.
Malfunctions of networks often occur in communications lines or in equipment other than the
Ascom Timeplex Synchrony IAN-150. When the malfunction has been isolated, proceed as
follows:
•
For communication line problems, call the telephone service center directly.
•
Take appropriate action to repair or replace faulty equipment other than the IAN-150.
•
If diagnostic tests indicate a fault in the IAN-150, replace the defective expansion module,
WAN personality module (WPM), or memory upgrade device, or reinstall the software as
described in the following procedures. Do not attempt to repair parts or modules.
CAUTION:
1. Observe electrostatic device safety standards when handling
the circuit boards.
2. Replacement of the modules will result in interruption of
supported facilities. All concerned parties should be notified that
such interruption will take place.
This chapter gives the following user-level part and module replacement procedures:
•
Procedure A-1. Power OFF
•
Procedure A-2. Power ON
•
Procedure A-3. Removing and Installing Expansion Modules
•
Procedure A-4. Removing and Installing WAN Personality Modules (WPMs)
•
Procedure A-5. Upgrading Buffer Memory (DRAM)
•
Procedure A-6. Upgrading System Software
IAN150/IPP MT
6/30/97
A-1
Appendix A, Replacement and Upgrade Procedures
Procedure A-1. Power OFF
Perform this procedure to shut down the IAN-150 before removing or installing any expansion
module or WAN Personality Module (WPM), or before upgrading the buffer memory.
1. Notify all concerned parties that the IAN-150 is being shut down.
2. Set the AC power switch on the rear panel to the OFF position (0). See Figure A-1.
3. Observe that all LEDs go off.
4. Remove power from the IAN-150 by disconnecting the power cord from the AC power
source.
AC POWER
SWITCH
MODEL:
INTERFACE 5
TM
Synchrony IAN-150
BEFORE SERVICING.
AVANT L'ENTRETIEN.
SER NO.
OP
TX
RX
OP
TX
RX
INTERFACE 6
OP
TX
RX
OP
TX
RX
INTERFACE 4
OP
TX
RX
INTERFACE 3
OP
TX
RX
ETHERNET
INTERFACE 2
OP
TX
RX
TOKEN RING
INTERFACE 1
100-240VAC 1.5A
50-60Hz
INTERFACE 7
CONSOLE
AC POWER
INLET
A. AC POWER CONNECTIONS - MODELS IAN-150-001, IAN-150-002, IAN-150-003,
IAN-150-004, IAN-150-005, AND IAN-150-006
AC POWER
OUTLET
AC POWER AC POWER
SWITCH
INLET
B. AC POWER CONNECTIONS - MODELS IAN-150-011, IAN-150-012, IAN-150-013,
IAN-150-014, IAN-150-015, AND IAN-150-016
Figure A-1. IAN-150 AC Power Connections
Procedure A-2. Power ON
1. Reconnect the power cord from the AC power source to the IAN-150.
2. Set the AC power switch on the rear panel to the ON position (1). See Figure A-1.
3. On the front panel, observe that the Power LED is on and that the Run LED is blinking off
and on.
A-2
IAN150/IPP MT
6/30/97
Procedure A-3. Removing and Installing Expansion Modules
The IAN-150 is shipped with the expansion module installed as ordered. When required, use this
procedure to install an expansion module in an empty module holder, or to replace the expansion
module for maintenance or upgrade purposes. Table A-1 lists expansion modules identified by
model, printed circuit board (PCB) part number, associated physical interface connections,
module assembly part number, and expansion slot cover plate part number. Table A-1 also
provides interoperability information between the various expansion modules and the base unit
configuration models.
Table A-1. IAN-150 Expansion Modules
Model No.
PCB
Part No.
Module Description
Assembly
Part No.✤
Expansion Slot
Cover Plate Part No. ✦
IAN-EXP-01*
116230-1
2 Serial ports
116223-1

IAN-EXP-02*
116229-2
1 ISDN-BRI port
116223-2

IAN-EXP-03*
116227-1
1 Ethernet port
116223-3

IAN-EXP-04*
116228-1
1 Token Ring port
116223-4

IAN-EXP-11✝
116230-1
2 Serial ports
116223-11
XC116978A
IAN-EXP-12✝
116229-2
1 ISDN-BRI port
116223-12
XC116979A
IAN-EXP-13✝
116227-1
1 Ethernet port
116223-13
XC116977A
IAN-EXP-14✝
116228-1
1 Token Ring port
116223-14
XC116977B
* Interoperable with base unit configuration models IAN-150-001, IAN-150-002, IAN-150-003,
IAN-150-004, IAN-150-005, and IAN-150-006.
✝ Interoperable with base unit configuration models IAN-150-011, IAN-150-012, IAN-150-013,
IAN-150-014, IAN-150-015, and IAN-150-016.
✤ The assembly number includes the PCB and the expansion module slot cover plate.
✦ The expansion module slot cover plate is separately orderable for expansion modules IAN-EXP-11,
IAN-EXP-12, IAN-EXP-13, and IAN-EXP-14.
1. Remove the cable(s) from the interface connector(s) of the module being replaced. If
necessary, tag the cable(s) for later reconnection.
2. On models IAN-150-001, IAN-150-002, IAN-150-003, IAN-150-004, IAN-150-005, and
IAN-150-006, loosen and remove the two Phillips-head screws and washers from the lower
left side of the IAN-150 cover and the two Phillips-head screws and washers from the lower
right side of the IAN-150 cover (see Figure A-2A).
On models IAN-150-011, IAN-150-012, IAN-150-013, IAN-150-014, IAN-150-015, and
IAN-150-016, loosen and remove the three Phillips-head screws and washers on the rear
panel: the screw and washer located in the lower left corner, in the lower right corner, and in
the upper middle portion of the rear panel (see Figure A-2B).
3. Carefully slide the tray out of the IAN-150 chassis.
4. Place the tray on a flat, static-free surface.
5. Remove the two Phillips-head mounting screws and washers from the expansion module
faceplate; remove the two Phillips-head mounting screws and washers that secure the
expansion module to the chassis; and then detach the 96-pin connector on the expansion
module from the motherboard.
IAN150/IPP MT
6/30/97
A-3
COVER
E
OL
NS
CO
ING
NR
KE
TO
2
LOWER
SCREW
(4 REQUIRED)
CE
2
CE
3
OP
TX
RX
FA
ER
INT
OP
TX
RX
INT
OP
TX
RX
FA
ER
CE
FA
ER
INT
ET
RN
HE
ET
OP
TX
RX
OP
TX
RX
N
ISD
OP
TX
RX
OP
TX
RX
TRAY
A. TRAY REMOVAL FOR MODELS IAN-150-001, IAN-150-002, IAN-150-003,
IAN-150-004, IAN-150-005, AND IAN-150-006
TRAY
REAR
PANEL
LOWER
RIGHT SCREW
UPPER
MIDDLE SCREW
LOWER
LEFT SCREW
B. TRAY REMOVAL FOR MODELS IAN-150-011, IAN-150-012, IAN-150-013,
IAN-150-014, IAN-150-015, AND IAN-150-016
Figure A-2. IAN-150 Tray Removal from Chassis
A-4
IAN150/IPP MT
6/30/97
IAN-150-006:
•
For expansion module Part No. 116230-1, slide the module out of its slot through the
rear panel opening and set the module aside.
•
For expansion module Part No. 116227-1, 116228-1, or 116229-2, lift the module
vertically out of the tray and set the module aside.
IAN-150-016:
•
For expansion module Part No. 116230-1, slide the module out of its slot through the
front panel opening and set the module aside.
•
For expansion module Part No. 116227-1, 116228-1, or 116229-2, lift the module
vertically out of the tray and set the module aside.
7. Remove the replacement expansion module and extra faceplate from the anti-static bag.
CAUTION:
Be sure to observe standard anti-static procedures (ensure
proper grounding, wear a wrist strap, etc.) when handling the
interface module.
8. If removing the WAN Personality Module (WPM) from its place on a serial expansion
module:
A. Follow Steps 1–6 above to remove the expansion module from the IAN-150 chassis.
B. Place the expansion module on a flat surface, with the module’s interface connectors
positioned on your right.
C. With your fingers, gently push the two guides holding the WPM in place away from the
WPM. When the guides no longer restrain it, the WPM will pop out of its holder.
D. When the WPM is clear of the guides, pick it up by the edges and remove it completely
from the holder. Be sure not to pick it up by the side that actually goes into the WPM
holder (the side with the tin-lead card edge connectors and the two notches).
E. Store the WPM in a cool, dry location away from static electricity.
9. If installing a WPM onto a serial expansion module:
A. Remove the WPM from the anti-static bag.
B. With the expansion module on a flat surface and the module’s interface connectors
positioned on your right, pick up the WPM by holding the short edges. Make sure the
tin-lead card edge connectors are on the bottom and the notched corner is positioned on
the left (see Figure A-3). The notched corner of the WPM must be in the lower left
corner; the WPM will not install if the notched corner is in the lower right corner.
C. Hold the WPM at about a 40-degree angle and gently push the side with the tin-lead card
edge connectors into the WPM holder on top of the guides. The WPM will go into the
holder just enough to cover the connectors.
D. Gently press on the left and right sides of the top edge of the WPM. This will push back
the guides. The posts on the WPM holder will show through the holes in the WPM and
the guides will snap back into place, locking the WPM in its holder.
IAN150/IPP MT
6/30/97
A-5
WAN PERSONALITY
MODULE (WPM)
Figure A-3. WAN Personality Module Replacement on IAN-150 Expansion Module
IAN-150-006:
•
For expansion module Part No. 116230-1, slide the module into its slot through the rear
panel opening of the tray and secure it to the motherboard with the 96-pin connector and
the two Phillips-head mounting screws and washers that secure the module to the
chassis. Attach the faceplate to the expansion module with the four cable locking screws.
•
For expansion module Part No. 116227-1, 116228-1, or 116229-2, place the module into
position from the top of the tray and secure it to the motherboard with the 96-pin
connector and two Phillips-head mounting screws and washers.
IAN-150-016:
•
For expansion module Part No. 116230-1, slide the module into its slot through the front
panel opening of the tray and secure it to the motherboard with the 96-pin connector and
the two Phillips-head mounting screws and washers that secure the module to the
chassis. Attach the faceplate to the expansion module with the four cable locking screws.
•
For expansion module Part No. 116227-1, 116228-1, or 116229-2, place the module into
position from the top of the tray and secure it to the motherboard with the 96-pin
connector and two Phillips-head mounting screws and washers.
IAN-150-006, secure the faceplate to the rear panel with two Phillips-head mounting screws
and washers.
IAN-150-016, secure the faceplate to the front panel with two Phillips-head mounting screws
and washers.
A-6
IAN150/IPP MT
6/30/97
12. Carefully slide the tray into the IAN-150 chassis.
IAN-150-006, secure the two Phillips-head screws and washers on the lower left side of the
IAN-150 cover and the two Phillips-head screws and washers on the lower right side of the
IAN-150 cover.
IAN-150-016, attach the IAN-150 cover to the rear panel by securing the Phillips-head screw
and washer on the lower left side, the upper middle portion, and the lower right side of the
IAN-150 cover.
14. Reconnect the interface cables.
Procedure A-4. Removing and Installing WAN Personality Modules
(WPMs)
When required, use this procedure to remove or install WAN Personality Modules (WPMs) that
have been preinstalled on the motherboard in the IAN-150. The following table lists the IAN-150
WPMs and their part numbers.
Table A-2. IAN-150 WAN Personality Modules (WPMs)
Description
Part No.
V.11
100268-1
V.28 DTE
100255-1
V.28 DCE
100267-1
V.35
100257-1
MIL-STD-188-114A
100258-2
1. Follow Steps 1–4 in Procedure A-3 above to remove the tray from the IAN-150 chassis.
2. To remove a WPM currently installed on the motherboard:
A. Place the IAN-150 tray on a flat surface with the physical ports facing you.
B. With your fingers, gently push the two guides holding the WPM in place away from the
WPM. When the guides no longer restrain it, the WPM will pop out of its holder.
C. When the WPM is clear of the guides, pick it up by the short edges and remove it
completely from the holder. Be sure not to pick it up by the side that actually goes into
the WPM holder (the side with the tin-lead connectors and the two notches).
D. Store the WPM in a cool, dry location away from static electricity.
3. To install a WPM onto the motherboard:
A. Remove the WPM from the anti-static bag.
CAUTION:
Be sure to observe standard anti-static procedures (ensure
proper grounding, wear a wrist strap, and so on) when handling
the WPM and the motherboard.
B. Place the IAN-150 tray on a flat surface with the physical ports facing you.
IAN150/IPP MT
6/30/97
A-7
C. Pick up the WPM by the left- and right-side edges with the notched corner positioned on
the lower left side (see Figure A-4). The notched corner of the WPM must be in the
lower left corner; the WPM will not install if the notched corner is in the lower right
corner.
D. Hold the WPM at about a 40-degree angle and gently push the tin-lead connector edge of
the WPM into the holder on top of the guides. The WPM will go into the holder just
enough to cover the tin-lead connectors.
E. Gently press on the left and right sides of the top edge of the WPM. This will push back
the guides. The posts on the WPM holder will show through the holes in the WPM and
the guides will snap back into place, locking the WPM in its holder.
4. Follow Steps 12–14 of Procedure A-3 above to replace the tray into the IAN-150 chassis.
PORT 5
PORT 4
PORT 3
WAN PERSONALTY
MODULE (WPM)
MOTHERBOARD
Figure A-4. WAN Personality Module Replacement on the IAN-150 Motherboard
A-8
IAN150/IPP MT
6/30/97
Procedure A-5. Upgrading Buffer Memory (DRAM)
IAN-150 Only
The IAN-150 motherboard is shipped from the factory with 2 MB of dynamic RAM (DRAM)
soldered to the motherboard (see Figure A-5). A single SIMM socket is available for DRAM
expansion. A 4-MB SIMM will increase the total DRAM to 6 MB; an 8-MB SIMM will increase
the total DRAM to 10 MB; a 16-MB SIMM will increase the total DRAM to 16 MB (the
maximum addressable memory is 16 MB).
To upgrade the buffer memory in the IAN-150, perform the following steps:
1. Power off the IAN-150 according to Procedure A-1.
2. Remove the tray from the IAN-150 as described in Steps 1–4 of Procedure A-3.
3. If an already installed SIMM device is to be replaced, remove the SIMM device from the
SIMM socket.
4. If a 4-MB expansion is being installed, locate one SIMM device (part number
IC561360-02Z) and install it into the 72-pin expansion DRAM SIMM socket (see Figure
A-5). Ensure the SIMM device is firmly seated in the socket and locking ears secure the
device.
CAUTION:
SIMM pins must be gold-plated.
5. If an 8-MB expansion is being installed, locate one SIMM device (part number
IC562360-02Z) and install it into the 72-pin expansion DRAM SIMM socket. Ensure the
SIMM device is firmly seated in the socket and locking ears secure the device.
CAUTION:
6. If a 16-MB expansion is being installed, locate one SIMM device (part number IC56432002Z) and install it into the 72-pin expansion DRAM SIMM socket. Ensure the SIMM device
is firmly seated in the socket and locking ears secure the device.
CAUTION:
7. Replace the IAN-150 tray according to Steps 12–14 of Procedure A-3.
IAN150/IPP MT
6/30/97
A-9
DRAM SIMM
TOTAL BASE DRAM
OF 2 MEGABYTES
MOTHERBOARD
Figure A-5. Buffer Memory (DRAM) Upgrade in the IAN-150
IPP Only
The IPP is shipped from the factory with a customer-specified configuration of 4, 8, or 16 MB of
dynamic RAM (DRAM) (see Figure A-6). Available DRAM part numbers are:
Description
4 MB DRAM SIMM
8 MB DRAM SIMM
16 MB DRAM SIMM
DRAM SIMM Part Number
IC561360-03Z
IC562360-03Z
IC564360-03Z
A single SIMM socket is provided for DRAM support. To upgrade (or replace) buffer memory in
the IPP, replace the existing DRAM SIMM as follows:
1. Remove the IPP module from the ST-1000 or ER-5.
2. Remove the existing SIMM device from the SIMM socket.
3. Install the new SIMM device into the 72-pin DRAM SIMM socket (see Figure A-6). Ensure
the SIMM device is firmly seated in the socket and locking ears secure the device.
CAUTION:
4. Install the IPP module into the ST-1000 or ER-5.
A-10
IAN150/IPP MT
6/30/97
DRAM
SIMM
P
C
P1
P8
P7
P6
R
P4
P3
P2
R
O
X TX P
P1
R
PW
R DIA FA
U
N G IL
P
IP
PORT 4
PORT 3
PORT 2
PORT 1
O
X TX P
P5
-4
P5
-8
PORT 8
PORT 7
PORT 6
PORT 5
Figure A-6. Buffer Memory (DRAM) Upgrade in the IPP
Procedure A-6. Upgrading System Software
The IAN-150 and the IPP can be upgraded with a new version of system software in two ways:
(1) using the TALK program running on a DOS-based computer connected to the console port, or
(2) using TFTP and the user interface loader utility. This procedure gives instructions for loading
software using TALK. For information on loading system software using TFTP, see Loader
Utility in Chapter 5 of this manual.
NOTE:
The TALK program should not be invoked in Microsoft Windows
to execute IAN-150 load, save or restore operations. In addition,
the Advanced Power Management (APM) feature of laptop PCs
may cause problems for disk access operations initiated by TALK.
To load system software over the console port using TALK, perform the following steps:
1. Attach a computer to the console port on the IAN-150 (see Procedure 2-5. Connecting a
Terminal or Computer to the Console Port in Chapter 2, “Getting Started”).
2. Power on the computer and ensure that the DOS prompt is displayed.
3. Insert the system software diskette into a 3-1/2 inch floppy disk drive of the PC.
4. Create a new subdirectory for the system software (for example, if you are upgrading an
IAN-150, you might create the following subdirectory: C:\IAN_150).
IAN150/IPP MT
6/30/97
A-11
5. Copy all the files from the system software diskette to the subdirectory you have created.
(For example, at the A:\ prompt, type copy *.* C:\ian_150 and press Enter. This will copy
all of the system files and the TALK program into the new subdirectory.)
6. Once the system files have been copied to the C: drive on your computer, go to the
subdirectory where the files are located and find the name of the master file. (The master file
is the file that has no extension.) You will need to remember this filename in order to
perform the TALK load. Now type talk and press Enter. The TALK program banner (see
Figure A-7) will appear at the bottom of the computer screen.
___________________________________________________________________________
Talk v5.2 Copyright (c)1993-1996 ascom Timeplex Press F1 for help
COM1
Figure A-7. TALK Program Banner
7. Make sure the COM ports are at the same connection: COM 1 or COM 2. Toggle the active
COM port by pressing F6 and then pressing Enter to display the banner.
8. Power-cycle the IAN-150 by setting the power switch at the rear of the IAN-150 to OFF,
then ON. The screen clears. When the message
appears, press Esc twice. The system displays the Loader menu (see Figure A-8).
(c)1996-1997 ascom Timeplex Loader
IAN 150 Version 1.0.2 Jun 26 1997
=========================================================
TALK File Transfer
Baud rate:
115200
=========================================================
(T) Start TALK load
(S) Save system configuration to file
(F) Factory test
(M) Mon960 menu
Main>
Figure A-8. IAN-150 Loader Menu
A-12
IAN150/IPP MT
6/30/97
NOTE:
The baud rate for the TALK program must match the baud rate
selected from the Loader menu. The default baud rate for TALK is
38400 bps.
9. If you wish to change the Loader baud rate, press c. The system displays the following
screen:
Talk current baud rate: 115200
--------------------------------------------------------Valid Baud Rates
1)
1200
2)
2400
3)
4800
4)
9600
5)
19200
6)
28800
7)
38400
8)
57600
9)
76800
10)
115200
--------------------------------------------------------Enter baud rate (or menu number):
Figure A-9. TALK Baud Rate Configuration Screen
10. You can change the Loader baud rate by typing the new baud rate or by typing the menu
number corresponding to the new baud rate, then pressing Enter. The Loader menu will be
redisplayed with the new baud rate indicated at the top of the menu as the current baud rate.
NOTE:
To change the TALK baud rate, press F3. The cursor appears
next to the current baud rate. Use the UP or DOWN arrow keys to
select a new baud rate and press Enter.
11. From the Loader menu prompt, press t to start loading system software using TALK. The
message Ready to receive program file. will be displayed.
12. Press F5. The prompt send filename: will appear in reverse video at the bottom of
your screen.
13. Type the path and filename of the master file and press Enter. The name of each system file
will be displayed as it is loaded into Flash memory. When the file transfer is complete, a
message will appear indicating whether or not a valid checksum was calculated, and the
Loader menu will be displayed again.
14. Press u to unzip the system files and to copy them from the storage section of Flash memory
to Execution Flash. Wait for the Loader menu to redisplay.
15. Press g to start executing Flash. The message
will be displayed. After about 30 seconds, the IAN-150 title screen will be displayed.
16. After the IAN-150 title screen appears, press Enter to display the login prompt. For
information on user access levels and passwords, see User Access Levels in Chapter 2,
“Getting Started.”
IAN150/IPP MT
6/30/97
A-13
Loader Menu Options
The Loader menu provides other functions not already mentioned in the specific procedures
above. These additional functions are described in the paragraphs below.
This option returns all user-configurable IAN-150 configuration parameters to their factory
default values, including MAC addresses, board revision level and board serial number. A
confirmation prompt asks you if you are sure you want to default the entire unit. It is
recommended that before selecting this option, you select (S) Save system configuration to file
and save your current configuration settings.
This option enables you to save the current configuration database information to a disk file for
possible later retrieval.
To save system configuration to a file, perform the following steps:
1. At the Main> prompt, type s and press Enter. The system displays two additional options on
the Loader menu.
IAN 150 Version 1.0.2 Jun 26 1997
=========================================================
TALK File Transfer
Baud rate:
115200
=========================================================
(T) Start TALK load
(F) Factory test
(M) Mon960 menu
Main> s
T) Upload Configuration via console (TALK)
F) Save Configuration to flash
2. Press ALT + F5. The system displays the Upload filename: prompt.
NOTE:
You must press ALT + F5 and enter a path and filename at the
TALK prompt. Otherwise, the configuration information is
“saved” only to the user interface screen.
3. At the Upload filename: prompt, type the filename and press Enter. The system displays the
message Read to upload into file “xxxxx.xxx”.
A-14
IAN150/IPP MT
6/30/97
4. At the Option> prompt, type t and press Enter. The system displays the message Begun
uploading bbram data.
This option enables you to restore configuration database information from a disk file to the nonvolatile memory (NVM) of an IAN-150.
To restore system configuration from a file, perform the following steps:
1. At the Main> prompt, type r and press Enter. The system displays two additional options on
the Loader menu.
IAN 150 Version 1.0.2 Jun 26 1997
=========================================================
TALK File Transfer
Baud rate:
115200
=========================================================
(T) Start TALK load
(F) Factory test
(M) Mon960 menu
Main> r
T) Download Configuration via console (TALK)
F) Restore Configuration from flash
Option>
2. At the Option> prompt, type t and press Enter. The system displays the message Ready to
receive configuration file.
3. Press F5. The system displays the Send filename: prompt.
4. Type the filename and press Enter. The system displays the message Sending
“filename”.
When the transmission is complete, the system displays the message Received data length =
xxxxxxx.
5. At the Enter in Configuration name (unix-filename): prompt, type the filename and press
Enter. The system displays the message Configuration saved into NVM.
IAN150/IPP MT
6/30/97
A-15
When you select this option, the system displays the names and sizes of all of the IAN-150
system files. An example is shown below.
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
File
(0): "ian1_040." 0xe0020009 291
(1): "ian1_040.1" 0xe0020139 38433
(2): "ian1_040.2" 0xe0029765 36861
(3): "ian1_040.3" 0xe003276d 49973
(4): "ian1_040.4" 0xe003eaad 48754
(5): "ian1_040.5" 0xe004a929 51379
(6): "ian1_040.6" 0xe00571e9 51119
(7): "ian1_040.7" 0xe00639a5 41481
(8): "ian1_040.8" 0xe006dbb9 58360
(9): "ian1_040.9" 0xe007bfbd 48462
(10): "ian1_040.10" 0xe0087d15 47968
(11): "ian1_040.11" 0xe0093881 49946
(12): "ian1_040.12" 0xe009fba5 49114
(13): "ian1_040.13" 0xe00abb89 52629
(14): "ian1_040.14" 0xe00b8929 48810
(15): "ian1_040.15" 0xe00c47dd 37893
(16): "ian1_040.16" 0xe00cdbed 55466
(17): "ian1_040.17" 0xe00db4a1 64095
(18): "ian1_040.18" 0xe00eaf0d 56238
(19): "ian1_040.19" 0xc0340009 55406
(20): "ian1_040.20" 0xc034d881 41807
(21): "ian1_040.21" 0xc0357bdd 25240
(22): "ian1_040.22" 0xc035de81 30770
(23): "ian1_040.23" 0xc03656bd 33817
Figure A-12. IAN-150 Operating System Files (Flash Files)
The list contains the name of each file, the memory location where the file begins, and the size of
the file in bytes.
When you select this option, the system displays the following menu:
Board Rev Number:
Serial Number:
cccc
66666
--------------------------------------------------------M)
I)
B)
S)
X)
Edit
Edit
Edit
Save
Exit
port MAC address
serial id
board rev number
this information to Flash
to main menu
EditInfo>
Figure A-13. Edit Board Information Menu for the IAN-150
This menu allows you to manually edit the serial number and/or revision level of the IAN-150
motherboard, or to change the factory-assigned MAC addresses of the Token Ring, Ethernet, and
expansion module serial ports.
A-16
IAN150/IPP MT
6/30/97
If you select M) Edit port MAC address, the system displays the following screen:
Mac Set:
ETHERNET (0)
Mac Address:
08:00:0b:3d:22:22
Mac Set:
Mac Address:
EXT PORT 1 (1)
08:00:0b:3d:99:99
Mac Set:
Mac Address:
EXT PORT 2 (2)
50:6e:06:d9:84:fb
Mac Set:
TOKEN RING (3)
Mac Address:
08:00:0b:3d:11:11
--------------------------------------------------------0)
1)
2)
3)
Edit
Edit
Edit
Edit
Ethernet mac address
Extension Port 1 mac address
Extension Port 2 mac address
Token Ring mac address
--------------------------------------------------------X) Exit to Main Menu
EditMac>
Figure A-14. Edit Port MAC Address Screen
Select the port whose MAC address you wish to change. Enter the new MAC address at the
prompt. Be sure to type a colon in between each pair of hex values. If an incorrect address is
entered, an error message will be displayed. If a properly formatted MAC address is entered, the
edit screen will be redisplayed with the new address in place. Type x and press Enter to return to
the Loader menu.
(F) Factory test
This option is described in Factory Diagnostics in Chapter 6 of this manual.
This option accomplishes the same thing as option G on the Loader menu.
(M) Mon960 menu
This option provides access to the user interface of the Intel i960 processor.
CAUTION:
IAN150/IPP MT
6/30/97
Do not use this option unless you are a qualified developer or
Customer Support representative!
A-17
Appendix
B
Cables
NOTE:
The information in this appendix refers only to Synchrony
IAN-150 cables. For IPP cable information, see the Synchrony
ST-1000/ER-5 Internetworking Installation and Maintenance
Manual.
This appendix provides information on cables used with the Synchrony IAN-150, including:
•
An index of cables (Table B-1)
•
Cable wiring diagrams (Figures B-1 through B-13)
Table B-1. IAN-150 Cable Index
Part Number*
Cable Name
Connectors
Figure
Description
100543-1 to -5
V35V35CM
25-pin Male 34-pin Male
B-6A
V.35 interface to V.35 DCE device
100547-1 to -4
V35DTEM
B-7A
V.35 interface to V.35 DTE device
100831-1 to -4
V35DTEF
25-pin Male 34-pin Female
B-7B
100832-1 to -4
V35V35CF
B-6B
100895-1 to -4
V28V28FM
B-11A
V.28 interface to V.28 flow control
DTE
100896-1 to -5
V28V28TM
B-11F
V.28 interface to V.28 symmetrical
DTE
100898-1 to -5
V28V54CM
B-10A
V.28 interface to V.28/V.54 DCE
interface
100912-1 to -4
V28V28TF
B-11F
DTE
100918-1 to -4
V28V28C
B-10B
V.28 interface to V.28 DCE interface
100919-1 to -4
V35V54CM
B-6C
(with OT1, OT2, TI)
100967-1 to -4†
V28DTEM
B-11C
V.28 interface to DTE devices where
EIA flow control is not required (e.g.,
SDLC)
100968-1 to -4
V28DTEF
B-11D
SDLC)
IAN150MT
6//30/97
B-1
Appendix B, Cables
Table B-1. IAN-150 Cable Index (Cont’d)
Part Number*
Cable Name
Connectors
Figure
Description
100968-1 to -4
V28DTEF
B-11D
SDLC)
116575
TL449TF
B-13A
IAN-150 to EIA RS-449 (MIL-STD188-114A) Cable Wiring (See Note 1)
116576
TL449CM
B-13B
IAN-150 to EIA RS-449 (MIL-STD188-114A) Cable Wiring (See Note 1)
612260-1 to -2
BNP/ISDN
B-12
ISDN BRI LIU to ISDN U-interface
612269-1 to -4
V.11/M-DCE/M
B-4
V.11 balanced interface to balanced
V.11 DCE device (See Note 2)
612270-1 to -4
V.11-DCE/X.21/M
B-9
V.11 interface to X.21 DCE device
612271-1 to -4
V.28/DCE/MV.28/DTE/M
B-11B
612272-1 to -4
V.28/DCE/MV.28/DTE/SYM/M
B-11E
DTE
612273-1 to -4
V.11/M-V.11/M
B-5A
V.11 balanced interface to balanced
V.11 DTE device
612274-1 to -4
V.11/M-V.11/DTE/M
B-5B
B-2A
IEEE 802.3 Ethernet 10BASE-T
interface to Ethernet hub
B-3
IEEE 802.5 Token Ring interface to
unshielded twisted pair (UTP)
multistation access unit (MAU)
COMATPX1013
B-2
COMATPX1062
B-2B
IEEE 802.3 Ethernet 10BASE-T
interface to Ethernet interface
(crossover cable)
COMATPX1160
‡
8-pin Female 9-pin Female
B-1A
Console port: RJ45 to female DB9
adapter
COMATPX1161
‡
8-pin Female 25-pin Female
B-1D
Console port: RJ45 to female DB25
adapter
COMATPX1178
‡
8-pin Female 9-pin Male
B-1C
Console port: RJ45 to male DB9
adapter
COMATPX1179
‡
8-pin Female 25-pin Male
B-1B
Console port: RJ45 to male DB25
adapter
ZZ97527B
B-1
Console port to COMATPX adapter
IAN150/IPP MT
6/30/97
Appendix B, Cables
Table B-1. IAN-150 Cable Index (Cont’d)
NOTE 1:
NOTE 2:
Cable number 116575 and 116576 may be used in V.11 applications where terminal timing (TT) is
required.
Cable number 612269 may be used in RS449/MIL-STD-188-114A applications where TT is not
required.
* Cable length is indicated by a suffix in the part number. For part numbers that begin with ZZ, the following
suffixes are used:
A = 6 ft
D = 50 ft
X=6m
B = 15 ft
V = 30 m
Y=3m
C = 30 ft
W = 15 m
Z=1m
For all other part numbers, the following suffixes are used:
-1 = 6 ft
-4 = 50 ft
-2 = 15 ft
-5 = a special length
-3 = 31 ft
† The V28DTEM (Part No. 100967) cable also can be used to connect an IAN-150 V.28 interface to IAN-150
V.28 interface.
‡ Console port connections require both a cable and adapter. While the cable (Part No. ZZ97527B) is
common to all four combinations, the choice of adapter depends on the type of DTE/DCE equipment. All
four adapters have a female RJ45 socket for the cable connection, but the DCE/DTE end varies in gender
and pin configuration.
NOTE: All cables are constructed using low capacitance, shielded wiring.
- Connectors require conductive hoods.
- Where appropriate, cable shield is connected to conductive hood and metallic body of connector.
- DTE/DCE 25-pin connectors are DB25S or DB25P; 34-pin connectors are Winchester TMRAC 34P-JTDH8CF, or TMRAC 34S-JTDH8-CF; 37-pin connectors are DB37P or DB37S.
IAN150/IPP MT
6/30/97
B-3
Appendix B, Cables
Interpreting Cable Wiring Diagrams
The drawing below shows a typical cable diagram and describes the symbols used.
CONNECTOR
LABEL (A)
SHIELD
TWISTED
PAIR OF
WIRES
CONNECTOR
LABEL (B)
TYPE OF EQUIPMENT
ATTACHED TO CONNECTOR
ATTACHMENT TO
ASCOM TIMEPLEX
ROUTER
CONNECTION TO
CONNECTOR SHELL
OR CLAMP
PIN DESIGNATIONS
ON CONNECTOR
MALE CONNECTOR
SYMBOL
NUMBER OF PINS
ON CONNECTOR
CONNECTOR A:
TO
INTERFACE MODULE
CONNECTOR B:
TO
V.35 DCE
A
P
S
R
T
B
E
H
C
D
F
Y
a
V
X
1
11
2
3
12
7
6
20
4
5
8
15
25
17
18
101 SHIELD
103 TXDATA A
103 TXDATA B
104 RXDATA A
104 RXDATA B
102 SIGNAL GND
107 DSR
108.2 DTR
105 RTS
106 CTS
109 DCD
114 TXCLK A
114 TXCLK B
115 RXCLK A
115 RXCLK B
34
25
A. TLV35CF (116581) CABLE
CABLE NAME
B-4
SIGNAL DESIGNATIONS
(INCLUDES ITU-T
CIRCUIT NUMBER
WHERE APPLICABLE)
NUMBER OF SOCKETS
ON CONNECTOR
FEMALE
CONNECTOR
SYMBOL
ASCOM TIMEPLEX
PART NUMBER
(DOES NOT INCLUDE SUFFIX
THAT INDICATES LENGTH)
IAN150/IPP MT
6/30/97
RJ45:
TO CONSOLE PORT
DTR
TXD
RXD
RTS
CTS
DSR
GND
N/C
Appendix B, Cables
RJ45:
TO ADAPTER
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
8
8
RJ45:
TO CABLE
DTR
TXD
RXD
RTS
CTS
DSR
GND
ZZ97527B CABLE
DB9:
TO PC OR TERMINAL
1
2
3
4
5
6
7
6
2
3
8
7
4
5
8
9
DSR
RXD
TXD
CTS
RTS
DTR
GND
COMATPX1160 ADAPTER
A. RJ45 TO FEMALE DB9 ADAPTER (WITH CABLE)
RJ45:
TO CONSOLE PORT
DTR
TXD
RXD
RTS
CTS
DSR
GND
N/C
RJ45:
TO ADAPTER
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
8
8
ZZ97527B CABLE
RJ45:
TO CABLE
DTR
TXD
RXD
RTS
CTS
DSR
GND
FRAME
DB25:
TO PC OR TERMINAL
1
2
3
4
5
6
7
8
8
20
2
3
4
5
6
7
8
DTR
TXD
RXD
RTS
CTS
DSR
GND
FRAME
25
COMATPX1179 ADAPTER
B. RJ45 TO MALE DB25 ADAPTER (WITH CABLE)
Figure B-1. Console Port Cable Wiring (Sheet 1 of 2)
IAN150/IPP MT
6/30/97
B-5
Appendix B, Cables
RJ45:
TO CONSOLE PORT
DTR
TXD
RXD
RTS
CTS
DSR
GND
N/C
RJ45:
TO ADAPTER
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
8
8
RJ45:
TO CABLE
DTR
TXD
RXD
RTS
CTS
DSR
GND
FRAME
DB9:
TO MODEM OR DCE
1
2
3
4
5
6
7
8
4
3
2
7
8
6
5
8
ZZ97527B CABLE
DTR
TXD
RXD
RTS
CTS
DSR
GND
9
COMATPX1178 ADAPTER
C. RJ45 TO MALE DB9 ADAPTER (WITH CABLE)
RJ45:
TO CONSOLE PORT
DTR
TXD
RXD
RTS
CTS
DSR
GND
N/C
RJ45:
TO ADAPTER
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
8
8
ZZ97527B CABLE
RJ45:
TO CABLE
DTR
TXD
RXD
RTS
CTS
DSR
GND
DB25:
TO MODEM OR DCE
1
2
3
4
5
6
7
6
3
2
5
4
20
7
8
25
DSR
RXD
TXD
CTS
RTS
DTR
GND
COMATPX1161 ADAPTER
D. RJ45 TO FEMALE DB25 ADAPTER (WITH CABLE)
Figure B-1. Console Port Cable Wiring (Sheet 2 of 2)
B-6
IAN150/IPP MT
6/30/97
Appendix B, Cables
RJ45:
TO PORT
RJ45:
TO HUB
1
2
3
6
4
5
7
8
1
2
3
6
4
5
7
8
8
8
UXMTB
UXMTA
URCVB
URCVA
N/C
N/C
N/C
N/C
UXMTB
UXMTA
URCVB
URCVA
N/C
N/C
N/C
N/C
A. 10BASE-T CABLE
COMATPX1013
RJ45:
TO ETHERNET
PORT
RJ45:
TO ETHERNET
PORT
1
2
3
6
4
5
7
8
3
6
1
2
4
5
7
8
8
8
UXMTB
UXMTA
URCVB
URCVA
N/C
N/C
N/C
N/C
URCVB
URCVA
UXMTB
UXMTA
N/C
N/C
N/C
N/C
B. 10BASE-T CROSSOVER CABLE
COMATPX1062
Figure B-2. IEEE 802.3 Ethernet II Cable Wiring
IAN150/IPP MT
6/30/97
B-7
Appendix B, Cables
N/C
N/C
UXMTA
UXMTB
URCVB
URCVA
N/C
N/C
RJ45:
TO PORT
RJ45:
TO MULTISTATION
ACCESS UNIT
(MAU)
1
2
3
6
4
5
7
8
1
2
3
6
4
5
7
8
8
8
N/C
N/C
UXMTA
UXMTB
URCVB
URCVA
N/C
N/C
TOKEN RING CABLE
COMATPX1013
Figure B-3. IEEE 802.5 Token Ring Cable Wiring
B-8
IAN150/IPP MT
6/30/97
Appendix B, Cables
CONNECTOR A:
TO INTERFACE (DTE)
CONNECTOR B:
TO V.11 DCE
1
2
11
3
12
5
10
6
19
8
14
15
25
17
18
20
21
22
7
4
9
23
1
4
22
6
24
9
27
11
29
13
31
5
23
8
26
12
30
14
20
19
37
7
25
10
25
37
SHIELD
TXDA
TXDB
RXDA
RXDB
CTSA
CTSB
DSRA
DSRB
RLSDA
RLSDB
TSEA
TSEB
RSEA
RSEB
DTRA
DTRB
OT2
SG2
SG1
SG0
RTSA
RTSB
OT1
V.11/M-DCE/M (612269) CABLE
Figure B-4. IAN-150 to V.11 DCE Cable Wiring
IAN150/IPP MT
6/30/97
B-9
Appendix B, Cables
CONNECTOR A:
TO INTERFACE (DTE)
SHIELD
TXDA
TXDB
RXDA
RXDB
RTSA
CTSA
RLSDA
SG2
SG1
DSRA
DTRA
TSEA
TSEB
TSEA
TSEB
RSEA
RSEB
DCDB
RTSB
CTSB
DTRB
DSRB
CONNECTOR B:
TO V.11 DTE
1
2
11
3
12
4
5
8
7
13
6
20
24
16
15
25
17
18
14
9
10
21
19
1
3
12
2
11
8
4
5
13
7
20
6
15
25
17
18
24
16
9
10
14
19
21
25
25
SHIELD
RXDA
RXDB
TXDA
TXDB
RLSDA
RTSA
CTSA
SG1
SG2
DTRA
DSRA
TSEA (DCE SOURCE)
TSEB (DCE SOURCE)
RSEA
RSEB
TSEA (DTE SOURCE)
TSEB (DTE SOURCE)
RTSB
CTSB
DCDB
DSRB
DTRB
A. V.11/M-V.11/M (612273) CABLE
CONNECTOR A:
TO INTERFACE (DTE)
CONNECTOR B:
TO V.11 DTE
1
2
11
3
12
1
6
24
4
22
31
27
9
13
29
11
SHIELD
RXDA
RXDB
TXDA
TXDB
RLSDB
CTSB
CTSA
RLSDA
DSRB
DSRA
30
12
25
7
26
23
5
8
37
20
DTRB
DTRA
RTSB
RTSA
RSEB
TSEB
TSEA
RSEA
SG0
SG1
9
4
10
21
20
5
19
6
14
8
18
16
24
17
7
13
25
37
B. V.11/M-V.11/DTE/M (612274) CABLE
Figure B-5. IAN-150 to V.11 DTE Cable Wiring
B-10
IAN150/IPP MT
6/30/97
Appendix B, Cables
CONNECTOR A:
TO INTERFACE (DTE)
CONNECTOR B:
TO V.35 DCE
1
2
11
3
12
4
6
7
13
5
15
25
17
18
20
8
A
P
S
R
T
C
E
B
SHIELD
TXDA
TXDB
RXDA
RXDB
RTS
DSR
SG
D
Y
AA
V
X
H
F
CTS
TSEA
TSEB
RSEA
RSEB
DTR
RLSD
25
34
A. V35V35CM (100543) CABLE
CONNECTOR A:
TO INTERFACE (DTE)
CONNECTOR B:
TO V.35 DCE
1
2
11
3
12
4
6
7
13
5
15
25
17
18
20
8
A
P
S
R
T
C
E
B
SHIELD
TXDA
TXDB
RXDA
RXDB
RTS
DSR
SG
D
Y
AA
V
X
H
F
CTS
TSEA
TSEB
RSEA
RSEB
DTR
RLSD
25
34
B. V35V35CF (100832) CABLE
Figure B-6. IAN-150 to V.35 DCE Cable Wiring (Sheet 1 of 2)
IAN150/IPP MT
6/30/97
B-11
Appendix B, Cables
CONNECTOR A:
TO INTERFACE (DTE)
CONNECTOR B:
TO V.35/V.54 DCE
1
2
11
3
12
4
6
7
13
8
15
25
17
18
5
21
23
22
A
P
S
R
T
C
E
B
SHIELD
TXDA
TXDB
RXDA
RXDB
RTS
DSR
SG
F
Y
AA
V
X
D
N
L
NN
RLSD
TSEA
TSEB
RSEA
RSEB
CTS
OT2
OT1
TI
25
34
C. V35V54CM (100919) CABLE
Figure B-6. IAN-150 to V.35 DCE Cable Wiring (Sheet 2 of 2)
B-12
IAN150/IPP MT
6/30/97
Appendix B, Cables
CONNECTOR A:
TO INTERFACE (DCE)
CONNECTOR B:
TO V.35 DTE
1
2
11
3
12
4
5
20
8
7
13
24
16
19
14
6
A
R
T
P
S
D
F
E
C
B
SHIELD
RXDA
RXDB
TXDA
TXDB
CTS
RLSD
DSR
RTS
SG
Y
AA
V
X
H
TSEA
TSEB
RSEA
RSEB
DTR
25
34
A. V35DTEM (100547) CABLE
CONNECTOR A:
TO INTERFACE (DCE)
CONNECTOR B:
TO V.35 DTE
1
2
11
3
12
4
5
20
8
7
13
24
16
19
14
6
A
R
T
P
S
D
F
E
C
B
SHIELD
RXDA
RXDB
TXDA
TXDB
CTS
RLSD
DSR
RTS
SG
Y
AA
V
X
H
TSEA
TSEB
RSEA
RSEB
DTR
25
34
B. V35DTEF (100831) CABLE
Figure B-7. IAN-150 to V.35 DTE Cable Wiring
IAN150/IPP MT
6/30/97
B-13
Appendix B, Cables
CONNECTOR A:
TO INTERFACE V.35 (DTE)
SHIELD
TXDA
TXDB
RXDA
RXDB
RTS
CTS
RLSD
SG
DSR
DTR
TSEA
TSEB
RSEA
RSEB
TSEA
TSEB
RSEA
RSEB
CONNECTOR B:
TO NODAL
PROCESSOR V.35 (DTE/DCE)
1
2
11
3
12
4
5
8
7
6
20
24
16
19
14
15
25
17
18
1
3
12
2
11
8
5
4
13
20
6
15
25
17
18
24
16
19
14
25
25
SHIELD
RXDA
RXDB
TXDA
TXDB
RLSD
CTS
RTS
SG
DTR
DSR
TSEA
TSEB
RSEA
RSEB
TSEA
TSEB
RSEA
RSEB
V35NP (612250) CABLE
Figure B-8. IAN-150 to V.35 Nodal Processor DTE/DCE Cable Wiring
B-14
IAN150/IPP MT
6/30/97
Appendix B, Cables
CONNECTOR A:
TO INTERFACE (DTE)
CONNECTOR B:
TO X.21 DCE
1
2
11
3
12
17
18
7
13
4
9
5
10
1
2
9
4
11
6
13
8
SHIELD
TXDA
TXDB
RXDA
RXDB
CLKA
CLKB
SG
3
10
5
12
CONTROL A
CONTROL B
INDICATOR A
INDICATOR B
25
15
V.11-DCE/X.21/M (612270) CABLE
Figure B-9. IAN-150 to X.21 DCE Cable Wiring
IAN150/IPP MT
6/30/97
B-15
Appendix B, Cables
CONNECTOR A:
TO INTERFACE
CONNECTOR B:
TO RS-232 DCE
1
2
3
4
5
6
7
8
14
15
17
20
21
22
23
1
2
3
4
5
6
7
8
25
15
17
20
21
22
18
25
25
SHIELD
TX DATA
RX DATA
RTS
CTS
DSR
SG
RLSD
TM
TSEA
RSEA
DTR
RL
RI
LL
A. V28V54CM (100898) CABLE
CONNECTOR A:
TO INTERFACE (DTE)
CONNECTOR B:
TO V.28 DCE
1
2
3
4
5
6
7
8
14
15
17
20
21
22
23
1
2
3
4
5
6
7
8
25
15
17
20
21
22
18
25
25
SHIELD
TXDA
RXDA
RTS
CTS
DSR
SG
RLSD (DCD)
TI
TSEA
RSEA
DTR
OT2
RNG
OT1
B. V28V28C (100918) CABLE
Figure B-10. IAN-150 to V.28 DCE Cable Wiring
B-16
IAN150/IPP MT
6/30/97
Appendix B, Cables
CONNECTOR A:
TO INTERFACE (DCE)
CONNECTOR B:
TO V.28
FLOW CONTROL (DTE)
1
2
3
4
5
6
7
8
20
1
3
2
5
20
SHIELD
RXDA
TXDA
CTS
DTR
7
SG
6
DSR
25
25
A. V28V28FM (100895) CABLE
CONNECTOR A:
TO INTERFACE (DCE)
CONNECTOR B:
TO V.28 DTE
1
2
3
4
5
6
7
8
15
17
20
1
2
3
4
5
6
7
8
15
17
20
25
25
SHIELD
TXDA
RXDA
RTS
CTS
DSR
SG
RLSD
TSEA
RSEA
DTR
B. V.28/DCE/M-V.28/DTE/M (612271) CABLE
Figure B-11. IAN-150 to V.28 DTE Cable Wiring (Sheet 1 of 3)
IAN150/IPP MT
6/30/97
B-17
Appendix B, Cables
CONNECTOR A:
TO INTERFACE (DCE)
CONNECTOR B:
TO DTE
1
2
3
4
5
8
1
3
2
8
SHIELD
RXDA
TXDA
RLSD (DCD)
4
5
20
6
7
24
RTS
CTS
DTR
DSR
SG
T/RSEA
23
15
17
22
TSEA
RSEA
RNG
25
25
6
20
7
15
17
24
C. V28DTEM (100967) CABLE
CONNECTOR A:
TO INTERFACE (DCE)
CONNECTOR B:
TO DTE
1
2
3
4
5
8
1
3
2
8
SHIELD
RXDA
TXDA
RLSD (DCD)
4
5
20
6
7
24
RTS
CTS
DTR
DSR
SG
T/RSEA
23
15
17
22
TSEA
RSEA
RNG
25
25
6
20
7
15
17
24
D. V28DTEF (100968) CABLE
B-18
IAN150/IPP MT
6/30/97
Appendix B, Cables
CONNECTOR A:
TO INTERFACE (DCE)
CONNECTOR B:
TO V.28
SYMMETRICAL DTE
1
2
3
4
5
6
7
8
15
17
20
21
24
1
2
3
4
5
6
7
8
15
17
20
22
24
25
25
SHIELD
TXDA
RXDA
RTS
CTS
DSR
SG
RLSD
TSEA
RSEA
DTR
RNG
TSC
E. V.28/DCE/M-V.28/DTE/SYM/M (612272) CABLE
CONNECTOR A:
TO INTERFACE (DCE)
CONNECTOR B:
TO V.28 SYMMETRICAL DTE
1
2
3
4
5
1
3
2
5
4
8
20
7
SHIELD
RXDA
TXDA
CTS
RTS
RLSD
DTR
SG
6
DSR
24
15
17
T/RSEA
TSEA
RSEA
6
7
8
20
15
17
24
25
25
F. V28V28TM (100896) AND V28V28TF (100912) CABLES
IAN150/IPP MT
6/30/97
B-19
Appendix B, Cables
CONNECTOR A:
TO ISDN BRI LIU
CONNECTOR B:
TO U-INTERFACE
SHIELD
1
2
4
5
3
6
7
8
1
2
4
5
3
6
7
8
T1
R1
RING
TIP
BNP/ISDN (612260) CABLE
Figure B-12. IAN-150 to ISDN Cable Wiring
B-20
IAN150/IPP MT
6/30/97
Appendix B, Cables
CONNECTOR A:
TO INTERFACE
CONNECTOR B:
TO RS-449 DTE
2
11
3
12
5
10
6
19
7
13
17
18
20
6
24
4
22
7
25
12
30
19
20
17
35
11
13
29
31
9
27
8
5
26
23
21
4
9
24
16
25
SHIELD
RD A
RD B
SD A
SD B
RS A
RS B
TR A
TR B
SG
RC
TT A
TT B
DM A
RR A
DM B
RR B
CS A
CS B
RT A
ST A
RT B
ST B
37
A. TL449TF (116575) CABLE
CONNECTOR A:
TO INTERFACE
CONNECTOR B:
TO RS-449 DCE
2
11
3
12
9
4
20
21
7
13
16
24
6
19
5
10
8
14
15
25
17
18
4
22
6
24
25
7
12
30
19
37
35
17
11
29
9
27
13
31
5
23
8
26
25
37
SHIELD
SD A
SD B
RD A
RD B
RS B
RS A
TR A
TR B
SG
SC
TT B
TT A
DM A
DM B
CS A
CS B
RR A
RR B
ST A
ST B
RT A
RT B
B. TL449CM (116576) CABLE
Figure B-13. IAN-150 to EIA RS-449 (MIL-STD-188-114A) Cable Wiring
IAN150/IPP MT
6/30/97
B-21
Appendix
C
Trap Messages
NOTE:
Unless otherwise indicated, the information in this
appendix applies to the Synchrony ST-1000/ER-5
Independent Packet Processor (IPP) module as well as to
the Synchrony IAN-150. All references to the IAN-150
apply to the IPP unless otherwise noted.
The Console port on the IAN-150 can act as a network manager by displaying traps in a
user-readable form on an attached terminal or PC. The IAN’s local traps are sent to the
SNMP Trap Display after being filtered (refer to Chapter 5 for more information on this
display). Any other node in the network can also specify a destination IP address on this
node and the system will display its traps.
IAN-150 trap messages are categorized as follows:
•
System trap messages (see Table C-1)
•
Port trap messages (see Table C-2)
•
BRE trap messages (see Table C-3)
•
DLSw trap messages (see Table C-4)
•
X.25 trap messages (see Table C-5)
•
SDLC trap messages (see Table C-6)
•
BSC trap messages (see Table C-7)
•
BPS trap messages (see Table C-8)
•
Frame relay trap messages (see Table C-9)
•
Chassis Manager Traps (see Table C-10)
NOTE:
Chassis Manager Traps only apply to IPP.
•
ISDN trap messages (see Table C-11)
•
OSPF trap messages (see Table C-12)
•
IP Trap Messages (see Table C-13)
IAN150/IPP MT
6/30/97
C-1
Appendix C, Trap Messages
Table C-1. System Trap Messages
Trap No.
Trap Name
Severity
Description
20
PRIMARY ENTITY UP
Normal
Sent by the primary port to the secondary
(backup) port to inform it of a positive
status
21
PRIMARY ENTITY
DOWN
Normal
Sent by the primary port to the secondary
(backup) port to inform it of a failure
22
MEMORY WARNING
Critical
The amount of system memory available
to the unit is below the configured
warning level. The node is near the
memory regulation threshold.
23
MEMORY WARNING
RECOVERY
Critical
to the unit is above the configured
warning recovery level.
24
MEMORY REGULATION
Critical
to the unit is below the configured
regulation level. The node does not have
sufficient memory buffers for data
reception and/or transmission.
25
MEMORY REGULATION
RECOVERY
Critical
to the unit is above the configured
regulation recovery level.
Table C-2. Port Trap Messages
C-2
Trap No.
Trap Name
Severity
Description
50
TASK INITIALIZATION
FAILURE
Critical
An error was detected during task
initialization due to conditions such as
insufficient resources, configuration
conflict, and so on.
51
REMOVE TASK
Critical
A task is removing itself. May be the
result of an error condition detection or
operator command (for example, cycle
operation)
52
DRIVER INSTALL
FAILED
Critical
An error condition (for example, hardware
failure, interface card absent) prevents
successful installation of driver.
53
NO CIRCUIT ZERO
Critical
A port that requires a circuit 0 cannot be
installed because the circuit 0 is not
configured. (Some X.25 based protocols
(for example, COP, BOP, and X.25)
require a circuit 0 to be configured.)
54
NO CIRCUITS
Critical
A port that requires circuits to be
configured cannot be installed because
circuits are not configured. (All X.25
based protocolsfor example, COP,
BOP, X.25, and SDLCrequire circuits to
be configured.)
55
CONCAT. OVER MTU
Warning
An attempt to reassemble a segmented
frame exceeds the allowable maximum
transmission unit (MTU) of the port.
IAN150/IPP MT
6/30/97
Table C-2. Port Trap Messages (Cont’d)
Trap No.
Trap Name
Severity
Description
56
PORT ALREADY
INSTALLED
Major
A port was attempted to be installed
where another port was already installed.
57
SOFTWARE MISSING
Major
A port was attempted to be installed but
the software does not support the
protocol requested.
58
INSTALL FAIL: MEMORY
Major
A port was attempted to be installed but
there is not enough memory to complete
the installation.
59
INSTALL FAIL:
RESOURCES
Major
A port was attempted to be installed;
however, the creation of a system
resource (for example, control block) was
not successful.
60
INSTALL FAIL: ROUTING
Major
A port was attempted to be installed;
however, the port number specified is
greater than the max routing port, or the
interface does not support a configured
routing protocol (for example, configuring
BPS as the interface with IP as a routing
protocol).
61
BRIDGE DOM CONFLICT
Major
All installed ports do not reference the
same bridge domain.
62
FORCE STAP
FORWARDING
Minor
The specified configuration is changed to
force STAP to a forwarding state.
63
CREATING DEF BRIDGE
DOM
Minor
A default bridge domain is created when
an interface specifies bridging as enabled
but a bridge domain record with Admin
state of Up is not found.
64
CREATING DEF BRIDGE
Minor
A default bridge record is created when
an interface specifies bridging as enabled
but a bridge record is not found.
65
BRIDGE DOM PORT
UNAVAIL
Minor
There are no available ports on which a
default bridge domain can be created.
66
WARNING: ZERO LAN &
BRIDGE
Warning
Although port installation is successful
when a zero bridge number and LAN ID
are configured, this is not a typical
configuration.
67
CONFLICTING BRIDGE
NUM
Minor
Conflicting bridge numbers are specified
without internal LAN in use.
68
INVALID SR LAN ID
Minor
LAN ID greater than 4095 is specified.
69
INVALID USER
PRIORITY
Minor
Invalid user priority is specified.
70
INVALID ACCESS
PRIORITY
Minor
Invalid access priority is specified.
71
INTERNAL LAN ID
CONFLICT
Minor
A LAN ID is specified on this interface
that is the same as the internal LAN ID.
72
FORCE SR PORT
Minor
Because this port type must allow source
routing (for example, DLSw), the
configuration has changed to allow
source routing.
73
FORCING SRF
FORWARD
Minor
Source routing port STAP state is forced
to Forward.
IAN150/IPP MT
6/30/97
C-3
Table C-2. Port Trap Messages (Cont’d)
Trap No.
Trap Name
Severity
Description
74
OSPF PORT CONFLICT
Minor
OSPF is configured for an interface type
that does not support routing (for
example, BPS, BSC).
75
RIP PORT CONFLICT
Minor
RIP is configured for an interface type
example, BPS, BSC).
76
IP PORT CONFLICT
Minor
IP is configured for an interface type that
does not support routing (for example,
BPS, BSC).
77
IPX PORT CONFLICT
Minor
IPX is configured for an interface type
example, BPS, BSC).
78
BRIDGE PORT
CONFLICT
Minor
Bridging is configured for an interface
type that does not support bridging (for
example, BPS, BSC).
79
INVALID GRP MAC
Major
Invalid group address on port
80
INVALID IND MAC
Major
Invalid individual address on port
81
DUPLICATE MAC
Major
Duplicate medium access control (MAC)
address
82
INSTALLING TASK
Normal
A task is being installed.
Table C-3. BRE Trap Messages
Trap No.
Trap Name
Severity
Description
140
DUP BRE NO
Major
Duplicate BRE number
141
MTU MISMATCH
Major
The specified MTU in the Bridge Hello
message does not match the MTU of the
BRE port.
142
RPI MISMATCH
Major
The specified RPI in the Bridge Hello
message does not match the RPI of the
BRE port.
Table C-4. DLSw Trap Messages
C-4
Trap No.
Trap Name
Severity
Description
160
DLSw/TCP
CONNECTION
OPERATIONAL
Normal
DLSw/TCP connection is established.
161
DLSw/TCP
CONNECTION FAILED
Normal
DLSw/TCP connection failed.
IAN150/IPP MT
6/30/97
Table C-5. X.25 Trap Messages
Trap No.
Trap Name
Severity
Description
180
RECEIVED INVALID
GFID
Major
A frame is received with an invalid global
filter ID (GFID) due to a Layer 3 modulo
misconfiguration.
181
HDLC SHUTDOWN
STARTED
Minor
HDLC or LLC is disabling operation as a
result of events such as operator
command, N2 expiration, and error
recovery.
182
SHORT MSG RECD
FROM NET
Major
An invalid (short) message is received
from the network (not the port interface).
183
INVALID RESTART
Major
An invalid restart is received from the
port, indicating a protocol error from
ITU-T X.25 Table C2.
184
RESET
Normal
An invalid reset is received.
185
RX ON UNASSIGNED
LCN
Minor
A packet is received from the interface
but there is no corresponding circuit
configured on the X.25 port.
186
CLEAR
Normal
An X.25-based port (for example, SDLC,
X.25, BPS, BSC, COP, and BOP) clears
an X.25 switched virtual circuit.
187
SHORT PKT RECD
FROM LINE
Major
A packet is received from the interface
that is less than the Layer 3 control.
Table C-6. SDLC Trap Messages
Trap No.
Trap Name
Severity
Description
200
STN RECOVER
Normal
A station is detected by generating a poll
or response.
201
STN FAILED
Normal
A station has failed (does not respond).
202
WIN EXCEED
Normal
A frame is received outside the
configured window size.
203
RX SNRM
Major
TPAD receives an SNRM from the
attached secondary device, indicating a
misconfiguration.
204
NULL SFRM
Minor
TPAD receives a null supervisory frame.
Table C-7. BSC Trap Messages
Trap No.
Trap Name
Severity
Description
220
DEV DOWN
Normal
The station is down.
221
DEV UP
Normal
The station is up.
222
NET CONG
Normal
The network is congested. This may be
corrected by increasing the Layer 3
(circuit) window size
IAN150/IPP MT
6/30/97
C-5
Table C-8. BPS Trap Messages
Trap No.
Trap Name
Severity
Description
240
DEV DOWN
Normal
The station is down.
241
DEV UP
Normal
The station is up.
242
NET CONG
Normal
The network is congested. This may be
corrected by increasing the Layer 3
(circuit) window size.
Table C-9. Frame Relay Trap Messages
C-6
Trap No.
Trap Name
Severity
Description
260
PVC UP
Normal
A DLCI becomes active.
261
PVC DOWN
Normal
A DLCI becomes inactive.
262
DUP
Major
A duplicate IPX address is detected.
263
DUPLICATE LOCAL
Major
A duplicate local DLCI is detected on the
node.
264
DUPLICATE REMOTE
Major
A duplicate remote DLCI is detected on
the node.
265
DUP
Major
A duplicate device is detected between
nodes.
266
INVALID
Minor
An invalid LMI is received.
267
INVALID
ADVERTISEMENT
Minor
An invalid advertisement is received.
268
INVALID IE LENGTH
Minor
An invalid information element is received
within an LMI.
269
INVALID DLCI
Minor
A frame is received with an invalid DLCI.
270
TOO MANY RECORDS
Major
The maximum number of configuration
records for a frame relay database has
been exceeded.
271
DUP LAP DLCI
Major
Duplicate LAP DLCIs are detected.
272
ARP DLCI MISMATCH
Major
An ARP entry already exists for the IP
address with a different DLCI in the table.
IAN150/IPP MT
6/30/97
Table C-10. Chassis Manager Trap Messages (IPP Only)
Trap No.
Trap Name
Severity
Description
300
Active
Normal
Generated when a new Master is
negotiated
301
Standby
Normal
Generated when a new Master is
negotiated
302
Return to Normal Pipe
Width
Major
Generated when parallel busses in the
ER Chassis returns to 96-bit operation
303
Narrow Pipe Width
Normal
Generated when parallel busses in the
ER Chassis narrow from 96-bit to 64-bit
operation
304
Module Inserted
Minor
Generated when ER module inserted
305
Module Removed
Minor
Generated when ER module inserted
306
Power Supply Failed
Major
Generated if power supply fails
307
Power Supply Failed
Major
Generated if power supply recovered
308
Fan Failed
Normal
Generated when fan fails
309
Fan Failed
Normal
Generated when fan recovers
Table C-11. ISDN Trap Messages
Trap No.
Trap Name
Severity
Description
340
CALL CONNECTED
Normal
An ISDN connection is established.
341
CALL CLEARED
Normal
An ISDN connection is cleared.
342
CALL REQ INITIATE
Normal
An ISDN connection is initiated.
343
INC CALL ACCEPT
Normal
An incoming ISDN connection is
accepted.
344
CALL REQ FAIL
Normal
An ISDN connection request failed.
345
INC CALL REJECT
Normal
An incoming ISDN connection is rejected.
IAN150/IPP MT
6/30/97
C-7
Table C-12. OSPF Trap Messages
C-8
Trap No.
Trap Name
Severity
Description
360
BAD PACKET TYPE
Normal
A packet with a bad OSPF type is
received.
361
BAD IP DEST
Normal
A packet with a bad IP address is
received.
362
BAD IP PROTO ID
Normal
A packet with a bad IP prototype field is
received.
363
RX OWN IP ADDR
Normal
A packet with this node’s IP address is
received.
364
BAD VERSION
Normal
A packet with a bad version is received.
365
BAD CHECKSUM
Normal
A packet with a bad checksum is
received.
366
BAD INTERFACE AREA
ID
Normal
A packet with a bad area ID is received.
367
AREA MISMATCH
Normal
A packet with an area that does not
match is received.
368
BAD VIRTUAL LINK
Normal
A packet with a bad virtual link is
received.
369
AUTHORIZATION TYPE
MISMATCH
Normal
A packet with an authorization type
mismatch is received.
370
AUTHORIZATION KEY
MISMATCH
Normal
A packet with an authorization key
mismatch is received.
371
PACKET TOO SMALL
Normal
A packet that is too small is received.
372
RECEIVED ON DOWN
PORT
Normal
A packet is received although the port is
down.
373
HELLO: E OPTION
MISMATCH
Normal
A Hello packet with a mismatch of E
Option is received.
374
HELLO: MASK
MISMATCH
Normal
A Hello packet with a mismatched Hello
mask is received.
375
HELLO: TIMER
MISMATCH
Normal
A Hello packet with a mismatched timer
is received.
376
HELLO: DEAD TIMER
MISMATCH
Normal
A Hello packet with a mismatched dead
timer is received.
377
HELLO: UNKNOWN
VIRTUAL NBR
Normal
A Hello packet with an unknown virtual
neighbor is received.
378
HELLO: UNKNOWN
NBMA NBR
Normal
A Hello packet with an unknown nonbroadcast multi-access (NBMA) neighbor
is received.
379
DB DESCR: UNKNOWN
NBR
Normal
A Hello packet with an unconfigured
380
ACK: UNKNOWN NBR
Normal
An Ack packet with an unconfigured
381
LS REQ: UNKNOWN
NBR
Normal
An LS Req packet with an unconfigured
382
LS UPDATE: UNKNOWN
NBR
Normal
An LS Update packet with an
unconfigured neighbor is received.
383
DB DESCR: NBR STATE
TOO LOW
Normal
A Hello packet with a neighbor state that
is too low is received.
IAN150/IPP MT
6/30/97
Table C-12. OSPF Trap Messages (Cont’d)
Trap No.
Trap Name
Severity
Description
384
ACK: NBR STATE TOO
LOW
Normal
An Ack packet with a neighbor state that
is too low is received.
385
LS REQ: NBR STATE
TOO LOW
Normal
An LS Req packet with a neighbor state
that is too low is received.
386
LS UPD: NBR STATE
TOO LOW
Normal
An LS Update packet with a neighbor
state that is too low is received.
387
DB DESC: NBR ROUTER
ID BAD
Normal
A bad router ID is received.
388
LS REQ: EMPTY
REQUEST
Normal
An empty LS Req is received.
389
LS REQ: BAD PACKET
Normal
A bad LS Req is received.
390
LS UPD: NEWER SELFGEN LSU
Normal
A newer self-generated LSU is received in
the LS update.
391
LS UPD: BAD LS
CHECKSUM
Normal
An LS update is received with a bad
checksum.
392
LS UPD: LESS RECENT
RECEIVED
Normal
An LS update is received that is less
recent than the one already received.
393
LS UPD: BAD LSA TYPE
Normal
An LS update that has a bad LSA type is
received.
394
MEMORY ALLOCATION
FAILURE
Minor
OSPF task failed memory allocation.
395
VIRTUAL LINK: NO
BACKBONE AREA
Major
Virtual link is configured without
backbone area.
396
PORT: NO BACKBONE
AREA
Major
Port is configured without backbone area.
397
NO TOS COST
Major
Type of service (TOS) cost is zero.
398
ILLEGAL PRIORITY
Major
Invalid priority is configured.
399
NO ROUTER ID
Major
Router ID is not configured.
400
PORT: NO AREA
Major
Area is not configured.
401
AREA: NO PORT
Major
Area is configured without port.
402
VIRTUAL LINK: < 2
AREAS
Major
Virtual link is configured with less than
two areas.
403
BACKBONE AREA: NO
PORT
Major
Backbone area is configured without port.
404
PORT: NO BACKBONE
AREA
Major
Backbone area is not configured.
405
DUPLICATE
BACKBONES
Major
A duplicate backbone network is
configured.
406
VIRTUAL LINK: NO
TRANSIT AREA
Major
Virtual link is configured without area.
407
PORT: NO TRANSIT
AREA
Major
Port is configured without area.
408
ILLEGAL INTERFACE
TYPE
Major
Interface type is illegal.
409
PORT: NO NETWORK
Major
Port does not have network configuration.
IAN150/IPP MT
6/30/97
C-9
C-10
Trap No.
Trap Name
Severity
Description
410
PORT: DUPL NET
Major
Port has a duplicate network
configuration.
411
PORT: NO IP ADDR
Major
Port is configured without IP address.
412
NET DEFINED IN SAME
AREA
Major
Duplicate networks are configured in the
same area.
413
NET DEFINED IN DIFF
AREAS
Major
Duplicate networks are configured in
different areas.
414
BACKBONE IN DIFF
AREAS
Major
Backbone is configured in another area.
415
DUPLICATE BACKBONE
AREAS
Major
Backbone area is a duplicate.
416
AREA 0 CANNOT BE
STUB
Major
Area 0 cannot be a stub.
417
PORT: DUPLICATE IP
ADDR
Major
Duplicate IP addresses are detected.
418
COMMON ROUTING
TABLE FULL
Major
Common routing table is full.
419
BAD PORT CONFIG
Major
Port configuration is missing or bad.
420
EXCEEDED MAX
ROUTERS ON NET
Major
Too many routers are configured on
network.
421
BAD PROTOCOL
CONFIG
Major
Protocol configuration is missing or
invalid.
422
OSPF PORT UP
Normal
Port is up. (See NOTE 1 below.)
423
WAIT TIMER
Normal
Port is in wait state. (See NOTE 1 below.)
424
BKUP SEEN
Normal
Port backup is seen. (See NOTE 1
below.)
425
NEIGHBOR CHANGE
Normal
Neighbor change is detected. (See NOTE
1 below.)
426
LOOP INDICATION
Normal
Loop indication. (See NOTE 1 below.)
427
UNLOOP INDICATION
Normal
Unloop indication. (See NOTE 1 below.)
428
PORT DOWN
Normal
Port is down. (See NOTE 1 below.)
429
HELLO RCVD
Normal
Hello is received from neighbor. (See
NOTE 2 below.)
430
START
Normal
Neighbor start. (See NOTE 2 below.)
431
TWO WAY RCVD
Normal
Neighbor two way. (See NOTE 2 below.)
432
NBR ADJ OK
Normal
Neighbor adjacency OK. (See NOTE 2
below.)
433
NEGOTIATION DONE
Normal
Negotiation is complete. (See NOTE 2
below.)
434
EXCHANGE DONE
Normal
Exchange is complete. (See NOTE 3
below.)
435
SEQUENCE NUMBER
MISMATCHED
Normal
Sequence number is mismatched. (See
NOTE 3 below.)
436
BAD LS REQUEST
Normal
Bad LS request is received. (See NOTE 3
below.)
IAN150/IPP MT
6/30/97
Trap No.
Trap Name
Severity
Description
437
LOAD DONE
Normal
LS database load is complete. (See
NOTE 3 below.)
438
ONE WAY
Normal
One way neighbor state. (See NOTE 3
below.)
439
RESET ADJACENCY
Normal
Neighbor adjacency reset. (See NOTE 3
below.)
440
KILL NBR
Normal
Neighbor is removed. (See NOTE 3
below.)
441
INACTIVE TIMER FIRED
Normal
Inactive timer of neighbor goes off. (See
NOTE 3 below.)
442
LOW LEVEL DOWN
Normal
Low level down. (See NOTE 3 below.)
443
T3_DR_CHANGE
Normal
The backup designated router (BDR) has
changed on one of the attached networks.
The logging message produced includes
the network IP address and the new
backup designated routers.
444
T4_NEW_LSA_SENT
Normal
The router is originating a new instance
of a link state advertisement. The logging
message produced indicates the LS type,
the link state ID, and the advertising
router associated with the advertisement.
445
T5_NEW_LSA_
RECEIVED
Normal
The router has received a new instance of
a link state advertisement in link state
update packets. The routing table will be
recalculated. The logging message
produced indicates the advertisement’s
LS type, link state ID, and advertising
router.
446
T6_ROUTING_TABLE_
CHANGE
Normal
An entry in the routing table has changed.
The logging message produced indicates
the destination type, destination ID, and
the old and new paths to the destination.
447
E1_RCV_LSA_CHKSUM
Normal
The checksum in a received link state
advertisement is incorrect. The
advertisement is discarded. The logging
message includes the advertisement’s LS
type, link state ID, and advertising router
(which may be incorrect). The message
also includes the neighbor from whom
the advertisement was received.
448
E2_AGED_LSA_
CHKSUM
Normal
During the aging process, it is discovered
that one of the link state advertisements
in the database has an incorrect
checksum. This indicates memory
corruption or a software error in the
router itself. The router should be
dumped and restarted.
IAN150/IPP MT
6/30/97
C-11
C-12
Trap No.
Trap Name
Severity
Description
449
R1_LSA_NEW_CHKSUM
Normal
Two link state advertisements have been
seen whose LS type, link state ID,
advertising router, and LS sequence
number are the same, yet with differing
LS checksums. These are considered to
be different instances of the same
advertisement. The instance with the
larger checksum is accepted as more
recent. The logging message includes the
LS type, link state ID, advertising router,
LS sequence number, and the two
differing checksums.
450
R2_LSA_NEW_AGE
Normal
Two link state advertisements have been
seen whose LS type, link state ID,
advertising router, LS sequence number,
and LS checksum are the same, yet can
be distinguished by their LS age fields
(one of the advertisement’s LS age is
MaxAge, or the two LS age fields differ by
more than MaxAgeDiff). The logging
message includes the LS type, link state
ID, advertising router, LS sequence
number, and the two differing ages.
451
R3_MORE_RECENT_
SELF_LSA
Normal
The router has received a more recent
instance of one of its self-originated
advertisements and is forced to originate
a new advertisement. The logging
type, link state ID, and advertising router
along with the neighbor from whom the
advertisement was received.
452
R4_NO_LSA_FOR_ACK
Normal
An acknowledgment has been received
for an instance of an advertisement that
is not currently contained in the router’s
database. The logging message details
the instance being acknowledged and the
database copy (if any), along with the
neighbor from whom the
acknowledgment was received.
453
R5_LESS_RECENT_LSA
Normal
An advertisement has been received
through the flooding procedure that is
less recent than the router’s current
database copy. The logging message
includes the received advertisement’s LS
type, link state ID, advertising router, LS
sequence number, LS age, and LS
checksum. The message also displays
the neighbor from whom the
advertisement was received.
IAN150/IPP MT
6/30/97
Trap No.
Trap Name
Severity
Description
454
N1_LSA_REFRESH_
FIRED
Normal
The link state refresh timer has fired for
one of the router’s self-originated
advertisements. A new instance of the
advertisement must be originated. The
type, link state ID, and advertising router.
455
N2_MAXAGE_LSA_
FLOOD
Normal
One of the advertisements in the router’s
link state database has aged to MaxAge.
At this point, the advertisement is no
longer included in the routing table
calculation and is reflooded. The
message lists the advertisement’s LS
type, link state ID, and advertising router.
456
N3_MAXAGE_LSA_
REMOVED
Normal
An advertisement of age MaxAge has
been flushed from the router’s database.
This occurs after the advertisement has
been acknowledged by all adjacent
neighbors. The message lists the
advertisement’s LS type, link state ID,
and advertising router.
NOTES:
1. The state of a router interface has changed, causing new link state advertisements to
originate. The logging message produced includes the interface’s IP address (or other
name) and new state values.
2. The state of a neighbor has changed. The logging message produced includes the neighbor
IP address and old and new state values.
3. The state of a neighbor has changed. The logging message produced includes the neighbor
IP address and new state values.
Table C-13. IP Trap Messages
Trap No.
Trap Name
Severity
Description
500
Duplicate IP Address
Minor
IP is configured with a duplicate IP
Address
IAN150/IPP MT
6/30/97
C-13
Appendix
D
User Interface Screen Index
NOTE:
Unless otherwise indicated, the information in this appendix
noted.
The User Interface Screen Index contains a list of every IAN-150 User Interface screen, the hotkey associated with each screen, and if applicable the command options that appear above the
command line prompt (see Note, below). The commands listed in the Screen Index are:
A
Abort
B
Build
C
Cycle
CC
Clear Call
CRS Chassis Reset
D
Delete
E
Evacuate
I
Install
M
Monitor (see Note, below)
N
Read Next
R
Read
RES Reset
RLC Reload Cfg
RLS Reload SW
RSC Reload SW & Cfg
RST Restart
SAM Switch Active Master
SC
Setup Call
SE
Search (see Note, below)
STF
Station Off
STN Station On
SU
IAN150/IPP MT
6/30/97
Submit
D-1
Appendix D, User Interface Screen Index
T
Translate
V
Validate
W
Write
NOTE:
The SE (search) and M (monitor) commands noted with an
asterisk (*) above are valid for some screens, but are considered
“hidden” commands and do not appear above the command line
prompt. The SE command applies to all screens where N (Read
Next) is a valid command. The M command is described in
Chapter 3, “Monitoring Basics,” and in each chapter that
describes how to monitor and troubleshoot specific operations,
such as Chapter 7, “Ethernet Monitoring.”
If you want a brief description of commands, refer to the Synchrony IAN-150 Quick Start Guide.
If you want a detailed explanation of the commands and their functions, refer to Chapter 2,
“Getting Started,” in this manual.
The * column identifies IAN-150 screens that display abbreviated information when viewed from
a partial access mode. For a description of the IAN-150’s available access modes, refer to
Synchrony IAN-150 Quick Start Guide or see Chapter 2, “Getting Started,” in this manual.
Table D-1. IAN-150 Screen Index
Hot Key
Screen
Number
M
D-2
*
Description
Commands
Available
Main Menu
S
1
SN
1.1
Status and Control (menu)
SNN
1.1.1
Node Status
R, RST, RLS, RLC,
RSC
SNH
1.1.2
Hardware Type Display
R
SNC
1.1.3
Chassis Manager Status (menu)
SNCM
1.1.3.1
Node Status and Control (menu)
Chassis Manager Statistics
CRS, R, RES, SAM
Chassis Manager Slot Statistics
R, N
SNCS
1.1.3.2
SNB
1.1.4
SP
1.2
SPP
1.2.1
Port Status and Control
SPE
1.2.2
R, N, RES
SPT
1.2.3
R, N, RES
SPM
1.2.4
EIA Modem Lead Display
R, N
SB
1.3
SBB
1.3.1
SBBE
1.3.1.1
BRE Port Statistics
R, N, RES
SBBP
1.3.1.2
R, N, RES
SBBF
1.3.1.3
R, N
Backup Statistics
Port Status (menu)
R, N, RES, I, E, C
Bridging Status (menu)
Bridge Relay Element Statistics (menu)
IAN150/IPPMT
6/30/97
Table D-1. IAN-150 Screen Index (Cont’d)
Hot Key
Screen
Number
SBBR
1.3.1.4
*
Description
BRE Routing Table
SBBA
1.3.1.5
SBB
1.3.2
General Bridging Status
BRE Adjacency Table
SBS
1.3.3
Spanning Tree Status (menu)
SBST
1.3.3.1
Commands
Available
R, N
R, N
R, N, RES
R, N
SBSP
1.3.3.2
R, N, RES
SBR
1.3.4
Source Routing Bridging Status
R, N, RES
SBD
1.3.5
Bridging Tables (menu)
SBTF
1.3.5.1
R, N
SBTS
1.3.5.2
R, N
SBDX
1.3.5.3
R, N
SR
1.4
SRI
1.4.1
SRII
1.4.1.1
SRIII
1.4.1.1.1
IP Status
R, RES
SRIIR
1.4.1.1.2
R, N
Routing Status (menu)
IP Control and Status (menu)
IP Status (menu)
SRIIA
1.4.1.1.3
Address Resolution Protocol Table
R, N
SRIIT
1.4.1.1.4
IP Address Table
R, N
SRIC
1.4.1.2
ICMP Status
SRIU
1.4.1.3
UDP Status (menu)
SRIUS
1.4.1.3.1
UDP Statistics
R, RES
SRIUL
1.4.1.3.2
UDP Listen Table
R, N
SRX
1.4.2
SRXP
1.4.2.1
IPX Protocol Status
R, RES
SRXS
1.4.2.2
IPX SAP Status
R, RES
SRXR
1.4.2.3
IPX Routing Table
R, N
SRXT
1.4.2.4
IPX Service Advertisement
Protocol (SAP) Table
R, N
SRTR
1.4.3.4
R, RES
SRTX
1.4.3.5
R, RES
SRD
1.4.4
SRDP
1.4.4.1
R, N, RES
SRDC
1.4.4.2
R, N
SRDN
1.4.4.3
DLSw NetBIOS Name Caching Table
R, N
R, RES
IPX Status (menu)
DLSw Status and Control (menu)
SRR
1.4.5
RIP Status
SRO
1.4.6
OSPF Status (menu)
R, RES
SROT
1.4.6.1
R, RES
SROI
1.4.6.2
R, N
SROL
1.4.6.3
OSPF Link State Database Status
(menu)
SROLS
1.4.6.3.1
IAN150/IPP MT
6/30/97
OSPF Link State Database Table STUB Type
R, N
D-3
Hot Key
Screen
Number
SROLR
1.4.6.3.2
OSPF Link State Database Table RTR Type
R, N
1.4.6.3.3
OSPF Link State Database Table NET Type
R, N
SROLU
1.4.6.3.4
OSPF Link State Database Table NET SUM Type
R, N
SROLA
1.4.6.3.5
OSPF Link State Database Table AS SUM Type
R, N
SROLE
1.4.6.3.6
OSPF Link State Database Table EXT Type
R, N
SRON
1.4.6.4
R, N
SROV
1.4.6.5
R, N
R, N
SROLN
D-4
*
Description
Commands
Available
SROR
1.4.6.6
SRE
1.4.7
SRES
1.4.7.1
EGP Statistics
R, RES
SRET
1.4.7.2
EGP Neighbor Table
R, N
EGP Control and Status (menu)
SRB
1.4.8
BOOTP Status
R, RES
SRL
1.4.9
LLC Status
R, N, RES
SS
1.5
SSI
1.5.1
Bisync Status
R, N, RES, STF,
STN
SSU
1.5.2
Burroughs Poll Select Status
R, N, RES, STF,
STN
SSS
1.5.3
SDLC Station Status
R, N, RES, STF,
STN
SSX
1.5.4
X.25 Status
R, N, RES
Packet Switching Status (menu)
SSC
1.5.5
Circuit Status
R, N, RES, CC
SSL
1.5.6
Cleared Circuit Status
R, N, RES
SF
1.6
SFP
1.6.1
Frame Relay Status (menu)
SFV
SFC
SFR
1.6.4
SI
1.7
SID
1.7.1
ISDN D-Channel Status and Statistics
R, N, RES
SIB
1.7.2
ISDN B-Channel Status and Statistics
R, N
SIN
1.7.3
ISDN Destination Status and Statistics
R, N, RES, SC, CC
SIH
1.7.4
ISDN Call History
R, N
C
2
CN
2.1
CNN
2.1.1
Node Parameter Configuration
R, W
CNF
2.1.2
Node Fast Path Configuration
R, W
CNC
2.1.3
Chassis Manager Configuration (menu)
R, N, RES
1.6.2
R, N, RES
1.6.3
R, N, RES, I, E, C
R, N, RES
ISDN Status (menu)
Configuration (menu)
Node Configuration (menu)
IAN150/IPPMT
6/30/97
Hot Key
Screen
Number
CNCP
2.1.3.1
Chassis Manager PIPE Port
Configuration
R, W
CNCC
2.1.3.2
Chassis Configuration
R, W, D
CNB
2.1.4
CNBP
2.1.4.1
Primary Port Configuration
CNBB
2.1.4.2
Backup Port Configuration
R, N, W, D, B
CNBT
2.1.4.3
Backup Timing Configuration
R, W
CNM
2.1.5
CNMS
2.1.5.1
System Group Configuration
R, W
CNMC
2.1.5.2
Community Name Configuration
R, W
CNMT
2.1.5.3
Trap Output Configuration
R, W
CNME
2.1.5.4
Element Management System
Configuration
R, W
CNMF
2.1.5.5
Trap Filtering
R, N, W
CL
2.2
CLE
2.2.1
*
Description
Commands
Available
Backup Node Configuration (menu)
R, N, W, D, B
Network Management Configuration
(menu)
LAN Port Configuration (menu)
Ethernet Port Configuration
R, N, W, D
Token Ring Port Configuration
R, N, W, D
CLT
2.2.2
CB
2.3
CBB
2.3.1
BRE Port Configuration
R, N, W, D
CBD
2.3.2
Bridge Domain Configuration
R, N, W, D
CBP
2.3.3
Bridge Port Configuration
R, N, W, D
CBF
2.3.4
Bridge Filter Configuration (menu)
CBFA
2.3.4.1
Bridge Address Filter Configuration
R, N, W, D, B
CBFM
2.3.4.2
Bridge Mask Filter Configuration
R, N, W, D. B
CBFS
2.3.4.3
Bridge Static Filter Configuration
R, N, W, D, B
CBFB
2.3.4.4
CBG
2.3.5
CR
2.4
CRI
2.4.1
Bridge Configuration (menu)
BRE Static Filter Configuration
Token Ring Group to Functional Map
R, N, W, D, B
R, N, W, D
Routing Configuration (menu)
IP Configuration (menu)
CRIP
2.4.1.1
x
IP Protocol Configuration
R, W, D
CRIO
2.4.1.2
x
IP Port Configuration
R, N, W, D
CRIS
2.4.1.3
IP Static Route Configuration
R, N, W, D
CRIA
2.4.1.4
IP Static ARP Configuration
R, N, W, D
IP Filter Configuration
R, N, W, D, B
CRIF
2.4.1.5
CRX
2.4.2
CRXP
2.4.2.1
x
CRXO
2.4.2.2
x
CRXR
2.4.2.3
CRXA
2.4.2.4
IPX Address Filter Configuration
R, N, W, D, B
CRXS
2.4.2.5
IPX SAP Filter Configuration
R, N, W, D, B
CRT
2.4.3
IAN150/IPP MT
6/30/97
IPX Configuration (menu)
x
IPX Protocol Configuration
R, W, D
IPX Port Configuration
R, N, W, D
IPX Static Routes
R, N, W, D
TCP Configuration
R, W, D
D-5
Hot Key
Screen
Number
CRD
2.4.4
CRDL
2.4.4.1
CRDR
2.4.4.2
CRR
2.4.5
CRRN
2.4.5.1
CRRP
2.4.5.2
CRO
2.4.6
CROT
2.4.6.1
CROA
2.4.6.2
CROD
2.4.6.3
CROP
2.4.6.4
CRON
2.4.6.5
Description
Commands
Available
DLSw Configuration (menu)
x
DLSw Local Configuration
R, N, W, D
DLSw Remote Configuration
R, N, W, D
RIP Configuration (menu)
x
RIP Neighbor Configuration
R, W, D
RIP Port Configuration
R, N, W, D
OSPF Configuration (menu)
x
x
OSPF Protocol Configuration
R, W, D
OSPF Area Common Configuration
R, N, W, D
OSPF Area Address Configuration
R, N, W, D
OSPF Port Configuration
R, N, W, D
OSPF NBMA Address Configuration
R, N, W, D
OSPF Virtual Link Configuration
R, W, D
CROV
2.4.6.6
x
CRE
2.4.7
x
CRB
2.4.8
CP
2.5
CPA
2.5.1
x
Async Configuration (menu)
CPAP
2.5.1.1
x
Async Port Configuration
R, N, W, D
CPAX
2.5.1.2
Async X.3 Parameters Configuration
R, N, W, D
CPAC
2.5.1.3
x
Async Circuit Configuration
R, N, W, D
CPAN
2.5.1.4
x
Async Network Parameter Configuration
R, N, W, D
CPAA
2.5.1.5
x
Async Access Class Configuration
R, N, W, D
CPAR
2.5.1.6
x
Async Resource Management
R, N, W, D
CPAL
2.5.1.7
x
Local/Remote Profile Configuration
R, N, W, D
CPB
2.5.2
x
Bisync Configuration (menu)
CPBT
2.5.2.1
x
Bisync Tpad Port Configuration
R, N, W, D
CPBH
2.5.2.2
x
Bisync Hpad Port Configuration
R, N, W, D
CPBC
2.5.2.3
x
Bisync Circuit Configuration
R, N, W, D
CPBN
2.5.2.4
x
CPO
2.5.3
x
BOP Configuration (menu)
CPOP
2.5.3.1
x
BOP Port Configuration
R, N, W, D
CPOC
2.5.3.2
x
BOP Circuit Configuration
R, N, W, D
CPON
2.5.3.3
x
BOP Network Parameter Configuration
R, N, W, D
CPU
2.5.4
x
CPUT
2.5.4.1
x
Burroughs Poll Select Tpad Port
Configuration
R, N, W, D
CPUH
2.5.4.2
x
Burroughs Poll Select Hpad Port
Configuration
R, N, W, D
x
Burroughs Poll Select Circuit
Configuration
R, N, W, D
x
Burroughs Network Parameter
Configuration
R, N, W, D
CPUC
CPUN
D-6
*
2.5.4.3
2.5.4.4
EGP Configuration
R, N, W, D
BOOTP Configuration
R, W, D
Packet Switch Configuration (menu)
Bisync Network Parameter
Configuration
R, N, W, D
Burroughs Poll Select Configuration
(menu)
IAN150/IPPMT
6/30/97
Hot Key
Screen
Number
*
CPC
2.5.5
x
COP Configuration (menu)
CPCP
2.5.5.1
x
COP Port Configuration
R, N, W, D
CPCC
2.5.5.2
x
COP Circuit Configuration
R, N, W, D
CPCN
2.5.5.3
x
COP Network Parameter Configuration
R, N, W, D
CPS
2.5.6
CPST
2.5.6.1
x
SDLC Tpad Configuration (menu)
CPSTP
2.5.6.1.1
x
SDLC Tpad Port Configuration
R, N, W, D
CPSTC
2.5.6.1.2
x
SDLC Tpad Circuit Configuration
R, N, W, D
x
SDLC Tpad Network Parameter
Configuration
R, N, W, D
Description
Commands
Available
SDLC Configuration (menu)
CPSTN
2.5.6.1.3
CPSH
2.5.6.2
x
SDLC Hpad Configuration (menu)
CPSHP
2.5.6.2.1
x
SDLC Hpad Port Configuration
R, W, N, D
CPSHC
2.5.6.2.2
x
SDLC Hpad Circuit Configuration
R, N, W, D
x
SDLC Hpad Network Parameter
Configuration
R, N, W, D
SDLC LLC Conversion Configuration
(menu)
CPSHN
2.5.6.2.3
CPSL
2.5.6.3
x
CPSLP
2.5.6.3.1
x
SDLC LLC Conversion Port
Configuration
R, N, W, D
CPSLC
2.5.6.3.2
x
SDLC LLC Conversion Circuit
Configuration
R, N, W, D
CPSLN
2.5.6.3.3
x
SDLC LLC Conversion Network
Parameter Configuration
R, N, W, D
CPX
2.5.7
x
X.25 Configuration (menu)
CPXP
2.5.7.1
x
X.25 Port Configuration
R, N, W, D
CPXC
2.5.7.2
x
X.25 Circuit Configuration
R, N, W, D
CPXL
2.5.7.3
CPXN
2.5.7.4
CPT
2.5.8
CPTD
2.5.8.1
Called Address Translation
Configuration
R, N, W, D, B, T
CPTG
2.5.8.2
Destination Calling Address Translation
Configuration
R, N, W, D, B, T
CPTS
2.5.8.3
Source Calling Address Validation
Configuration
R, N, W, D, B, V
CPF
2.5.9
CF
2.6
CFN
2.6.1
CFNP
2.6.1.1
x
CFNC
2.6.1.2
x
CFT
2.6.2
x
IAN150/IPP MT
6/30/97
x
X25 Lookup Table
R, N, W, D
X.25 Network Parameter Configuration
R, N, W, D
Address Translation Configuration (menu)
Facility Configuration
R, N, W, D
Frame Relay Configuration (menu)
Frame Relay Network Configuration
(menu)
Frame Relay Network Port
Configuration
Frame Relay Network PVC
Configuration
Frame Relay Trunk Port Configuration
R, N, W, D
R, N, W, D
R, N, W, D
D-7
D-8
Hot Key
Screen
Number
CFG
2.6.3
CFGP
2.6.3.1
*
Description
Commands
Available
Frame Relay Gateway Configuration
(menu)
x
Frame Relay Gateway Port
Configuration
R, N, W, D
R, N, W, D
R, N, W, D
CFGC
2.6.3.2
x
Frame Relay Internetwork PVC
Configuration
CFGV
2.6.3.3
x
Frame Relay Virtual Trunk
Configuration
CFD
2.6.4
CFDP
2.6.4.1
Frame Relay Dedicated User Configuration
(menu)
x
Frame Relay Dedicated User Port
Configuration
R, N, W, D
R, N, W, D
CFDC
2.6.4.2
x
Frame Relay Dedicated User PVC
Configuration
CFH
2.6.5
x
Frame Relay HDLC/SDLC Configuration
R, N, W, D
CFL
2.6.6
CFLP
2.6.6.1
x
Frame Relay LAP Configuration (menu)
CFLC
2.6.6.2
x
CFM
2.6.7
Frame Relay Multicast Configuration
CFA
2.6.8
Frame Relay Address Translation (menu)
CFAI
2.6.8.1
Frame Relay IP Address Translation
Configuration
R, N, W, D
CFAX
2.6.8.2
Frame Relay IPX Address Translation
Configuration
R, N, W, D
CFS
2.6.9
Frame Relay Source Routing Configuration
R, N, W, D
CI
2.7
CIP
2.7.1
x
CID
2.7.2
x
U
3
UP
3.1
UPP
3.1.1
UPX
3.1.2
UF
3.2
UFI
3.2.1
UFIC
3.2.1.1
Frame Relay LAP Configuration
Frame Relay LAP PVC Configuration
R, N, W, D
R, N, W, D
R, N, W, D
ISDN Configuration (menu)
ISDN Port Configuration
R, N, W, D
ISDN Destination Configuration
R, N, W, D, B
Utilities (menu)
Ping (menu)
ICMP Ping Parameters
R, SU, A
IPX Ping Parameters
R, SU, A
Table Flush (menu)
IP Table Flush (menu)
Common Routing Table Flush
SU
ARP Table Flush
SU
UFIA
3.2.1.2
UFX
3.2.2
UFXR
3.2.2.1
IPX Routing Table Flush
SU
UFXS
3.2.2.2
IPX SAP Table Flush
SU
US
3.3
SNMP Trap Display
UU
3.4
Pseudoport Configuration and Operation
(menu)
UUP
3.4.1
Pseudoport Port Configuration
R, W
UUC
3.4.2
Pseudoport Circuit Configuration
R, N, W, D
UUO
3.4.3
Pseudoport Operation
R, N, SU, A
IPX Table Flush (menu)
IAN150/IPPMT
6/30/97
Hot Key
Screen
Number
UL
3.5
UT
3.6
D
4
*
Description
Loader
R, SU, A
Telnet
Diagnostics (menu)
DP
4.1
T
5
Time
H
6
Help
IAN150/IPP MT
6/30/97
Commands
Available
Port Diagnostics
R, N, SU, A
R, W
D-9
Index
3
3270 Bisync Port, 3-5, 13-1
A
Abort (A) Command, 2-28
AC Power Connections, IAN-150, 1-7
Access Levels, user interface, 2-19
Access Port
3270 Bisync, 3-5
SDLC TPAD, 3-4
Access Switching Specifications, IAN-150, 1-12
Activating Configuration Settings, 2-31
Address Resolution Protocol (ARP) Table
displaying, 11-8
parameter descriptions, 11-8
ARP Table. See Address Resolution Protocol
(ARP) Table
AS SUM Advertisements, OSPF Link State
Database Table, 11-43
Assigning IP Address, 3-13
B
Backup Operations
monitoring, 19-1
troubleshooting, 19-1
Backup Statistics
Backup Statistics Screen, 19-2
B-Channel Status, ISDN
displaying, 18-7
Binary Synchronous Communication (BSC)
Operations. See Bisync Operations
Bisync Circuit Status
displaying, 13-5
Bisync Cleared Circuit Status
displaying, 13-9
IAN150/IPP MT
6/30/97
Bisync Operations
monitoring, 13-1
Bisync Port Status and Control, 13-2. See also
Bisync Status
displaying, 13-3
Boot PROM, 2-16
BOOTP Status
displaying, 11-55
BPS Operations. See Burroughs Poll Select
(BPS) Operations
BPS Trap Messages, C-6
BRE Adjacency Table
displaying, 9-22
displaying, 9-18
displaying, 9-17
BRE Port Statistics
displaying, 9-13
BRE Routing Table
displaying, 9-20
BRE Trap Messages, C-4
displaying, 9-25
Bridge Monitoring, 9-1
Bridge Relay Element (BRE) Statistics
adjacency table, 9-22
forwarding table, 9-18
physical port, 9-17
routing table, 9-20
virtual port, 9-13
Bridge Relay Element (BRE) Statistics Menu,
9-12
Bridging Status Menu, 9-2
Bridging Tables Menu, 9-24
IN-1
BSC 3270 Protocol Operations. See Bisync
Operations
BSC Trap Messages, C-5
Buffer Memory
upgrading, A-9
Buffer Memory, IAN-150, 1-11
Build (B) Command, 2-28
Burroughs Poll Select (BPS) Circuit Status
displaying, 14-5
Burroughs Poll Select (BPS) Cleared Circuit
Status
displaying, 14-9
Burroughs Poll Select (BPS) Operations
monitoring, 14-1
Burroughs Poll Select (BPS) Port Status and
Control, 14-2. See also Port Status and
Control
Burroughs Poll Select (BPS) Status
displaying, 14-3
C
Cabinet Mounting, IAN-150, 2-3
Cables, B-1
diagrams of, B-4
Changing Parameter Settings, 2-27, 2-30, 3-6
Chassis Manager Trap Messages, C-7
Chassis Reset (CRS) Command, 2-28
Circuit Clearing, causes of
bisync, 13-10
Burroughs Poll Select (BPS), 14-11
Synchronous Data Link Control (SDLC),
15-13
X.25, 16-12
Circuit Status
bisync
displaying, 13-5
Burroughs Poll Select (BPS)
displaying, 14-5
Synchronous Data Link Control (SDLC)
displaying, 15-7
IN-2
X.25
displaying, 16-7
Clear Circuit (CC) Command, 2-28
bisync
displaying, 13-9
Burroughs Poll Select (BPS)
displaying, 14-9
displaying, 15-11
X.25
displaying, 16-11
Command Line, accessing, 2-28
Commands, D-1
Abort (A), 2-28
Build (B), 2-28
Chassis Reset (CRS), 2-28
Clear Circuit (CC), 2-28
confirmation of, 2-29
Cycle (C), 2-28, 3-6
Delete (D), 2-28, 2-30
Evacuate (E), 2-28
hot keys for, D-1
Install (I), 2-28
IP, 4-2
Main Menu (MAI), 2-28
Monitor (M), 2-28
Monitor (MON), 3-15
Read (R), 2-28, 2-30
Read Next (N), 2-28
Reload Cfg (RLC), 2-28
Reload SW & Cfg (RSC), 2-29
Reload SW (RLS), 2-29
Reset (RES), 2-29
Restart (RST), 2-29
Search (SE), 2-29
Setup Call (SC), 2-29
Shell (SH), 2-29
Station Offline (STF), 2-29
Station Online (STN), 2-29
Submit (SU), 2-29
Switch Active Master (SAM), 2-29
Translate (T), 2-29
Validate (V), 2-29
IAN150/IPP MT
6/30/97
Write (W), 2-29, 2-30
X.28 PAD, 2-25
Community Names Configuration, 4-6
Configuration, 3-1
default, 3-1
fast path parameters, 3-11
node parameters, 3-6
port parameters, 3-10
pseudoport, 5-10
Configuration Menu, 2-22
Configuration Options, 1-2
Configuration Settings
activating, 2-31
changing, 2-30
deleting, 2-30
duplicating, 2-31
entering, 2-30, 3-6
reading, 2-30
Connecting IAN-150
console port to terminal or computer, 2-12, B5
IEEE 802.3 Ethernet interface, 2-13
IEEE 802.5 Token Ring interface, 2-14
serial WAN interfaces, 2-15
Console Port, 1-6
configuration, 3-2
connecting to terminal or computer, 2-12
CPU, IAN-150, 1-11
Crash Dump Procedure, 6-3
Cycle (C) Command, 2-28, 3-6
D
Data Link Switching Operations. See DLSw
Operations
Date and Time, setting on IAN-150, 2-23
D-Channel Status, ISDN
displaying, 18-3
Default Configuration, 3-1
Delete (D) Command, 2-28, 2-30
Deleting Configuration Settings, 2-30
Desktop Mounting, IAN-150, 2-3
Diagnostics, 5-21
codes for
bisync, 13-11
Burroughs Poll Select (BPS), 14-12,
14-13
IAN150/IPP MT
6/30/97
15-14, 15-15
X.25, 16-13
factory, 6-6
port, 5-24, 6-3
self-tests, 5-21
Diagnostics Menu, 2-23
Displaying. See Monitoring
Displays. See Screens
displaying, 10-5
DLSw NetBios Name Caching Table
displaying, 10-7
DLSw Operations
monitoring, 10-1
displaying, 10-2
DLSw Status and Control Menu, 10-1
DLSw Trap Messages, C-4
DRAM. See Dynamic RAM
Duplicating Configuration Settings, 2-31
Dynamic RAM (DRAM), 1-11
upgrading, A-9
E
Echo Function, pseudoport, 5-9
Edit Board Information Menu, A-16
Edit Port MAC Address Screen, A-17
EGP Control and Status Menu, 11-51
EGP Neighbor Table
displaying, 11-53
EGP Statistics
displaying, 11-52
EIA Modem Lead Status
displaying, 3-21
Electrical Specifications, IAN-150, 1-13
Element Management System (EMS),
configuration, 4-8
EMS. See Element Management System
Entering Data, user interface, 2-27, 3-6
IN-3
Environmental Requirements, IAN-150, 1-13
Ethernet Operations
monitoring, 7-1
Ethernet Port, 3-3
connecting to, 2-13
displaying, 7-2
Evacuate (E) Command, 2-28
Expansion Module Slot, 1-3
Expansion Modules, 1-3, A-3
installing, A-3
removing, A-3
EXT (External) Advertisements, OSPF Link
State Database Table, 11-44
F
Factory Diagnostics, 6-6
Factory Test Menu, 6-7
Fast Path Parameters, configuring, 3-11
Frame Relay LAP Port, 3-5
Frame Relay Operations, monitoring, 17-1
displaying, 17-2
displaying, 17-7
displaying, 17-10
Frame Relay Trap Messages, C-6
displaying, 17-4
G
General (Transparent) Bridging Status
displaying, 9-3
H
Hardware Configuration Options, 1-2
Hardware Monitoring, 3-19
IN-4
Hardware Specifications, IAN-150, 1-9
Hardware Type Display, 3-19
Help Screen, 2-24
Hot Keys, listing of, D-1
HTTP Connections
displaying, 11-16
HTTP Protocol Statistics
displaying, 11-15
HTTP Status Menu, 11-14
HTTP Users
displaying, 11-17
I
IAN-150
AC power connections, 1-7
access switching specifications, 1-12
buffer memory, 1-11
cables, B-1
configuration options, 1-2
configuring, 3-1
console port connection to terminal or
computer, 2-12
diagnostics, 5-21
electrical specifications, 1-13
environmental requirements, 1-13
expansion module slot, 1-3
expansion modules, 1-3, A-3
hardware configuration options, 1-2
hardware specifications, 1-9
IEEE 802.3 Ethernet connection, 2-13
IEEE 802.5 Token Ring connection, 2-14
indicators, 1-7
installation procedures, 2-2
LED indicators, 1-7
login procedure, 2-17
loopback connectors, 5-26
memory, 1-11
motherboard, 1-2, 1-11
mounting, 2-3
network management, 4-1
outlet requirements, 1-13
physical specifications, 1-9
port configuration, default, 3-2
ports, physical, 1-6
IAN150/IPP MT
6/30/97
IAN-150 (continued)
power cord requirements, 1-13
powering off, A-2
powering up, 2-11
processor, 1-11
product description, 1-1
routing specifications, 1-12
serial WAN connections, 2-15
software, 2-16
software features, 1-9
start-up procedures, 2-1
system architecture, 1-10
traps, 5-6
user interface description, 2-17
utilities, 5-1
WAN connections, 2-15
ICMP Ping Parameters, 5-2
ICMP Status
displaying, 11-10
IEEE 802.3 Ethernet Connection, 2-13
IEEE 802.5 Token Ring Connection, 2-14
Independent Packet Processor (IPP). See IPP
Indicators, IAN-150, 1-7
Install (I) Command, 2-28
Installation Procedures, 2-2
expansion modules, A-3
SIMM, A-9
WAN personality modules, A-7
Internet Control Message Protocol (ICMP) Ping
Parameters, 5-2
Internet Control Message Protocol (ICMP)
Status. See ICMP Status
Internet Packet Exchange (IPX) Ping Parameters,
5-4
IP Address Table
displaying, 11-9
IP Address, assigning, 3-13
IP Command, 4-2
displaying, 11-6
IP Control and Status Menu, 11-2
IP Port Configuration, assigning IP address, 3-13
IP Status
displaying, 11-4
IP Status Menu, 11-3
IAN150/IPP MT
6/30/97
IP Table Flush, 5-5
IP Trap Messages, C-13
IPP
login procedure, 2-17
loopback connectors, 5-26
software, 2-16
user interface description, 2-17
IPX Ping Parameters, 5-4
IPX Protocol Status
displaying, 12-3
IPX Routing Table
displaying, 12-8
IPX Routing, monitoring, 12-1
IPX Service Advertisement Protocol (SAP)
Status
displaying, 12-6
IPX Service Advertisement Protocol (SAP) Table
displaying, 12-9
IPX Status Menu, 12-2
IPX Table Flush, 5-6
ISDN B-Channel Status and Statistics
displaying, 18-7
ISDN Call History
displaying, 18-16
ISDN D-Channel Status and Statistics
displaying, 18-3
ISDN Destination Status and Statistics
displaying, 18-10
ISDN Operations
monitoring, 18-1
ISDN Status Menu, 18-2
ISDN Trap Messages, C-7
L
LED Indicators, IAN-150, 1-7
Line Trace Procedure, 6-4
Link State Advertisements (LSAs), OSPF, 11-37
AS external (EXT), 11-44
IN-5
network (NET), 11-40
router (RTR), 11-39
STUB, 11-38
type 3 summary (NET SUM), 11-41
type 4 summary (AS SUM), 11-43
LLC Status
displaying, 10-8
Loader, 5-15
Loader Menu, 6-6, A-12, A-14, A-15
Loader Utility, 5-15
Login Procedure, 2-17
using web browser, 2-18
Loopback Connectors
IAN-150, 5-26
IPP, 5-26
LSAs. See Link State Advertisements
M
Main Menu, 2-20
using browser, 2-19
Main Menu (MAI) Command, 2-28
Memory, IAN-150, 1-11
Menus. See also Screens
accessing, 2-20
Bridge Relay Element (BRE) Statistics, 9-12
Bridging Status, 9-2
Bridging Tables, 9-24
Configuration, 2-22
Diagnostics, 2-23
DLSw Status and Control, 10-1
Edit Board Information, A-16
EGP Control and Status, 11-51
Factory Test Menu, 6-7
HTTP Status, 11-14
index of, D-1
IP Control and Status, 11-2
IP Status, 11-3
IP Table Flush, 5-5
IPX Status, 12-2
IPX Table Flush, 5-6
ISDN Status, 18-2
Loader, 6-6, A-12, A-14, A-15
Network Management Configuration Menu,
4-3
OSPF Link State Database Status, 11-37
OSPF Status, 11-30
IN-6
Spanning Tree (STA/P) Status, 9-5
Status and Control Menu, 2-22
Table Flush Utilities, 5-5
TCP Status and Control, 11-18
Telnet Help, 5-21
UDP Status, 11-12
User Interface Main Menu, 2-20
Utilities, 2-22, 5-1
Monitor (M) Command, 2-28
Monitor (MON) Command, 3-15. See also
Monitoring
Monitoring, 3-15
Backup Operations, 19-1
bisync operations, 13-1
bridging operations, 9-1
Burroughs Poll Select (BPS) operations, 14-1
DLSw (data link switching) operations, 10-1
Ethernet operations, 7-1
frame relay operations, 17-1
hardware, 3-19
IPX routing, 12-1
ISDN operations, 18-1
node, 3-15, 5-21
ports, 3-18, 3-19
Simple Network Management Protocol
(SNMP) traps, 5-6
operations, 15-1
TCP/IP operations, 11-1
Token Ring operations, 8-1
X.25 operations, 16-1
Motherboard, 1-2
Motherboard, IAN-150, 1-11
Mounting Procedures, IAN-150
cabinet, 2-3
desktop, 2-3
rack, 2-3
N
NET (Network) Advertisements, OSPF Link
State Database Table, 11-40
NET SUM Advertisements, OSPF Link State
Network Management, 4-1. See also Simple
Network Management Protocol (SNMP)
Network Management Configuration Menu, 4-3
Node Fast Path Configuration, 3-11
IAN150/IPP MT
6/30/97
Node Monitoring, 3-15, 5-21
Node Parameters, configuring, 3-6
Node Status
displaying, 3-15
O
displaying, 11-35
OSPF Link State Database Status Menu, 11-37
OSPF Link State Database Table
external (EXT) advertisements
displaying, 11-44
network (NET) advertisements
displaying, 11-40
router (RTR) advertisements
displaying, 11-39
STUB advertisements
displaying, 11-38
type 3 summary (NET SUM) advertisements
displaying, 11-41
type 4 summary (AS SUM) advertisements
displaying, 11-43
displaying, 11-45
displaying, 11-31
OSPF Status Menu, 11-30
OSPF Trap Messages, C-8
displaying, 11-47
displaying, 11-49
Outlet Requirements, IAN-150, 1-13
IAN150/IPP MT
6/30/97
P
Parameter Settings
activating, 2-31
changing, 2-27, 2-30
deleting, 2-30
duplicating, 2-31
entering, 2-30, 3-6
reading, 2-30
Parameters
(BRE) adjacency table, 9-22
Address Resolution Protocol (ARP) Table,
11-8
backup statistics, 19-2
bisync circuit status, 13-5
bisync cleared circuit status, 13-9
bisync status, 13-3
BOOTP status, 11-55
BRE Forwarding Table, 9-18
BRE physical port statistics, 9-17
BRE port statistics, 9-13
BRE routing table, 9-20
Bridge Forwarding Table, 9-25
Burroughs Poll Select (BPS) circuit status,
14-5
Burroughs Poll Select (BPS) cleared circuit
status, 14-10
Burroughs Poll Select (BPS) status, 14-3
circuit status
bisync, 13-5
15-7
X.25, 16-7
cleared circuit status
bisync, 13-9
15-11
X.25, 16-11
community name, 4-6
default, 3-1
DLSw Connection Summary, 10-5
DLSw NetBios Name Caching Table, 10-7
DLSw port statistics, 10-3
EGP neighbor table, 11-53
EGP statistics, 11-52
EIA modem lead status, 3-22
IN-7
Parameters (continued)
Element Management System (EMS), 4-9
Ethernet port status, 7-2
fast path configuration, 3-11
frame relay port status, 17-2
frame relay PVC status, 17-7
frame relay route topology status, 17-10
frame relay virtual trunk status, 17-5
hardware type, 3-20
HTTP connections, 11-16
HTTP protocol statistics, 11-15
HTTP users, 11-17
ICMP status, 11-10
Internet Control Message Protocol (ICMP)
Ping, 5-2
IP Address Table, 11-9
IP common routing table, 11-7
IP port configuration, 3-13
IP status, 11-4
IPX protocol status, 12-3
IPX routing table, 12-8
IPX service advertisement protocol (SAP)
status, 12-6
IPX service advertisement protocol (SAP)
table, 12-9
ISDN B-channel status and statistics, 18-7
ISDN call history, 18-16
ISDN D-channel status and statistics, 18-3
ISDN destination status and statistics, 18-11
LLC status, 10-8
node configuration, 3-6
node status, 3-16
OSPF Interface Data Table, 11-35
external (EXT) advertisements, 11-44
network (NET) advertisements, 11-40
router (RTR) advertisements, 11-39
STUB advertisements, 11-38
type 3 summary (NET SUM)
advertisements, 11-42
type 4 summary (AS SUM)
advertisements, 11-43
OSPF Neighbor Data Table, 11-45
OSPF Protocol Status, 11-32
OSPF Virtual Link Data Table, 11-47
OSPF Virtual Neighbor Data Table, 11-49
port configuration, 3-10
port diagnostics, 5-25
port status, 3-18
IN-8
Parameters (continued)
pseudoport circuit configuration, 5-11
pseudoport operation, 5-13
pseudoport port configuration, 5-10
RIP Status, 11-29
SDLC station status, 15-3
Source Route Encapsulation Table, 9-26
spanning tree port status, 9-9
spanning tree protocol status, 9-6
SR-TB Translation Table, 9-28
circuit status, 15-7
cleared circuit status, 15-11
system group, 4-4
TCP connection statistics, 11-23
TCP Connection Table, 11-21
TCP receive statistics, 11-25
TCP standard statistics, 11-19
TCP transmit statistics, 11-27
trap filtering, 4-9
trap output, 4-7
UDP Listen Table, 11-14
UDP statistics, 11-13
X.25 circuit status, 16-7
X.25 cleared circuit status, 16-11
X.25 status, 16-4
Physical Ports, IAN-150, 1-6
Physical Specifications, IAN-150, 1-9
Ping Parameters
ICMP, 5-2
IPX, 5-4
Ping Utility, 5-2
Port Diagnostics, 6-3
Port Diagnostics Screen, 5-25
Port Monitoring, 3-18
Port Parameters, configuring, 3-10
displaying, 3-18, 5-20
Port Trap Messages, C-2
Ports
3270 Bisync, 3-5
console, 3-2
diagnostics, 5-24, 6-3
Ethernet, 3-3
frame relay LAP, 3-5
IAN-150, 1-6
number limitations of, 3-10
IAN150/IPP MT
6/30/97
SDLC TPAD, 3-4
serial WAN, 3-3
Token Ring, 3-2
Power Connections, IAN-150, 1-7
Power Cord Requirements, IAN-150, 1-13
Powering Off, IAN-150, A-2
Powering Up, IAN-150, 2-11
Processor, IAN-150, 1-11
PROCOMM, 2-17
Product Description, IAN-150, 1-1
Pseudoport Circuit Configuration, 5-10
Pseudoport Operation, 5-13
Pseudoport Port Configuration, 5-10
Pseudoport Utility, 5-7
echo function, 5-9
sink function, 5-9
traffic generator function, 5-8
user interface, 5-8
R
Rack Mounting, IAN-150, 2-3
Read (R) Command, 2-28, 2-30
Read Next (N) Command, 2-28
Reload Cfg (RLC) Command, 2-28
Reload SW & Cfg (RSC) Command, 2-29
Reload SW (RLS) Command, 2-29
Removing
Replacing
SIMM, A-9
Reset (RES) Command, 2-29
Restart (RST) Command, 2-29
RIP Status
displaying, 11-29
Router (RTR) Advertisements, OSPF Link State
Routing Specifications, IAN-150, 1-12
RTR (Router) Advertisements, OSPF Link State
IAN150/IPP MT
6/30/97
S
Screens. See also Menus
accessing, 2-20
Address Resolution Protocol (ARP) Table,
11-8
Backup Statistics, 19-2
Bisync Status, 13-3
BOOTP Status, 11-55
BRE Adjacency Table, 9-22
BRE Forwarding Table, 9-18
BRE Physical Port Statistics, 9-17
BRE Port Statistics, 9-13
BRE Routing Table, 9-20
Bridge Forwarding Table, 9-25
Burroughs Poll Select (BPS) Status, 14-3
changing parameter settings, 2-27, 3-6
Circuit Status
bisync, 13-5
15-7
X.25, 16-7
bisync, 13-9
15-11
X.25, 16-11
commands for, D-1
Community Name Configuration, 4-6
DLSw Connection Summary, 10-5
DLSw NetBios Name Caching Table, 10-7
DLSw Port Statistics, 10-2
Edit Port MAC Address, A-17
EGP Neighbor Table, 11-53
EGP Statistics, 11-52
EIA Modem Lead Status, 3-21
Element Management System Configuration,
4-8
entering data, 2-27, 3-6
Ethernet Port Status, 7-2
Frame Relay Port Status, 17-2
Frame Relay PVC Status, 17-7
Frame Relay Route Topology Status, 17-10
Frame Relay Virtual Trunk Status, 17-4
General (Transparent) Bridging Status, 9-3
Hardware Type Display, 3-19
IN-9
Screens (continued)
Help, 2-24
HTTP Connections, 11-16
HTTP Protocol Statistics, 11-15
HTTP Users, 11-17
IAN-150 title screen using browser, 2-18
ICMP Ping Parameters, 5-2
ICMP Status, 11-10
index of, D-1
IP Address Table, 11-9
IP Common Routing Table, 11-6
IP Port Configuration, 3-13
IP Status, 11-4
IPX Ping Parameters, 5-4
IPX Protocol Status, 12-3
IPX Routing Table, 12-8
Status, 12-6
Table, 12-9
ISDN B-Channel Status and Statistics, 18-7
ISDN Call History, 18-16
ISDN D-Channel Status and Statistics, 18-3
ISDN Destination Status and Statistics, 18-10
LLC Status, 10-8
Loader, 5-15
Main Menu, 2-20
Main Menu (Browser), 2-19
Node Fast Path Configuration, 3-11
Node Parameter Configuration, 3-6
Node Status, 3-15
OSPF Interface Data Table, 11-35
AS SUM, 11-43
EXT type, 11-44
NET SUM type, 11-41
NET type, 11-40
RTR type, 11-39
STUB type, 11-38
OSPF Neighbor Data Table, 11-45
OSPF Protocol Status, 11-31
OSPF Virtual Link Data Table, 11-47
OSPF Virtual Neighbor Data Table, 11-49
Port Diagnostics, 5-25, 6-3
Port Status and Control, 3-18, 5-20
Pseudoport Circuit Configuration, 5-10
Pseudoport Operation, 5-13
Pseudoport Port Configuration, 5-10
RIP Status, 11-29
IN-10
Screens (continued)
SDLC Station Status, 15-3
SNMP Trap Display, 5-6
Source Route Encapsulation Table, 9-26
Source Routing Bridging Status, 9-10
Spanning Tree Port Status, 9-8
Spanning Tree Protocol Status, 9-6
SR-TB Translation Table, 9-28
System Group Configuration, 4-4
TCP Connection Statistics, 11-23
TCP Connection Table, 11-21
TCP Receive Statistics, 11-25
TCP Standard Statistics, 11-19
TCP Status and Control, 11-18
TCP Transmit Statistics, 11-27
templates, 3-6
Time, 2-23
Token Ring Port Status, 8-2
Trap Output Configuration, 4-7
UDP Listen Table, 11-13
UDP Statistics, 11-12
User Interface Main Menu, 2-20
VxWorks Shell Access, 6-3
X.25 Status, 16-4
X.28 help, 2-25
X.28 status, 2-26
SDLC Circuit Status
displaying, 15-7
SDLC Cleared Circuit Status
displaying, 15-11
SDLC Operations
monitoring, 15-1
SDLC Port Status and Control, 15-2. See also
SDLC Station Status
displaying, 15-3
SDLC TPAD Port, 3-4
SDLC Trap Messages, C-5
Search (SE) Command, 2-29
Self-Tests, IAN-150, 5-21
Serial WAN Port, 3-3
connecting to, 2-15
Setup Call (SC) Command, 2-29
Shell (SH) Command, 2-29
SIMM, installing, A-9
IAN150/IPP MT
6/30/97
Simple Network Management Protocol (SNMP),
4-1
configuring, 4-3
community names, 4-6
Element Management System stations, 4-8
system group parameters, 4-4
trap filters, 4-9
trap output addresses, 4-7
traps, monitoring, 5-6
Sink Function, pseudoport, 5-9
SNMP. See Simple Network Management
Protocol
SNMP Trap Display, 5-6, 6-2
Software, 2-16
upgrading, A-11
Software Features, IAN-150, 1-9
Source Route Bridging Status
displaying, 9-10
displaying, 9-26
Source Route-Transparent Bridging. See SR-TB
Translation Table
Spanning Tree (STA/P) Status Menu, 9-5
displaying, 9-8
displaying, 9-6
Specifications
physical, 1-9
Specifications, IAN-150
access switching and routing, 1-12
electrical, 1-13
environmental requirements, 1-13
memory, 1-12
processor, 1-12
SR Bridging Status. See Source Route Bridging
Status
displaying, 9-28
STA/P, 9-5
Start-Up Procedures, IAN-150, 2-1
Station Offline (STF) Command, 2-29
Station Online (STN) Command, 2-29
Statistics
Bridge Relay Element (BRE), 9-12
IAN150/IPP MT
6/30/97
DLSw port, 10-2
Ethernet port, 7-2
IP, 11-4
Status and Control Menu, 2-22
STUB Advertisements, OSPF Link State
Submit (SU) Command, 2-29
Summary Advertisements, OSPF Link State
Database Table
AS SUM, type 4, 11-43
NET SUM, type 3, 11-41
Switch Active Master (SAM) Command, 2-29
Synchronous Data Link Control Operations. See
SDLC Operations
Synchrony IAN-150. See IAN-150
System Architecture, IAN-150, 1-10
System Group Configuration, 4-4
System Trap Messages, C-2
T
Table Flush Utility, 5-5
IP, 5-5
IPX, 5-6
TALK Terminal Emulation Program, 2-16
upgrading IAN-150 software, A-11
TCP Connection Failure Codes, 10-3
TCP Connection Statistics
displaying, 11-23
TCP Connection Table
displaying, 11-21
displaying, 11-25
TCP Standard Statistics
displaying, 11-19
TCP Status and Control Menu, 11-18
displaying, 11-27
TCP, configuring, 3-15
TCP/IP Operations, monitoring, 11-1
TELNET, 5-19
Telnet Help Menu, 5-21
Templates, 3-6
IN-11
TFTP Error Codes, 5-17
Time and Date, setting on IAN-150, 2-23
Time Screen, 2-23
Token Ring Operations
monitoring, 8-1
Token Ring Port, 3-2
connecting to, 2-14
displaying, 8-2
Traffic Generator Function, pseudoport, 5-8
Translate (T) Command, 2-29
Transparent Bridging Status
displaying, 9-3
Trap Filtering, 4-9
Trap Messages, C-1
BPS, C-6
BRE, C-4
BSC, C-5
Chassis Manager, C-7
DLSw, C-4
frame relay, C-6
IP, C-13
ISDN, C-7
OSPF, C-8
port, C-2
SDLC, C-5
system, C-2
X.25, C-5
Trap Output Configuration, 4-7
Traps, displaying, 5-6
Trivial File Transfer Protocol (TFTP)
error codes, 5-17
parameters
download/upload, 5-15
Troubleshooting, 6-1
Backup operations, 19-1
bisync operations, 13-1
Burroughs Poll Select (BPS) operations, 14-1
crash dump procedure, VxWorks, 6-3
DLSw (data link switching) operations, 10-1
Ethernet operations, 7-1
factory diagnostics, 6-6
initial evaluation procedure, 6-1
ISDN operations, 18-1
line trace procedure, VxWorks, 6-4
port diagnostics, 6-3
preventive maintenance, 6-5
SNMP trap display, 6-2
IN-12
operations, 15-1
Token Ring operations, 8-1
X.25 operations, 16-1
U
UDP Listen Table
displaying, 11-13
UDP Statistics
displaying, 11-12
UDP Status Menu, 11-12
Upgrading
dynamic RAM (DRAM), A-9
software, A-11
User Access Levels, 2-19
User Datagram Protocol (UDP) Status, 11-12
User Interface, 2-17
commands, 2-28, D-1
main menu, 2-19, 2-20
Utilities, 5-1
loader, 5-15
ping, 5-2
ICMP, 5-2
IPX, 5-4
pseudoport, 5-7
table flush, 5-5
TELNET, 5-19
Utilities Menu, 2-22, 5-1
V
Validate (V) Command, 2-29
Viewing Ping Response, ICMP, 5-3
VxWorks Shell Access Screen, 6-3
W
WAN Connections, 2-15
WAN Personality Modules, 1-8
installing, A-7
removing, A-7
WAN Port, 1-6, 3-3
Web Browser, login procedure, 2-18
WPM. See WAN Personality Modules
IAN150/IPP MT
6/30/97
Write (W) Command, 2-29, 2-30
X
X.25 Circuit Status
displaying, 16-7
X.25 Cleared Circuit Status
displaying, 16-11
IAN150/IPP MT
6/30/97
X.25 Operations
monitoring, 16-1
X.25 Port Status and Control, 16-2. See also
X.25 Status
displaying, 16-4
X.25 Trap Messages, C-5
X.28, 3-12
X.28 Help Screen, 2-25
X.28 Status Screen, 2-26
IN-13
NOTE:
The regulatory information contained in this section applies to the
Synchrony IAN-150. For regulatory information relating to the
Independent Packet Processor (IPP) module, refer to the
Synchrony ST-1000/ER-5 Internetworking Installation and
Maintenance Manual.
This section contains regulatory information for geographical areas that require specific text to
appear in the manual documentation. This equipment has been approved for use in areas other
than those listed in this section. For areas not listed below, regulatory requirements and approvals
information can be obtained from your local Ascom Timeplex office.
The information in this section includes mandatory or recommended requirements of certification
authorities for the following areas:
•
Canada
•
Europe
•
United States
NOTE:
IAN150MT
6/30/97
All ports on this equipment are Safe Extra Low Voltage (SELV)
unless otherwise noted and should only be connected to SELV
ports on other equipment.
REG-1
Canada
Telephone Line Connection Information
The Canadian Department of Communications label identifies certified equipment. This
certification means that the equipment meets certain telecommunications network protective,
operational, and safety requirements as prescribed in the appropriate Terminal Equipment
Technical Requirements documents. The department does not guarantee the equipment will
operate to the user’s satisfaction.
Before installing this equipment, users should ensure that it is permissible to be connected to the
facilities of the local telecommunications company. The equipment also must be installed using
an acceptable method of connection. The customer should be aware that compliance with the
above conditions may not prevent degradation of service in some situations.
Repairs to certified equipment should be coordinated by a representative designated by the
supplier. Any repairs or alterations made by the user to this equipment, or equipment
malfunctions, may give the telecommunications company cause to request the user to disconnect
the equipment.
Users should ensure for their own protection that the electrical ground connections of the power
utility, telephone lines, and internal metallic water pipe systems, if present, are connected
together. This precaution may be particularly important in rural areas.
CAUTION:
Users should not attempt to make such connections themselves,
but should contact the appropriate electric inspection authority,
or electrician, as appropriate.
The required connection arrangement (telephone jack) for this product is CB1D.
Canadian Compliance Statement
This digital apparatus does not exceed the Class A limits for radio noise emissions from digital
apparatus set out in the Radio Interference Regulations of the Canadian Department of
Communications.
Le présent appareil numérique n’émat pas de bruits radioélectriques dépassant les limites
applicables aux appareils numériques de la classe A prescrites dans le Réglement sur le
brouillage radioélectrique édicté par le ministère des Communications du Canada.
IAN150MT
6/30/97
CAN-1
Europe
General Pan-European Requirements
With the harmonization of Telecommunications in Europe, the connection of Terminal
Equipment to the Public Telecommunications Networks, is regulated by Directives issued by the
European Commission. Public Telecommunication Network Services provided to Terminal
Equipment users may be supplied as a National Service, with interface standards specific to the
country in which it is provided, or as a Pan-European Service, with a common interface standard
throughout all European countries.
In this section, it is stated which product interfaces are compatible with the National and which
with the Pan-European standards. In principle, products with the CE markings are intended for
use in any European country. But, in practice, products with multiple interfaces require a clearer
definition of their compatibility with the public network.
CE Marked Equipment
Certain Ascom Timeplex equipment is marked with one of the following:
The equipment, when correctly installed in accordance with the user
manual instructions, meets the requirements of the European
Electromagnetic and Low Voltage Directives.
Electromagnetic, Low Voltage, and Telecommunications Terminal
Directive, and may be connected to the Public Telecommunications
Networks of the European Union Countries.
Electromagnetic, Low Voltage, and Telecommunications Terminal
Directive, but cannot be connected to the pan-European Public
Telecommunications Networks of the European Union Countries.
Where ❒ is a National Approval Label, implies the equipment, when
correctly installed in accordance with the user manual instructions,
meets the requirements of the European Electromagnetic and Low
Voltage Directives, and in addition has been granted Public Network
Attachment Approval in those countries whose labels are affixed.
NOTE:
IAN150MT
6/30/97
Refer to the country-specific sections of this regulatory section to
determine the National Attachment Approvals granted to the
equipment.
EUR-1
Ascom Timeplex has endeavored to undertake the mandatory "TYPE APPROVAL TESTING"
of Public Network Interfaces on their products to both Pan-European and selected countryspecific requirements. Certificates and reports permitting the CE marking of the products "Placed
On The European Market" and the Public Network Attachment Approval Certificates associated
with National Interfaces are held on file by the company. Please contact Ascom Timeplex for
further information.
NOTICE
PUBLIC NETWORK ATTACHMENT APPROVAL HAS BEEN GRANTED ON THE
BASIS THAT THE EQUIPMENT IS IDENTICAL TO THAT CERTIFIED DURING
"TYPE APPROVAL TESTING". USERS MUST ENSURE CONFIGURATION AND
INSTALLATION IS PERFORMED IN ACCORDANCE WITH THE USER MANUAL
INSTRUCTIONS, AND USING THE SPECIFIED APPROVED CABLES.
Declaration of Comformity
In association with the CE marking of the product, Ascom Timeplex declares under its sole
responsibility that the product known as the Synchrony IAN-150 is in conformity with the
following Directives and standards. An official copy of the Declaration of Comformity is
available upon request.
European Low Voltage Directive
Telecommunications Terminal Equipment Directive
Electromagnetic Compatibility Directive
CE Marking Directive
EN 60950:1992
EN 55022:1987 Class A
EN 50082-1
IEC 801-2: 1991
IEC 801-3: 1984
IEC 801-4: 1991
NET.1 / I- CTR 1
NET.2 / I- CTR 2
NET.2 / I- CTR 2
NET.3 / I- CTR 3
CSE P 10 - 20A
CSE P 10 - 21A
BAPT 223 ZV 25
EUR-2
(LVD)
(TTE)
(EMC)
(CEM)
73/ 23/EEC
91/263/EEC
89/336/EEC
93/ 68/EEC
Safety of information technology equipment, & electrical business equipment
Limits of radio disturbance characteristics of IT equipment, Class A
Immunity characterstics: Residential, Commercial, & Light Industry
Electrostatic Discharge
Radiated Electromagnetic Field
Electrical Fast Transients / burst requirements
X.21 Point to Point Digital Leased Lines (X.21 / V.11)
X.21 bis Point to Point Digital Leased Lines (V.24 / V.28, V.35, V.36 / V.11)
X.25 Public Packet Switched Services
ISDN Basic Rate Access
ISDN Liste des exigences complimentaires applicables aux NET.3 et NET.5
ISDN Liste des exigences complimentaires applicables aux NET.3 et NET.5
ISDN German deviations to NET.3 and NET.5
IAN150MT
6/30/97
Regulatory Guidance
It is considered a criminal offense to install Telecommunications Terminal Equipment which is
not approved, or to install it in a non-compliant manner. Advice should be obtained from a
competent Engineer BEFORE making Public Network Connections.
European Telecommunications Regulatory legislation is concerned mainly with the following
aspects of connection to Public Telecommunications Networks:
1. That all equipment in a Network connected directly or indirectly to a public network is
approved, and appropriately marked to show this.
2. That all equipment connected directly to a Public Network is approved for connection to the
service concerned.
3. That any equipment connected directly to the Public Network does not present hazardous
conditions to the network or place the user at risk from hazards present on the Public
Network.
4. That the equipment used as a direct or indirect attachment to the Public Network does not
affect the integrity of that Public Network.
5. That networks installed in one country, but linked to international circuits, comply with
international agreements.
6. That the equipment, approved for operation under certain conditions, and connected in an
acceptable manner to the Public Network, is used in accordance with suitable user
installation and operating instructions supplied with the equipment.
Principles of Product Attachment Approval Requirements
The Public Network Attachment Approval of this equipment shall be invalidated in the event of
the connection of any apparatus or cabling which does not comply with the following:
1. Digital attachments to PTO Services shall be equipment approved for the purpose in which
they are being used.
2. Attachments shall not materially affect the electrical performance characteristics of the
interface to the PTO service.
3. All cables and wiring shall be compliant with appropriate codes of practice and relevant
standards.
4. Apparatus approved for connection to PTO services must be connected to the Network
Termination Point (NTP) using the approved listed cable or an alternate cable meeting the
electrical characteristics of the Ascom Timeplex specified cable.
5. National requirements may restrict the carrying or interfacing of speech derived from, or
destined for the PSTN.
IAN150MT
6/30/97
EUR-3
Safety Information and Warnings
This equipment is only approved for use when operated in the following environment:
•
Temperature Range: 0° to 45°C
•
Humidity: To 90% (noncondensing)
•
Atmospheric Pressure: 10,000 feet (3050 meters)
•
Power Input Range: 100 to 230 VAC, 50/60 Hz
WARNINGS: THIS EQUIPMENT HAS BEEN CERTIFIED COMPLIANT
WITH EN55022 CLASS A ELECTROMAGNETIC
EMISSIONS STANDARDS, AND IS SUITABLE FOR USE IN
COMMERCIAL AND LIGHT INDUSTRIAL
ENVIRONMENTS WHEN INSTALLED IN ACCORDANCE
WITH THE USER INSTRUCTIONS.
THIS EQUIPMENT IS NOT APPROVED FOR USE IN
PARTICULARLY DAMP ENVIRONMENTS WHERE WATER
OR MOISTURE IS PREVALENT.
THIS EQUIPMENT MUST BE CONNECTED TO A
PROTECTIVE EARTH IN ACCORDANCE WITH THE
INSTRUCTIONS WITHIN THE MAINTENANCE AND
TROUBLESHOOTING MANUAL. IMPROPER EARTHING
MAY RESULT IN AN ELECTRICAL SHOCK HAZARD.
THIS EQUIPMENT DOES NOT PROVIDE SAFETY
ISOLATION BETWEEN ITS PORTS. HAZARDOUS
CONDITIONS IMPOSED AT A PORT MAY RESULT IN
HAZARDOUS CONDITIONS ON OTHER PORTS.
INTERCONNECTION DIRECTLY OR BY WAY OF OTHER
APPARATUS OF ANY EQUIPMENT NOT COMPLIANT
WITH EN60950/EN41003 TO ANY PORT ON THIS
EQUIPMENT MAY PRODUCE HAZARDOUS CONDITIONS
ON THE NETWORK AND, THEREFORE, ADVICE SHOULD
BE OBTAINED FROM A COMPETENT ENGINEER
BEFORE SUCH CONNECTIONS ARE MADE.
EUR-4
IAN150MT
6/30/97
Eurocables
With the advent of Pan-European Public Network Interface Standards, Ascom Timeplex
Equipment is approved for connection to European Public Networks using standard cables
applicable to the European Marketplace. These cables form part of the Attachment Approval and
should be ordered using their associated Part Numbers.
To maintain full compliance with the Interface specifications, attention is drawn to the maximum
and minimum lengths, and baud rates specified on some interfaces which are known to be fully
compliant. Reference should be made to ITU-T (formerly CCITT) documents which recommend
the expected relationship between length and baud rate for reliable operation.
Refer to Table R-1 for a listing of the cables used to interconnect product to the Public Network
Interface.
Ascom Timeplex has taken into account the following aspects of cable design to ensure
compliance with European legislation applicable to equipment used in "Commercial and Light
Industrial" environments:
•
Impedance/meter
•
Transition rise times
•
EMC earthing practices
•
Emissions characteristics
•
Interface connections
•
Screen coverage/type
•
Immunity to interference
•
Connector screening
•
Capacitance/meter
•
Balance about earth
•
Connector type
•
Safety earthing aspects
CAUTION:
IAN150MT
6/30/97
Before installing the equipment in other environments, or using
alternative cabling, the advice of a competent Engineer should
be taken.
EUR-5
Pan-European Public Network Certification
Table R-1 lists Ascom Timeplex equipment that has received pan-European public network
certification.
Table R-1. Pan-European Public Network Certification
Public Network Interface
Standard
CTR 1
X.21/V.11
Digital Leased Lines
CTR 2
V.24/V.28
CTR 2
V.35
CTR 2
V.36/V.11
CTR 1 & CTR 2
V.24/V.28, V.35,
V.36/V.11, X.21/V.11
Ascom Timeplex
Certified Modules
Personality Module Type V.11,
Part No. 100268-1
Personality Module Type V.28
DTE, Part No. 100255-1
Public Network Interface Cable
25M - 15M, D-type,
Part No. 612270-1 to -4*
Part No. 100257-1
DTE - DCE
25M - 25M, D-type,
Part No. 100898-1 to -4*
With V.54: 25M - 34M, MRAC,
Part No. 100919-1 to -4*
Part No. 100268-1
25M - 37M, D-type,
Part No. 612269-1 to -4*
Supplementary WAN Interface
Appropriate cables as specified
Module, Part No. 116230-1, and
above
the above listed Personality
Modules
CTR 3
Basic Rate ISDN Module,
RJ45 - RJ45,
Basic Rate ISDN
Part No. 116229-2
Part No. 612260-1 to -2*
*Cable length is indicated by a suffix in the part number. The following suffixes are used:
-1 = 6 ft
-2 = 15 ft
-3 = 31 ft
-4 = 50 ft
German National Attachment Approvals
Table R-2 lists Ascom Timeplex equipment that has been granted German national attachment
approvals.
Table R-2. German National Attachment Approvals
Public Network
Interface Standard
Euro-ISDN
German Deviations
Ascom Timeplex
Certified Modules
ISDN Module,
Part No. 116229-2
RJ45 - RJ45,
Part No. 612260-1 to -2*
-1 = 6 ft
-2 = 15 ft
EUR-6
IAN150MT
6/30/97
French National Attachment Approvals
Table R-3 lists Ascom Timeplex equipment that has been granted French national attachment
approvals.
Table R-3. French National Attachment Approvals
Public Network
Ascom Timeplex
Interface Standard
Certified Modules
Euro-Numeris ISDN
Basic Rate ISDN Module
RJ45 - RJ45
French Deviations
Part No. 116229-2
Part No. 612260-1 & -2*
-1 = 6 ft
-2 = 15 ft
IAN150MT
6/30/97
EUR-7
United States
WARNING
This device complies with Part 15 of the FCC Rules. Operation is subject to the
following two conditions: (1) This device may not cause harmful interference, and (2)
this device must accept any interference received, including interference that may
cause undesirable operation. In accordance with FCC Part 15 Subpart B requirements,
changes or modifications made to this equipment not expressly approved by Ascom
Timeplex could void user’s authority to operate this equipment.
Radio Frequency Interference
This equipment has been tested and found to comply with the limits for a Class A digital device,
pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial environment. This
equipment generates, uses, and can radiate radio frequency energy and, if not installed and used
in accordance with the instruction manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential area is likely to cause harmful
interference in which case the user will be required to correct the interference at the user’s own
expense.
General Information Regarding the Use
of Customer-Provided Telephone Equipment
FCC regulations and telephone company procedures prohibit connection of customer-provided
equipment to telephone company-provided coin service (central office implemented systems).
Connection to party lines service is subject to State tariffs.
The goal of the telephone company is to provide you with the best service it can. To do this, it
may occasionally be necessary for them to make changes in their equipment, operation, or
procedures. If these changes might affect your service or the operation of your equipment, the
telephone company will give you notice, in writing, to allow you to make any changes necessary
to maintain uninterrupted service.
If you have any questions about your telephone line, such as how many pieces of equipment you
can connect to it, the telephone company will provide this information upon request.
In certain circumstances, it may be necessary for the telephone company to request information
from you concerning the equipment that you have connected to your telephone line. Upon
request of the telephone company, you must provide the FCC registration number of the
equipment that is connected to your line. The FCC registration number is listed on the equipment
label.
If this equipment causes harm to the telephone network, the telephone company will notify you
in advance that temporary discontinuance of service may be required. If advance notice is not
practical, the telephone company will notify the customer as soon as possible. Also, you will be
advised of your right to file a complaint with the FCC if you believe it is necessary.
IAN150MT
6/30/97
US-1
Federal Communication Commission
Part 68 Registration Information
Table R-4. Telecom Interface Port Codes
Manufacturer’s Port
Identifier
Facility Interface
Codes
Service Order
Code
Network Jacks
IAN-150 ISDN BRI
Interface Board
02IS5
6.0N
Not Applicable
If Problems Arise
If trouble is experienced with this equipment, please contact Ascom Timeplex Customer Support
at (800) 237-6670 for repair and/or warranty information. If the trouble is causing harm to the
telephone network, the telephone company may request that you remove the equipment from the
network until the problem is resolved.
The following repairs may be done by the customer: None.
This equipment cannot be used on telephone company-provided coin service. Connection to
Party Line Service is subject to state tariffs.
In the event repairs are ever needed on this equipment, they should be performed by Ascom
Timeplex, Inc., or an authorized representative of Ascom Timeplex, Inc. For information contact:
Ascom Timeplex, Inc.
16255 Bay Vista Drive
Clearwater, Florida 34620
1-800-237-6670
US-2
IAN150MT
6/30/97

Synchrony IAN-150/IPP Maintenance and Troubleshooting Manual

Transcription

Similar documents

Napoleon Container Terminal

Subcutaneous Port Catheter (Port, porta

January 17, 2011 - Village of Port Clements

PDF 1mb - Marina Adelaide

the perfect condo in port aransas!

JAY A. FERNANDO Vice-President Strategic Planning

#104 300 Klahanie Drive • Port Moody

The project incorporates two types of new architecture

July, 1993 - Stumpf Welding Supplies

PA NEWS - Port Authority Retirees Association, Inc.