NETWORK EQUIPMENT TECHNOLOGIES, INC. (hereinafter referred to as "N.E.T."), PROVIDES THIS
DOCUMENT AS IS, WITHOUT WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY AND FITNESS
FOR A PARTI C ULAR PURPOSE.
No part of this publication may be stored in a retrieval system, transmitted or reproduced in any way, including photocopy, photograph, magnetic, or other record, without the prior written permission of N.E.T. Unpublished-rights
reserved under the copyright laws of the United States.
Trademarks
The N.E.T. logo, PanaVue, PrimeSwitch, Promina, SCREAM, Service Creation Manager, and SHOUTIP are
registered trademarks, and CellXpress, FrameXpress, Frame Relay Exchange, IPNX, LAN/WAN Exchange, Network
Equipment Technologies, N.E.T., the net.com logo, net.com, netMS, PortExtender, PrimeVoice, SCREAMvue, and
SHOUT are trademarks of Network Equipment Technologies, Inc.
SunOS and Solaris software copyright is held by Sun Microsystems, Inc. Sun Microsystems is a registered trademark
and Sun, SunOS, OpenWindows, Solaris, and Ultra are trademarks of Sun Microsystems, Inc. UNIX is a registered
trademark of The Open Group.
All other trademarks and registered trademarks are the sole property of their respective owners.
This document constitutes the sole Specifications referred to in N.E.T.'s Product W arranty for the products or services
described herein. N.E.T.’s Product Warranty is subject to all the conditions, restrictions, and limitations contained
herein and in the applicable contract. N.E.T. has made reasonable efforts to verify that the information in this document is accurate, but N.E.T. reserves the right to correct typographical errors or technical inaccuracies. N.E.T.
assumes no responsibility for any use of the information contained in this document or for any infringement of patents or other rights of third parties that may result from the use of this document. Networking products cannot be
tested in all possible uses, configurations or implementations, and interoperability with other products cannot be
guaranteed. The customer is solely responsible for verifying the suitability of N.E.T.'s products for use in its network.
Local market variations may apply. This document is subject to change by N.E.T. without notice as additional information is incorporated by N.E.T. or as changes are made by N.E.T. to hardware or software.
U.S. Government Rights, Government Use rs
The software accompanying this documentation is furnished under a license and may only be used in accordance with
the terms of such license. This documentation is "commercial computer software documentation" as that term is used
in 48 CFR 12.212. Unless otherwise agreed, use, duplication, or disclosure of this documentation and any related
software by U.S. Government civilian agencies is subject to restrictions as set forth in 48 CFR 52.227-14 (ALT III)
and 48 CFR 52.227-19, and use, duplication, or disclosure by the U.S. Department of Defense is subject to restrictions as set forth in 48 CFR 227.7202-1(a) and 48 CFR 227.7202-3(a) or, if applicable, 48 CFR 252.2277013(c)(1)(ii) (OCT 1988).
Released
November 2009
Network Equipment Technologies, Inc.
This document provides information about PX modules within the
Promina Multiservice Access Platform. This document is for use in the
installation and management of the PX packet processing module.
This document assumes that the user has a working knowledge of data
communications, frame relay , integrated services digita l network (ISDN)
and basic trunking and transmission concepts. The user also needs to be
aware of the hazards associated with electronic equipment and electricity ,
a detail discussion of which is beyond the scope of this document. The
VxWorks™ software was developed from Wind River Systems, Inc.
Document Organization
The document contains the following sections:
SectionTitleDescription
Chapter 1OverviewDescribes thePX3 platforms used in
the Promina Series of products.
Chapter 2Module InstallationDescribes how to install the front and
rear cards into the shelves.
Chapter 3Module DescriptionDescribes the PX3 platform,
including an example of the front and
rear cards and information on front
panel status indicators, jumpers and
switch settings.
Chapter 4Database
Installation
Chapter 5TroubleshootingDescribes the troubleshooting, file
Chapter 6Operator Interface
Command
Summary
Appendix APX3 Operating
System and
Applications
Describes installing cards in the
configuration database through the
Operator Interface, including a
description of card and port
parameters.
operations, card replacement
procedures.
Contains a summary of the Operator
Interface commands used in the
configuration of modules described
in this manual.
Describes the PX platform Operating
System and Bootstrap Program.
If there is a problem installing or using N.E.T. products, call N.E.T.
Technical Assistance Center (TAC) at the following numbers:
For North America, call 1.800.800.4638
For International collect calls, use 1.703.948.7999
TAC engineers are available by telephone 24 hours a day, seven days a
week. Warranty and contract customers receive first consideration in the
scheduling of technical resources.
Before contacting TAC for help, review and verify the provisions
contained in your warranty or contract. Depending on those provisions,
there might be a charge for service.
When authorized, TAC engineers can diagnose most network problems
remotely, using dial-up connections. When a service technician is
required, TAC will dispatch the nearest N.E.T. or third-party service
engineer.
Note: Technical problems can be diagnosed and resolved more quickly if you
have remote access, such as a dial-in modem. Use a modem rated at 9600bps
or greater, or an ISDN connection, for dial-in N.E.T. TAC support and incoming
PPP connections. For other remote access methods, contact N.E.T. TAC.
The PX3 platform is an integrated packet-switching module for the
N.E.T. Promina Series Multiservice Access Platform nodes. The PX3
platform provides packet-switched services over a wide area network and
is the engine that drives the N.E.T. packet-over-circuit architecture.
This chapter provides an overview of the PX3 platform which consist of a
front and a rear interface card. The sections in this chapter describing the
PX platform, applications, and Promina software are:
PX3 cards deliver high throughput for frame- and packet-switched traffic.
The PX3 ports handle input/output packet data. By transmitting multiple
frames in parallel, the PX3 card increases the efficiency of input/output to
the wide area network. The PX3 platform consists of a front card and
optional rear interface cards. The PX3 front card family consists of three
versions:
•PX3-4 Port
•PX3-8 Port
•PX3-16 Port
Users can leverage their investment in existing Promina equipment while
implementing state-of-the-art packet processing.
Front Card
Features
The PX3 front card includes an onboard processor and high speed serial
ports. PX3 serial ports can be connected to remote PX3 modules or to
local or remote data cards with external serial ports. The PX3 card has an
instruction cache and data cache. Increased memory provides additional
buffers for user traffic and memory for system tables (for example,
topology, route, and system data).
Software applications for the PX3 are stored directly on the card in
onboard flash memory. This allows faster reloads and permits redundant
software images which simplifies the upgrade process.
LEDs on the PX3 platform front panel indicate the status of the module.
For example, the Heartbeat LED indicates the overall health of the card,
while the Power LED indicates the card is receiving power. Refer to
Figure 3-2 for more details regarding the LEDs.
PCMCIA Card
The PX3 front card can use an optional PCMCIA card to facilitate backup
of configuration files and to upgrade software images.
The PX3 platform provides the following optional rear interface cards:
•T1/Ethernet
•E1/Ethernet
•Ethernet
•Token Ring
The T1 and E1 cards provide dynamic programmable channel allocation
and CRC-16 generation and checking. The interface cards can be
swapped without switching off power (“hot swapped”). The T1 and E1
interface cards have their own processor and therefore execute code
independent of the PX3 front card packet memory option.
The T1, E1, Ethernet, and Token Ring interface rear cards are available
for all PX3 models.
With the T1 and E1 interface cards, the PX3 supports access from
groomed carrier services. The T1 card supports up to 24 channelized
DS0s for a T1 trunk; the E1 supports up to 31 channelized timeslots for an
E1 trunk. These channels may be aggregated to form higher bit rate
signals with no requirement that they be contiguous. Both the T1 and E1
interface cards provide a 10BaseT port to support management console
access and diagnostics.
The PX3 platform supports the following networking applications: LWX
(LAN/W AN Exchange), FRX (Frame Relay Exchange), and PrimeSwitch
Module.
FRXFrame Relay Exchange (FRX) is N.E.T.’s solution for frame relay
networking. FRX networks enable an organization to provide frame relay
services over public or private trunks, or a hybrid public/private network.
FRX systems are designed to fulfill the following roles in hybrid frame
relay networks:
•Central switches that emulate hubs routing a large number of circuits
for frame relay traffic.
•Concentrator switching nodes that consolidate traffic from many
sources into a single or smaller number of circuits.
LWXThe LAN/WAN Exchange (LWX) application is a general purpose
router/bridge application integrated into the Promina Series platform,
providing internetwork connectivity between LANs over WANs that
contain Promina Series nodes. The LWX application is used in
conjunction with a PX3 front card and an Ethernet or Token Ring
interface rear card, and provides:
•concurrent multi-protocol routing and fallback MAC layer bridging
•up to eight logical serial connections to other LWXs or external
routers
PrimeSwitchN.E.T.’s Promina Series provides a network interface for an Integrated
Services Digital Network (ISDN). Promina Series supports the following
interfaces:
These interfaces enable a private ISDN network to be established
between Promina and IDNX platform products is 0. nodes, transforming
the N.E.T. wide area network (WAN) into a dynamic communications
resource that allocates bandwidth on demand, optimizing the use of the
backbone network. Connections can also be from any of these module
types to off-net public ISDN services.
Note: Refer to the appropriate user’s manuals for more information about:
The software application running on the PX3 module can be managed
through the Promina Interface Menu (PIM) using the Virtual
Connection/Card Connect option.
Table 1-1 shows the Promina system and software that fully supports the
PX3 platform.
Table 1-1Promina Software Support for the PX3 Platform
Promina SystemPromina Software Release
Promina 100R2.x1 or greater
Promina 200/400R1.x1 or greater
Promina 800R1.x1 or greater
Data port connectivity depends on the Promina software release installed
in the node. Refer to Chapter 2, Module Installation for PX platform
connectivity.
Data formats and port speeds supported depend on the Promina software
release installed in the node. Refer to Chapter 4, Database Installation
for a list of data formats and port speeds supported.
There are several key elements that assist the PX3 in establishing and
maintaining FRX, LWX, and PrimeSwitch connectivity. These elements
are shown in Figure 1-1 and described in Table 1-2.
Table 1-2PX3 Connectivity Network Elements (1 of 2)
Network ElementFunction
PX3 cardPX3 front cards connect to Promina cards
through 4, 8, or 16 internal serial port s. These
ports are made available through the
Operator Interface.
Operator InterfaceThe Operator Interface has simple menu
selections and commands to query and
control the operation of the Promina node.
UART connectorThe card also has a connector so that a
terminal can be attached through a Un ive rsal
Asynchronous Receiver/Transmitter (UART)
cable. You can also access the PX3 card via
the Promina Operator Interface or through
the Ethernet port on an optional interface
card. N.E.T. field service personnel uses the
UART cable for on-site diagnostics and
problem resolution.
CBus interface
Card Connect
SNMP/Agent—FRXThe SNMP agent communicates with the
SNMP/Agent—ProminaThe SNMP agent manages N.E.T.’s ATM and
The CBus, or control bus, carries signaling
and control information between modules.
The Connect-to-PX card feature allows an
operator at a Promina console to access an
application operator interface on a particular
PX card.
FrameXpress applications via SET and GET
commands. SNMP services can be
configured to support different application
products.
Multiservice Access Platform services.
The PPM, PLM, and IPLM controls and runs
the system software used on a Promina
node. It also controls the node and contains
the Operator Interface software. The PPM is
installed in the Promina 800; the PLM is
installed in the Promina 400/200; the IPLM is
installed in a Promina 100.
The PX3 platform can communicate through
LANs via the Ethernet interface. Simple
connections to the internet can also be
established. IP packets framed in Ethernet is
the transport protocol for SNMP messages
between the workstation and the
FrameXpress switch. The backcard portion of
the PX3 card supplies the Ethernet interface
to a workstation and supports TFTP, FTP,
Telnet, and SNMP.
FrameXpress Manager) also connect to the
Promina system through their individual
connections via the front card or interface
card using their own applicable method of
data transmission (for example, SNMP and
FTP).
This section describes how to estimate logical slot requirements, load
units, and power consumption; Promina shelf restrictions; and PX3
platform connectivity to data ports.
Logical SlotsLogical slots measure a module’s backplane bandwidth requirement (one
logical slot equals 2.048 Mbps of bandwidth). Logical slots must be
calculated to determine whether a configuration exceeds the logical slot
constraints for a shelf.
Note: For information on logical slot requirements, see the Quick Reference
Guide of the Promina Series documentation set.
The PX3 card is a multi-rate card. The PX3 supports up to 4.096 Mbps of
bandwidth per port. For the PX3 card, logical slots are assigned on a per
port basis and vary depending on the aggregate bandwidth and port
speeds.
The logical slots are based on the data rate selected by the user (refer to
Table 2-1).
Table 2-1Port Speed and Logical Slots Requirements
Port SpeedLogical Slots
Up to 64 kbps0.03125
Up to 128 Kbps0.0625
Up to 256 kbps0.125
Up to 512 kbps0.25
Up to 1.024 Mbps0.5
Up to 2.048 Mbps1.0
Up to 4.096 Mbps2.0
Load UnitsA load unit is a measure of the processor processing capacity. The PX
platform front card has a microprocessor unit (MPU) on board and does
not draw load units from the processor on the Promina node. Refer to the
Quick Reference Guide of the Promina Series documentation set for more
information.
Before installing the PX platform, determine the power consumption
requirement for the shelf where the PX platform is to be installed.
Refer to the Quick Reference Guide of the Promina Series documentation
set for more information.
Installation of the PX platform is restricted to certain slots on a Promina
shelf. These slot restrictions depend on the node and the shelf where the
PX platform is being installed. Table 2-2 lists the shelf restrictions for
Promina nodes.
Caution: Do not attempt to install a PX3 card in the Promina 800 HSS-2 shelf.
PX3 platform front cards connect to Promina cards through 4, 8, or 16
internal serial ports. These ports are made available through the Operator
Interface.
Note: For more information about individual PX3 platform connecti vity to data
ports, including formats and port speeds su pp orted fo r in dividu al data modules,
see the Promina SeriesData Modules manua l.
Table 2-3 lists PX3 card interconnections.
Note: T able 2-3 describes conn ections possible for PX3 cards in nodes running
Promina Release 1.x1 or later software.
Access
Platform
PX3 YesYesYesYesYesYesYesYesYes
1.The PX platform modules, when connecting to HSD-2 cards, do not support the Normal 56 data format.
2.The PX3 module cannot be connected to QSAD or QSD-2 modules running at 48 kbps.
3.For QXP connectivity at 56 kbps, configure the PX3 card for Normal 56 data format. For connectivity at 64 kbps,
configure the PX3 card for Normal 64 data format.
PX,
PX-2,
and PX3
Table 2-3PX3 Card Connectivity (Promina R1.x1 or later)
PX, PX
Plus
HSD-2
1
QASD
QSD-2
2
PRC
TMCP
USDCX
Clear
Channel
TRK-3
QXP
3
The individual port speeds are adjustable from 9.6 kbps to 4.096 Mbps on
all Promina platforms.
The serial ports are available in four port groups: ports 0-3, ports 4-7,
ports 8-11, and ports 12-15. The maximum allowable throughput for each
group of four ports is 8 Mbps, up to 32 Mbps per card.
In a Promina 800 node, speeds greater than 2 Mbps are available.
Consequently, it is important not to exceed the 8 Mbps per group
bandwidth requirement as described above. For example, in a Promina
800 node, if port 0 is 4 Mbps, and port 1 is 4 Mbps, then ports 2 and 3
should not be used.
Note: Although all 32 Mbps (16 x 2 Mbps) can be configured, there is a limit
based on available TBus and PX3 card switching capability.
This section describes the PX3 platform hardware installation. The
physical installation involve two steps for both the front and rear interface
card.
•Identify the physical slot
•Insert the card into the backplane
Caution: Before handling any card, observe precautions regarding electrostatic
discharge to prevent damage.
Pre-installationComplete these steps prior to installation.
To prepare for front and interface card installation
1. Open the cabinet rear door.
2. Locate the slot corresponding to where the front card will be installed.
3. Use the Query Card command to verify that the slot is not
configured for another card type.
Interface Card
Installation
This section describes the procedure for installing interface cards. If no
interface card is to be installed, bypass this section.
Caution: Make sure there is no front card installed in the slot corresponding to
the interface card. If you fail to observe this precaution, you may damage the PX
platform and the Promina node.
Figure 2-1 shows the installation of an interface card in a chassis using
knurled thumbscrews to secure the card in the shelf.
Note: If the shelf is not equipped with EMI-compliant retaining bracket s, contact
N.E.T. for a conversion kit for EMI-compliant cards. EMI-compliant retaining
brackets are scalloped, as shown in Figure 2-1. Th is conversion maint a ins FCC
compliance and is required for the T1/Ethernet and E1/Ethernet interface.
4. Attach the appropriate interface cables to the interface card
connectors:
T1/Ethernet Interface—Connect the 10BaseT cable to the T1
interface card connector; connect the other end to the concentrator.
Connect the T1 cable (from your T1 service provider) to the DB15
connector on the interface card.
E1/Ethernet Interface—Connect the 10BaseT cable to the E1
interface card connector; connect the other end to the concentrator.
For 120 Ω connections, attach the E1 service provider’s cables to the
transmit/receive BNC connectors. For 75 Ω (default) settings,
connect the E1 service provider’s cable to the DB15 connector on the
interface cable.
Ethernet Interface—The Ethernet access unit interface (AUI) cable
has a male connector at both ends. Connect the AUI cable to the
transceiver or repeater first and to the Ethernet interface last. The
Ethernet interface provides +12V to the transceiver . AUI-to-10Base2
transceivers may be directly connected to the interface.
Front Card
Installation
Token Ring Interface—Connect the DB9 end of the Token Ring
cable to the Token Ring interface card. Normally, the Token Ring
cable has a DB9 connector on one end, but the type of Token Ring
cable used depends on the Token Ring configuration. Connect the
other end of the cable to the media access unit (MAU).
5. Close the cabinet rear door.
This section describes the procedures for installing the PX3 card.
To install the PX3 card
1. Confirm that the interface card and the slot number for the front card
are correct.
Caution: Do not attempt to install a PX3 card in a the Promina 8 00 HSS-2 shelf.
2. Open the cabinet front door. Insert the card into the slot, as shown in
Figure 2-2. Seat the card in the slot by rotating the ejector arms
toward the center of the card, locking the arms inside the shelf front
edge. Seat the card completely, within two to three seconds, so that
power sequencing is applied to the card.
a. Observe the Power LED; the LED flashes for approximately 0.5
seconds and remains lit.
b. Observe the Heartbeat LED; a flashing LED (60 ppm) indicates
normal heartbeat operation.
Note: If any discrepancies are noted, refer to Chapter 5, Troubleshooting.
Figure 2-2Installing the Front Card
3. Close the cabinet front door.
4. Configure the PX3 platform through the Promina Operator Interface.
Configuration of the PX3 module in the Promina database is
described in Chapter 4, Database Installation.
For application specific configurations, refer to the appropriate
application manual.
Depending on the type of Promina shelf, slots 0 and 1 can be reserved for
use by other cards. Refer to Table 2-2 for more information.
When the PX3 front and rear interface cards are installed, the PX3
platform completes initialization and remains in the ready state for
database installation. The following LEDs provides a visual indication
that the PX3 platform has completed its initialization:
•Power LED—the green LED is lit and constant
•Heartbeat LED—pulsing LED at a rate of 60 ppm
If any discrepancies are noted, refer to Chapter 5, Troubleshooting.
PX3 front cards can be installed in an Promina Series node with or
without a rear interface card. When used with an interface card,
connections at rates up to 2048 kbps reduces the amount of TBus
bandwidth needed to support the platform.
Interface cards also provide the physical ports for LAN connectivity
which can be used for management or user IP traffic based on the
application in use.
This chapter contains module descriptions for the PX platform hardware
in the following sections:
PX3 front cards can be installed in an Promina Series node with or
without an interface card. When used without an interface card, the
system provides connection through the Promina backplane to the 4, 8, or
16 serial ports internal to the PX3 card. The PX3 front card does not
require an interface card and it can be configured with only the internal
serial ports activated. Interface cards for the PX3 card provide the
physical ports to connect local devices to the node.
The following are the hardware components that provides the PX3 card
capabilities.
•MC68LC040 processor operating at 25 MHz
•Up to four QUICC (Quad Integrated Communications Controller)
processors for faster switching at the port level
•Expandable memory resources
–system DRAM for system processing
–flash memory for code storage
–packet DRAM for user data buffers
–NVRAM (non-volatile memory) for configuration and
PX3 FeaturesThe PX3 card includes an onboard processor and high speed serial ports.
PX3 serial ports can be connected to remote PX3 modules or to local or
remote data cards with external serial ports. The PX3 card has an
instruction cache, data cache, and additional memory providing buffers
for user traffic and memory for system tables.
The PX3 card supports up to 16 HDLC ports which are divided into four
groups (refer to Table 3-1 for port to group associations).
The common features listed below apply to both the T1 and E1 interface
cards. Specific T1 and E1 features appear in their corresponding sections.
•MC68MH360 processor operating at 33 MHz
•1 Mb DRAM (256 Kb x 32) for program use and link statistics
•2 Mb flash memory (1 Mb x 16) for operating system, device drivers,
and application code
•16-bit DMA data path to front card packet memory
•64 byte NVRAM for serial number and card type
Ethernet LAN Interfaces
•RJ45 connection
•10BaseT connection
Note: Refer to the specific applications manual for specific support.
Clocking
•Promina clock mastership capability
•Promina reference clock using loop clock from the T1 or E1 span
Diagnostics
•full T1 or E1 loop back support at the port level
•LEDs for Ethernet, T1, and E1 alarms
T1 Interface CardThe T1 interface card provides PX3 based applications with a
channelized T1 connection that provides up to 24 additional logical ports.
These additional ports connect the PX3 to an available T1 network along
with CSU support. The T1 interface card does not utilize any TBus
bandwidth.
The T1 interface card is channelized up to 1.536 Mbps and meets
T1.403-1989; TR 62411 (12-90); TR 54016; ITU G.703, G.704, G.706,
G.823; and I.431 specifications. In addition, the T1 interface card
provides the following features:
•a DB15 connector
•Generates and detects
–CSU loop codes
–line interface for short or long haul trunks
–DSX-1 and CSU line build outs
•CSU selections of 0dB, -7.5dB, -15dB, and -22.5dB
•DSX selectable options of: 133 ft. (41 m), 266 ft. (81 m), 399 ft. (122
m), 533 ft. (162 m), or 655 ft. (200 m)
•D4(SF)/ESF framing formats
•AMI or B8ZS one’s density options support
•FDL compliance to ANSI T1.403 and AT&T TR54016 support (for
ESF, both protocols may be used concurrently)
•up to 24 HDLC ports to the PX3 front card (a port is a multiple of
NC56 or NX64 Kbps)
•Meets UL 1950; FCC Part 15 Class A; FCC Part 68; IEC 950; CSA
C22.2 No. 950; and IC CS-03 compliance
E1 Interface CardThe E1 interface card provides the PX3 based applications with a
channelized E1 connection that provides up to 31 additional logical ports
that can be used for data. The E1 interface card does not utilize any TBus
bandwidth.
The E1 interface card is channelized up to 2.048 Mbps and meets ITU
G.703, G.704, G.706, G.823, and I.431 specifications. In addition, the E1
interface card provides the following features:
•up to 31 HDLC ports (multiframe) to the PX3 front card (a port is a
The E1 interface card is shipped from the factory configured to 75 Ω. The
transmit ring is grounded and the received ring is AC coupled to ground.
Note: This is provided for use with the BNC connector.
The E1 interface card has seven user configurable jumpers. Four to select
the line impedance setting and three for the optional ring grounding. The
jumpers for selecting either 120 Ω or 75 Ω are located on the bottom half
of the interface card as shown in Figure 3-6. Jumper E10 is located near
the top-right of the card.
Note: The E-1 Rev. 200 and earlier interface cards are not customer
configurable; contact TAC for assistance setting to 120 Ω.
To set 75/120 Ohm Line Impedance
1. To select the 75 Ω setting, ensure that the jumpers are seated on both
pins for the four jumper blocks, E1, E2, E3, and E10, as shown in
Figure 3-6.
2. Remove the jumpers from E1, E2, E3, and E10 jumper blocks to
Figure 3-6Line Impedance Jumpers for Rev. 300 (and later) Cards
change the impedance on the card to 120 Ω, as shown in Figure 3-6.
After installing the PX3 platform hardware, the system must be software
configured and database installed as part of the Promina wide area
network (WAN). This chapter provides the card and port parameter
information, with examples, in the following sections:
After the PX3 platform is physically installed (described in Chapter 2,
Module Installation), it must be configured as part of the Promina wide
area network (WAN). To database install the PX3 platform, there are two
required steps to be performed from the Promina Interface Menu:
•install and configure the card (Install Card command)
•install and configure the ports on the card (Install Port command)
Promina database installation provides the PX3 based applications the
following:
•virtual connect capability (card install)
•access to physical connections (TBus) for serial ports (port install)
•access to the CBus
Use the Query Card and Query Port commands to display PX3
platform configurations. Use the Modify Card and Modify Port
commands to change PX platform card and port configurations.
The Promina Interface Menu does not configure the functionality of the
PX3 based application ports; these are configured through the application
interface menu.
Note: The PX platform can provide clock references if it has a T1 or E1 rear
card. The T1 or E1 facility is used for the clock source, for example the Ethernet
interface.
Note: For additional information about the Operator Interface, OI menus, and
expert mode, see the Promina Series Node Management manual as well as the
Operator Interface Command Summary in Appendix A.
Use the following procedure to install the PX3 card in the Promina
configuration database. After the PX3 card has been installed, the
Operator Interface prompts for the card to be enabled and activated.
To install the PX3 card
1. Use the menu path or expert mode command shown below to install a
card.
Menu Path: CONFIGURATION/INSTALL/CARD
Expert Mode: Install Card
The Operator Interface prompts for the card ID (the node and slot
number where the card will reside).
2. Enter the card ID (Example 4-1).
The Operator Interface displays a list of installable card types.
Example 4-1Install PX3 Card
< install card
INSTALL which CARD(s)? [ALL ON THIS NODE]
CARD ID = c34
*** Slot N1C34 contains card type PX-3.
Do you want to install card N1C34? [YES]
3. Enter the card type and modify any applicable parameters. The
Operator Interface displays the card parameter settings and prompts
to activate the card (card parameters are described in Card Configuration Descriptions on page 4-8).
Example 4-2PX Platform Card Configuration Parameters
*** CONFIGURATION PARAMETERS FOR PX-3 CARD N8C24 ***
[ 0] EVENT ALARM LOGGING = ENABLED
[ 1] REQUIRED SOFTWARE VERSION = NONE
[ 8] TOKEN RING SPEED = 4MB
[10] CLOCK REFERENCE SELECT = NONE
[11] PORT CAPACITY = 16
ENTER PARAMETER INDEX (OR HIT RETURN TO CONTINUE)
PARAMETER INDEX =
4. Confirm that the card parameter settings are correct before activating
the card.
5. Activate the card; the PX3 card cannot build calls until the card is
activated.
6. Use the Query Card command to view the card’s configuration
(Example 4-3).
Note: To confirm that the card has been installed in the Promina configuration
database, use the Query Events command to query the node where the car d is
installed. Refer to the Promina Series Operator Interface for more information
about this command.
After the PX3 platform has been installed, use the Query Card command
to display the PX3 platform configuration. Use the menu path or expert
mode command shown below to query a card.
Menu Path: CONFIGURATION/QUERY/CARD
Expert Mode: Query Card
For more information about the Query Card command, refer to the
Promina Series Operator Interface.
Card
Configuration
Descriptions
Example 4-5PX Platform Card Configuration Screen
*** PX-3 Card N202C25 Configuration (Cpu:C4)
DB Status: ACTIVE Card Status: UP
Slot Type: PX-3_16 Interface Type: ETHERNET
Port Capacity: 16
Installed Ports: 2 Active Ports: 2
Function : LWX
Event/Alarm Logging: ENABLED
Token Ring Speed: 4MB
Clock Reference Select: NONE
Front Card Serial Num: 1355853 (REV B)
Interface Card Serial Num: 1042846 (REV A)
Example 4-5 shows a PX3 platform card configured as a LWX module.
Refer to the descriptions in the following pages for a description of fields
in the configuration display.
This section describes the fields that appear in PX platform card
configuration displays. The values, options, or ranges for each field are
provided, when applicable.
Header Information
The header displays general information regarding the card type, card ID,
and slot number of the processor that is managing the PX platform tasks.
This field indicates the status of the card in the configuration database.
The values are Active (in service), Enabled (in test mode), and Disabled
(not available).
Card Status
This field indicates the status of the software running on the PX card. The
values are Up if the correct software version is running, Down if no
software is running.
Slot Type
This field identifies the type of card installed in the slot. the value can be
any card type or None.
Note: An asterisk in the slot type usually indicates a database mismatch. Verify
that the card type is the same as the card physically installed in the slot.
Interface Type
This field shows the type of interface card (including the revision
number) installed in the rear card slot.
•None—indicates that no interface card is installed in the rear slot.
•T1/Ethernet—indicates that a T1/Ethernet card is installed in the rear
slot
•E1/Ethernet—indicates that an E1/Ethernet card is installed in the
rear slot
•Ethernet—indicates that an Ethernet card is installed in the rear slot.
•Token Ring—indicates that a Token Ring card is installed in the rear
slot.
Port Capacity
This field is automatically configured at install. Users can modify this
field, but it is not recommended. For modification recommendations,
contact your N.E.T. representative.
Installed Ports
This field indicates the number of serial ports installed in the
configuration database.
This field indicates the number of ports with calls in progress.
Function
This field indicates the function assigned to the PX platform.
With Promina Release 1.x1 or later software, the options are as follows:
•None—booter is running on the PX3 card
•LWX—full function multi-protocol router
•FRX—frame relay switch with DCE and DTE interface support
•ISDN—displayed for PrimeSwitch
•PrimeSwitch—PrimeSwitch channel server module
Event/Alarm Logging
This field indicates whether alarms and events for the PX platform are
logged in the Promina alarm database. For more information, refer to [0] Event/Alarm Logging on page 4-6.
Token Ring Speed
This field may operate at either 4 Mb or 16 Mb ring speeds. Use this field
to modify the Token Ring to match ring speeds.
Clock Reference Select
The PX3 card with a T1 or E1 connection may be configured to provide a
clock reference for the node. Refer to the Promina Series Node Management Manual to modify node clocks.
Required Software Version
This field indicates the version of software code required for the
application to run on this node. For more information, refer to [1] Required Software Version on page 4-7.
Running Software Version
This field indicates the image of software application code running on the
PX platform. The value of the parameter can be None or a specific
version and edit of code. The default value of this parameter is None.
PX3 port installation follows card installation. Make sure the PX3 card is
installed before attempting to install ports.
Use the Install Port command to add ports to the configuration database
and make them operational. Use the Query Port command to display an
installed port configuration. Use the Modify Port command to change
the configuration of a port.
Note: For information about Operator Interface, OI menus, and expert mode,
see the Promina Series Node Management manual.
The following procedure describes how to install a port on the PX3 card.
To install a port on the PX card
1. Use the menu path or expert mode command shown below to install a
port.
Menu Path: CONFIGURATION/INSTALL/PORT
Expert Mode: Install Port
The Operator Interface prompts for the port ID (the node, card, and
port on the card, Example 4-6).
Example 4-6Install Port
INSTALL which port(s)? [ALL ON THIS NODE]
PORT ID = n1c25p0
Port N1C25P0 is type ’PX-3’.
Do you want to install this port? [YES]
YES OR NO =
Do you want to copy the configuration of an existing port? [NO]
YES OR NO =
2. Enter the port ID. The Operator Interface provides the option to
specify any port filters and copying the configuration of a previously
installed port.
Note: Use the Operator Interface copy option when installing multiple ports
with identical configurations.
3. For originate-only or originate-answer ports, specify the destination
port ID.
4. Modify any other applicable port parameters. Refer to the Port
Parameters on page 4-14.
5. Confirm that all port parameters and the destination port ID are
correct, then press <Return> to install the port. The Operator
Interface displays the configuration for the port.
Note: If configuring the port parameter Maximum Link Cost Routing, the
value range is 0 (lowest) through 1023 (highest). T he defa ult is 0 ( no limit) . Fo r
a given call, if the call attempts to traverse to a set of links whose costs exceed
the origination port or port bundle’s maximum link cost value, the call will be
prevented from taking that path and rejected on a call by call basis. For
interdomain calls, the cumulative link cost is reset upon entering a transit and/or
destination domain. This means the cumulative link cost is bounded on a per
domain basis for interdomain calls.
[0] Originate/Answer Mode
Options are Ans-only (default), Orig-only, and Orig/Ans.
This parameter specifies whether the port can originate and answer calls,
answer calls only, or originate calls only. Originate/answer and
originate-only ports require a destination port.
[1] Destination Port/Bundle
This option is selectable only if this is Orig-only, or Orig/Ans.
The setting for the destination port ID is the destination port that
communicates with the origination port.
This parameter is required for originate/answer and originate-only ports.
The type of destination ports the PX platform can communicate with
depend on the release of the Promina software.
With Promina Release 1.x1, the PX platform can connect to clear channel
ports on a TRK-3 (span mode). This parameter is listed as [1] Destination
Bundle when parameter [11] TRK-3 Clear Channel Port is set to Yes.
With Promina Release 1.x1, the PX3 card can connect to several
destination ports, for example, HSD-2, CX, or PRC. For a complete list of
PX3 platform connectivity refer to Table 2-3.
[2] Call/Preempt Priority
These parameters apply to answer and originate-only ports, but not
answer-only ports.
The range for Call Priority is 0 (lowest) through 15 (highest). The default
is 7. The range for Preempt Priority is 0 (lowest) through 15 (highest).
The default is 0.
Although they appear on the screen as one item, these are two
independent parameters. They work together to determine which call is
placed or reconnected.
Call priority determines the order in which a call originating from this
port is reconnected when the port is interrupted for any reason. A port
with a high call priority is reconnected before ports of lower call priority,
but after ports of higher call priority. When all ports have the same call
priority, there is no particular order for reconnection.
Call priority is also used to determine whether a call originating on a port
can be preempted when there is insufficient bandwidth on the link to
handle all calls. Call priority and preempt priority work together in
making this determination.
Preempt priority is used when there is not enough bandwidth to complete
a call. The preempt priority value assigned to the call is compared to the
call priority value assigned to other calls on the link to determine which
calls should be preempted. Calls having a call priority value lower than
the value of the preempt priority call are preempted. The preempted call
is placed when enough bandwidth is recovered.
To prevent certain calls originating on other ports from being preempted,
assign them a call priority that is higher than the value of the preempt
priority. Although preempt priority ensures that the call obtains
bandwidth, it does not mean that the call will be completed if the
destination port is busy.
[3] Secondary Call/Preempt Priority
The range for Secondary Call Priority is 0 (lowest) through 15 (highest)
and the default is 7. The range for Secondary Preempt Priority is 0
(lowest) through 15 (highest) and the default is 0.
The description and values are similar to [2] Call/Preempt Priority , but [3]
takes effect on a secondary basis. When a call is trying to build on the
optimal path, it uses the primary set of priorities defined by [2]; if the
optimal path is not available, the call uses the secondary priorities.
Optimal path is defined as a selected path fulfilling the routing
preferences and employing the least number of hops and least cost.
[4] Port Speed
The port speeds available depend on the data format and the type of node
in which the PX platform is installed. A higher bandwidth is available for
a PX platform installed in an Promina 800 than for a PX platform
installed in a Promina 400. For more information about the modules that
support 9.6 and 19.2 kbps asynchronous call rates, see the Promina Series Data Module manuals.
Port speeds listed in this section are available for PX platform to PX
platform connections. The following section discusses PX3 specific port
speeds (Table 4-1). Port speeds available for PX platform to data port
connections vary depending on the type of data port. For more
information, refer to [1] Destination Port/Bundle on page 4-15.
The port speeds shown include the maximum speeds that can be
configured. The actual reliable port speeds may be lower, depending on
the following factors: trunk speed; the application of the PRC or TMCP
cards; the model number of the Promina; and the PX platform card in use.
For Promina nodes, the PX3 card supports asynchronous call rates of 9.6
and 19.2 kbps. This makes these PX platforms suitable for connection to
any data card that supports trunk asynchronous call rates of 9.6 and 19.2
kbps, including the HSD-2, QSD-2, and QASD cards.
Table 4-1 lists the port speeds available in Nx64, Normal 64, Nx56, and
Normal 56 data formats.
Note: The port speeds shown in Table 4-1 include the maximum speeds that
can be configured. The actual reliable port speeds may be lo wer, depending on
the following factors: trunk speed; the application of the PRC, TMCP, or NGS
cards; and the model number of the Promina.
For permanent calls, when the same start and end times are specified, the
call is torn down and replaced every day at that time. This technique can
be used to optimize the path used. The call will not be torn down when it
is already on an optimal path.
[6] Routing Options
This parameter specifies the routing requirements for terrestrial routing,
encryption routing, ATM, SCLX, and fiber routing. The possible settings
for each of these routing options are Don’t Care (default), Prefer Not, Preferred, and Required.
Use the routing options parameter to specify the routing method for a
specific application. For example, selecting Fiber can indicate any
operator-defined routing method.
•Don’t Care specifies that any available path is used.
•Prefer Not specifies that certain paths are used when no other paths
are available. The call is not blocked.
•Preferred specifies that certain paths are used first. If those paths are
not available, any path is used. The call is not blocked.
•Required specifies that only certain paths can be used. If those paths
are not available, the call is blocked.
Note: Refer to the appropriate application manual for guidelines.
[7] Primary Selected Path
Up to 12 node IDs, including intermediate nodes and the destination
node, can be specified in a selected path. When specifying more than one
node, separate the node IDs with a comma. The same node cannot be
specified more than once. The default setting for this parameter is None.
This parameter allows the user to override the system and specify the path
the call takes through the network. This provides for full end-to-end
management of the call from the originating node, through the transit and
destination domains, all the way to the destination node.
When creating a path, confirm that it meets the port’s routing attributes.
Up to 255 selected paths can be created. Only one path can be specified
per port, but specified paths can be shared among ports.
After a path is created, it is placed in the path select table, where it can be
queried or deleted. When a path is deleted from the path select table, all
ports using that path are changed to None.
When no path is specified or the selected path is unavailable, the system
determines the best path.
Note: Refer to the appropriate application manual for guidelines.
[8] Data Format
This parameter can be set to Nx56, Nx64 (default), Normal 56, or
Normal 64.
Note: Refer to Table 4-1 for port speeds.
This parameter specifies the type of data format used on the port. When
Nx64 is selected, all bits in the data stream are used. Choose Nx56 format
when data passes through equipment that requires the ones density
format. Nx56 uses seven bits of the stream for data, with the eighth bit set
to one. Normal 64 format can be used for SDLC inter-networking and
lower speeds.
Table 4-2 lists data formats for card types at the other end of the call.
Table 4-2Call Data Formats
Card TypeFormat
HSD-2Both sides are set the same
PX3All. Both sides are set the same
PX-2All. Both sides are set the same
PX PlusAll. Both sides are set the same
PXNx64 or Nx56
QASDNormal 56 or Normal 64
QSD-2Normal 56 or Normal 64
PRCNx64
TMCPNx64
USDNormal 64
QXPNormal 56 or Normal 64
1.The PX platforms, when connecting to an HSD-2, do not support Normal 56 data.
This parameter can be set to Two Way Call (default), One Way Inbound,
or One Way Outbound.
This parameter is used to define the direction of the data flow. This
parameter is used in conjunction with one way call and asymmetric
trunks (SA-TRK module). Most data ports have this option, although it is
not necessary for all applications.
One Way Inbound specifies that the data only flows from the originate
port to the answer port. One Way Outbound specifies that the data flows
from the answer port to the originate port.
For more information on one-way and two-way calls associated with the
SA-TRK, refer to Promina Series Trunk Modules.
[10] Path/Selected Path Required
This parameter can be set to Yes or No.
When the parameter is set to Yes, calls are restricted to the path specified
in the selected path field. When no selected path is specified, this
parameter is inactive.
The path required parameter prevents the system from rerouting calls
from the selected path to a different path. When the parameter is set to
No, the system can reroute calls from the selected path to a diffe rent path
when there is a network failure.
[10] Selected Path Required is available to nodes running IDNX Release
12.x2 or later software.
Note: Refer to the appropriate application manual for guidelines.
[11] Clear Channel Port
Value is Yes or No (defualt).
This parameter can be set to Yes or No. Set this parameter to Yes to enable
the TRK-3 clear channel port. Data format must be set to Nx64 for
connection to CX VBR/CBR ports.
Note: This parameter can be used to connect to any port bundle (for example,
CX, SCLX, for an IP-TRK port bundle), not just a TRK-3 clear channel port.
This parameter specifies a secondary call path; see[7] Primary Selected
Path on page 4-20.
[14] Primary Selected Gateway
Values are: 0 through 250; 0 is NONE (default).
This parameter specifies a primary gateway node which is referred to as
the Outbound Gateway (OBGW) node. The call will try to use the newly
specified OBGW node.
[15] Secondary Selected Gateway
Values are: 0 through 250; 0 is NONE (default).
This parameter specifies a secondary gateway node (for backup) which is
referred to as the Outbound Gateway (OBGW) node. The call will try to
use this secondary specified OBGW if the primary selected gateway is
unavailable.
[16] Gateway Required
Values are: Yes or No (default)
This parameter specifies that the specified gateway node(s) is/are
Use the Operator Interface Query Port command to display the
configuration for a port.
Use the menu path or expert mode command to query a port.
Menu Path: CONFIGURATION/QUERY/PORT
Expert Mode: Query Port
For more information about the Query Port command, refer to the
Operator Interface Command Summary appendix.
Port Configuration
Descriptions
Example 4-9PX3 Platform Port Configuration Screen
*** PX-3 Port N1C33P0 Configuration (Dest Port is Port N250C37P0) ***
N1C33P0 N250C37P0 N1C33P0 N250C37P0
Card Type: PX-3 HSD-2 Slot Type: PX-3 HSD-2
DBCard Status: ACTIVE ACTIVE DB Port Status: ACTIVE ACTIVE
Clr Chan Port: NO
Orig/Ans Mode: ORIG-ONLY ANS-ONLY Dest Port: N250C37P0
Port Speed: 256000 256000
Call Priority: 7 Preempt Prty: 0
Sec Call Pty: 7 Sec Prmt Pty: 0
HW I/F Type: DCE/RS530/D DB I/F Type: DCE
Terr Routing: DON'T CARE TOD Restrict: NONE
Encry Routing: DON'T CARE
Fiber Routing: DON'T CARE
ATM Routing: DON'T CARE
SCLX Routing: DON'T CARE Max Link Cost: 0
Transp Signl: NO
DCE TTiming: NO
Call Ans Sig: NONE
Signal Events: NO
Pri Sel Path: NONE
Sec Sel Path: NONE
Pri Sel GW: NONE
Sec Sel GW: NONE
Sel GW Req: NO
Actual Path: 1-250 (OP)
Data Format: NX64 NX64
Data Flow Direction: Two Way Call
Example 4-9 displays the port configuration for the PX3 platform.
*** PX-3 Port N1C33P0 Status (Other End is N250C37P0) ***
Call State: Call In Progress Last Disconnect: HANG UP
This section describes the fields that appear in PX platform port
configuration displays. The values, options, or ranges for each field are
provided, when applicable.
This field shows the path the port is using to complete a call through the
network. The origination node is listed first, and the destination node is
listed last. Any nodes in between are intermediate nodes through which
the call passes to arrive at the destination node.
This field also indicates whether the path is an optimal path (OP) or a
non-optimal path (NOP). When a call is reconnected through an optimal
(that is, least-cost) path, OP is displayed to the right of the actual path
field. If there is insufficient bandwidth and a call is connected through a
non-optimal path, NOP is displayed.
ATM Routing
See [6] Routing Options on page 4-20.
Call Answer Signal
This field indicates the signal required to answer a call. For more
information, see the Promina Series Data Modules manual.
Call Origination Signal
This field indicates the signal required to generate a call. For more
information, see the Promina Series Data Modules manual.
Call Priority and Preempt Priority
This field determines how a call is reconnected or placed. For more
information, see [2] Call/Preempt Priority on page 4-15.
Call State
This field shows the state of the call when the port is queried. The
possible call states are:
•Answer disconnect—When in the awaiting answer state, the port is
disconnected. When the call is answered, it is disconnected.
•Awaiting answer—The port originated a call and is waiting for
confirmation from the destination port before it completes the call.
•Awaiting connect (orig) and awaiting connect (dest)—The circuit is
built, and the node is waiting for a connect acknowledgment before
signaling to the terminal that the call is up (carrier detect comes up).
When the destination port is configured for an answer signal, the
origination port remains in the awaiting answer state until the
destination port responds.
This field indicates the data format used on the port. For more
information, refer to [8] Data Format on page 4-21.
DCE Timing (HSD-2 only)
This field indicates whether DCE timing is switched on. DCE timing
makes sure that the clock and data received at the port are in phase.
Values are Yes and No.
Dest Port
This field indicates the destination port for the originate port and appears
for originate/answer and originate-only ports. For more information, refer
to [1] Destination Port/Bundle on page 4-15.
Encryption Routing
This field specifies routing requirements For more information, refer to
[6] Routing Options on page 4-20.
Fiber Routing
This field specifies routing requirements. For more information, refer to
[6] Routing Options on page 4-20.
Generic Header Information
This field displays the ID of both the port being queried and the
destination port.
Gateway Required
See [16] Gateway Required on page 4-23.
Last Disconnect
This field describes the reason the call was terminated. The possible call
terminations are:
•Call blocked—The call is blocked because there are no resources
available.
•Dest busy—A call is in progress at the destination port.
•Dest error—A network error occurred at the destination node.
•Dest fault—The destination port will not accept the call because the
port is not active, there is a port configuration mismatch, the card is
not active, or the port did not pass self-tests.
•Dest timeout—The node exceeded the amount of time required to
connect a call on the destination node.
•Duplicate call—The node indicated that a call to or from a port was
already placed when a request for a new call is made.
•Hang up—The other side hung up.
•Invalid dest address—The destination port was not installed.
•No path—There is no network path for the call.
•Task timeout—The call could not be completed because the
origination task did not receive a response from the destination task.
This condition can occur if the origination port is active and the
destination port is disabled.
•TBus fault—A negative acknowledgment was received from the TBus
manager when a request for a call was made.
•T imeout on char ge packet—The origination port did not receive a call
answer message within the required timeframe.
Orig/Ans Mode
This field indicates whether the port can originate or answer calls. For
more information, refer to [0] Originate/Answer Mode on page 4-15.
Path Required
This field indicates whether a selected path is specified. For more
information, refer to [10] Path/Selected Path Required on page 4-22.
Port Speed
This field indicates the port speed. For more information, refer [4] Port
Speed on page 4-16.
See [3] Secondary Call/Preempt Priority on page 4-16.
SCLX Routing
See [6] Routing Options on page 4-20.
Signal Events
This field indicates whether or not interface signal transition events are
logged. This parameter is for diagnostic purposes only because the events
may flood the event log. Options are No (default) or Yes.
The signals that can cause events are DTR/DSR, DCD, ring indicator,
ready, and test mode. For more information, see Promina Series Data Modules manual.
Slot Type
This field shows the type of card physically installed in the slot.
Note: When the card type and slot type are not the same, either replace the
card or install the correct card in the configuration database.
Terrestrial Routing
This field specifies routing requirements. For more information, refer to
[6] Routing Options on page 4-20.
TOD Restrict
This field indicates the times of the day when a port is active. For more
information, refer to The time-of-day restriction specifies a start and end time for the port. The default is None. on page 4-19.
Transparent Signaling
This field refers to the HSD-2 card connecting to the PX platform on the
Promina WAN. For more information, see the Promina Series Data Modules manual.
The Connect-to-PX Card command allows a Promina operator to
communicate with the PX3 platform processor from the Promina
Interface Menu (PIM). Example 4-10 displays the Promina Interface
Menu. Select option 10, Connect-to-PX card, and enter the card number
when prompted.
Example 4-10Promina Interface Menu
PPM Promina Interface Menu
Node 1 Card 4 Console Port
1. Operator Interface
6. Connect to a CPU in this node
7. Connect to another node
8. Connect to the PSM
9. Connect to CX card (this node)
10. Connect to PX card
99. Logout
Enter Choice
->10
Which card [NxCx] ->
LWX Card
Connection
Example 4-11LWX Prompt
PPM Promina Interface Menu
Node 153 Card 6 Remote Port
1. Operator Interface
6. Connect to a CPU in this node
7. Connect to another node
8. Connect to the PSM
9. Connect to CX card (this node)
10. Connect to PX card
99. Logout
Enter Choice
->10
Note: For information about the Operator Interface, OI menus, and expert
mode, see the Operator Interface Command Summary appendix.
When the PX3 platform is configured as an LWX, the LWX prompt
appears after entering the card number. On initial connection to LWX,
password is not required. Refer to the LWX manual for details
configuring the password.
Copyright (C) 1996 Network Equipment Technologies, Inc. All Rights
Reserved
This software is furnished under a license and may only be used in
accordance with the terms of such a license. Use by the
Government is restricted in accordance with the RESTRICTED RIGHTS
provisions of FAR 52.227-19 and DFARS 252.227-7013 unless otherwise
agreed. See software media, documentation or governing contract
for details.
(RETURN to continue ...) >
N.E.T. FRX 3.02.01, v32.3 From IDNX D0N1C26
Top Level Menu (? for help)
When the PX3 platform is configured as an FRX, the login prompt
appears. After the valid login is accepted, the password prompt appears.
After the valid password is accepted, the FRX Banner and Top Level
Menu displays.
1 (QUE) Query status and configuration
2 (MOD) Modify configuration and/or attributes
3 (INS) Install new object
4 (DEL) Delete object
5 (ACT) Activate object
6 (DIS) Disable object
7 (SAV) Save configuration in file ’default.cfg’
8 (FIL) File operations
9 (MAN) Management operations
10 (CON) Connect to another FRX node
11 (LOG) Logout of this FRX node
12 (RES) Reset and Reload this FRX node
Copyright (C) 1998 by
Network Equipment Technologies, Inc.
All Rights Reserved.
Copyright 1984-1995 Wind River Systems, Inc
Copyright 1989-1992, Trillium Digital Systems, Inc.
This software is furnished under a license and may only be used in accordance
with the terms of such a license.Use by the Government is restricted in
accordance with the RESTRICTED RIGHTS provisions of FAR 52.227-19 and DFARS
252.227-7013 unless otherwise agreed. See software media, documentation or
governing contract for details.
******************************************************************************
PrimeSwitch 6.01.01, v(47.07) From IDNX CARD: D15N4C16
MAIN MENU (? for help) 17:5:31 03-16-99
1 (CON) CONFIGURATION
When the PX3 platform is configured as PrimeSwitch, the login prompt
appears. After the valid login is accepted, the password prompt appears.
After the valid password is accepted, the PrimeSwitch Top Level Menu
displays.
This chapter describes troubleshooting, diagnostics, repair, and
replacement procedures.
The troubleshooting procedures described in this chapter are provided for
personnel trained in servicing N.E.T. system equipment. Some
procedures require knowledge of the PX3 Operating System (Bootstrap
Program) to perform general troubleshooting of the applications. The
troubleshooting procedures do not go beyond the scope of the user level
options available in the Bootstrap Program Menu.
Note: For software module-specific information about the PX platform, refer to
that module’s user’s manual
Troubleshooting, repair, and replacement procedures are described in the
following sections:
The LEDs on the PX3 module front panel (Figure 3-2) are status
indicators for specific functions in the PX3 module. Table 5-1 is a quick
reference listing the LEDs, descriptions of problem conditions, and action
to perform.
Table 5-1LED Status
LEDDescriptionAction
PowerThe power LED is off.Check that power is switched on to the
shelf.
The power LED flashed momentarily, but
does not stay on.
Problem still exist.Call TAC or your local N.E.T. support center.
PortThe port LED is not on.The HDLC controller is not activated. Refer
Problem still exist.Call TAC or your local N.E.T. support center.
HeartbeatThe LED is off.Reset card.
The LED is not pulsing at a rate of 60 pulses
per minute.
Problem still exist.Call TAC or your local N.E.T. support center.
CBusThe CBus LED is lit.There is a CBus failure; reset card.
Problem still exist.Call TAC or your local N.E.T. support center.
ResetThe Reset LED is lit or is flashing. The card is hung in a loop state; reset card.
Problem still exist.Call TAC or your local N.E.T. support center.
Check the power supply. Go to DC Power Checks on page 5-8.
to the appropriate application manual for
specific LED status.
Check the power supply. Go to DC Power Checks on page 5-8.
This section provides the troubleshooting procedures for problem
indicators that may occur during the database installation of the PX3 card.
Normal Install
Condition
Example 5-1Install PX3 Card
< install card
INSTALL which CARD(s)? [ALL ON THIS NODE]
CARD ID = c34
*** Slot N1C34 contains card type PX-3.
Do you want to install card N1C34? [YES]
When the PX3 card is inserted into the card slot and completes its
initialization, the card is recognized by the Promina system. From the
Operator Interface this acknowledgement is confirmed when the
command install card is entered (Example 5-1).
Card Slot is Empty
1. Verify that the node number and card slot number is correct.
2. Allow an additional 15 to 20 seconds for the PX3 card to complete its initialization; repeat the install card command.
3. Go to PX3 Card Installation on page 5-3 and check the card
installation procedure.
4. If the problem still exist, call TAC or your local N.E.T . support center.
This section provides the troubleshooting procedures for problem
indicators that may occur during the bootstrap phase of the PX3 card.
Normal Boot
Condition
When the PX3 is installed, you can access the PX3 card through its
virtual connection. From the Operator Interface, select the option to
Connect to PX card.
Cannot Connect to the PX Card
Virtual connection is not enabled until the PX3 card is installed.
1. Verify that the node number and card slot number is correct.
2. Check that the PX3 card is database installed.
3. Refer to Chapter 4, Database Installation.
4. Press the Reset switch to reset the PX3 card and boot the application.
5. If the problem still exist, call TAC or your local N.E.T . support center.
6. Make sure you are on the correct processor.
Connect to PX Card - Bootstrap Banner Appears
The bootstrap banner and login prompt displays; the port LEDs are
flashing sequentially (counterclockwise)—the application did not boot.
Note: For details regarding the Bootstrap menu and submenus, refer to
Appendix A, PX3 Operating System and Applications.
1. Examine the card (from Bootstrap) for boot information.
2. Verify that the setting for “bootable image” is set to the application
image file.
Note: For details regarding the Examine Items submenu, refer to Appendix A,
PX3 Operating System and Applications.
3. Verify that the appropriate application file (from File Operations) is
located in the /flash/0 directory.
Note: For details regarding the File Operations submenu, refer to Appendix A,
PX3 Operating System and Applications.
Example 5-2Verify Application File
PX3 BOOTSTRAP
File ...
1 (PWD) PWD Print Working Directory
2 (DIR) Directory of files
3 (CD ) CD Change to Directory
4 (LIS) List a file
5 (DEL) Delete file
6 (COP) Copy a file
7 (REN) Rename a file
8 (MOU) Mount PCMCIA FLASH Device (/FLASH/1)
9 (DOS) DOS Fs Config Info
10 (CAL) Calculate Checksum for a File
11 (REA) Read Checksum Information in a file
* 12 (FIN) Finish - return to top menu
Enter> dir
size date time name
4. Read the checksum information for the application file.
Example 5-3Read Checksum
PX3 BOOTSTRAP
File ...
1 (PWD) PWD Print Working Directory
2 (DIR) Directory of files
3 (CD ) CD Change to Directory
4 (LIS) List a file
5 (DEL) Delete file
6 (COP) Copy a file
7 (REN) Rename a file
8 (MOU) Mount PCMCIA FLASH Device (/FLASH/1)
9 (DOS) DOS Fs Config Info
10 (CAL) Calculate Checksum for a File
11 (REA) Read Checksum Information in a file
* 12 (FIN) Finish - return to top menu
Enter> 11
Filename? frx32.04
Magic Number in file frx32.04 = 0x1
Checksum in file frx32.04 = 0x7C578FC
5. Calculate the checksum for the application file and compare to the
checksum information read in 4.
Example 5-4Calculate Checksum
PX3 BOOTSTRAP
File ...
1 (PWD) PWD Print Working Directory
2 (DIR) Directory of files
3 (CD ) CD Change to Directory
4 (LIS) List a file
5 (DEL) Delete file
6 (COP) Copy a file
7 (REN) Rename a file
8 (MOU) Mount PCMCIA FLASH Device (/FLASH/1)
9 (DOS) DOS Fs Config Info
10 (CAL) Calculate Checksum for a File
11 (REA) Read Checksum Information in a file
* 12 (FIN) Finish - return to top menu
Enter> 10
Filename? frx32.04
Checksum Calculated for file frx32.04 = 0x7C578FC
6. Press the Reset switch to reset the PX3 card and boot the application.
7. If the problem still exist, call TAC or your local N.E.T . support center.
The PX3 module front panel provides test points (Figure 3-2) to monitor
the condition of the DC voltages from the shelf backplane to the card.
Table 5-2 lists the available DC voltages to the card.
Table 5-2DC Voltages
VoltageDescription
+12 V DCProvides DC power to the flash card for write and erase
operations
+5 V DCProvides DC power to the PWA compon ents
-5 V DCProvides DC power to the PWA components
GndMonitors the reference ground signal for the DC power
This section describes procedures for replacing an interface card, a front
card with an identical card, and upgrading a front card.
Note: Always remove the front card prior to removing the rear interface card.
Replacing an
Interface Card
Replacing the interface card requires temporary removal of the front card.
When an interface card is replaced with a different interface (for example,
T oken Ring to Ethernet, or vice versa), the in terface card is automatically
detected by the system.
To replace an interface card
1. Disable the PX3 module using the Disable Card command.
2. Open the cabinet front door.
3. Disconnect the front card from the backplane by rotating the two
ejector arms on each end of the card.
4. Open the cabinet rear door.
5. Remove the interface cables from the interface card.
6. Loosen the thumbscrews and remove the card.
7. Insert the interface card into the slot. Push firmly on the card to seat it
into the backplane. Secure the card to the chassis using the
thumbscrews (Figure 5-1).
Note: Thumbscrews should be finger tight only.
8. Reinsert the front card (see Front Card Installation on page 2-7).
Follow these steps to replace a PX3 front card with an identical card.
To replace a PX3 front card with an identical card
Note: Ensure that the same type of PX3 card is being replaced. For example,
you must replace a PX3 4-port module with another PX3 4-port module with the
same assembly number and revision level. The same rule also applies to the 8and 16-port PX3 modules.
1. Save the configuration files to a remote host or to flash memory. For
application configurations, refer to the appropriate application
manual.
Note: When replacing the front card on a PX3, transfer the flash memory card
from the original card to the replacement card to retain the original code image
(such as FRX, LWX, or PrimeSwitch). In some cases, it may be necessary to
transfer the DRAM. Refer to Switching Flash Memory on the PX3 on page 5-14.
2. Disable the PX module using the Disable Card command.
3. Open the cabinet front door.
4. Remove the front card by rotating the two ejector arms on each end of
the card. Slowly pull the card from the shelf, being careful not to
disturb the adjacent cards.
5. Confirm that the slot number is correct, then insert the replacement
card as shown in Figure 5-2. Seat the card in the slot by rotating the
ejector arms toward the center of the card, locking the arms inside the
shelf front edge.
7. Activate the PX platform card using the Activate Card command.
a. The card boots the application from /flash/0.
b. Copy the configuration file from flash to NVRAM.
c. Reboot.
8. If the card does not boot the application:
a. Set the boot image.
b. Copy the configuration file from flash to NVRAM.
c. Reboot.
Note: Refer to Appendix A, PX3 Operating System and Applications for details
on using the PX3 Bootstrap program to enter network configuration data and
completing the installation process.
Use this procedure to delete the old card type from the Promina database;
physically upgrade the front card (such as, a PX3 with an upgraded PX3);
and update the Promina database with the new card type.
Note: If the Promina database is not updated, when the Quer y Card command
is used, the PX3 will fail to load. Configuring the new card in the Promina
database is described in Chapter 4, Database Installation.
To replace a front card with an upgraded front card
1. Save the configuration files to a remote host or flash memory. Refer
to the appropriate application manual for application configurations.
2. Open the cabinet front door.
3. Remove the front card by rotating the two ejector arms on each end of
the card. Slowly pull the card from the shelf, being careful not to
disturb the adjacent cards.
Note: When replacing the front card on a PX3, transfer the flash memory card
from the original card to the upgrade card to retain the original code image
(software application such as FRX, LWX, or Prime Switch). In some cases, it
may be necessary to transfer the DRAM. Refer to the Switching Flash Memory on the PX3 on page 5-14.
4. Confirm that the slot is correct, then insert the replacement card into
the slot. Seat the card in the slot by rotating the ejector arms toward
the center of the card, locking the arms inside the shelf front edge.
Note: The replacement PX3 card assembly number an d re visio n level is
automatically detected by the system. The ports may need to be modified.
5. Close the cabinet front door.
6. Modify the card and its ports using the Modify Card command.
Note: Using this command to configure the PX3 platform in the Promina
database is described in Chapter 4, Database Installation. For information on
using the PX3 Bootstrap program, refer to Chapter A, PX3 Operating System and Applications.
This section describes the procedure for switching the flash memory card,
system DRAM card, or both on the PX3 front card.
1. In preparation for removing the flash memory card from the new
PX3, place the new PX3 on top of an antistatic bag on a flat surface.
2. Locate the flash memory card and socket on the new PX3
(Figure 5-3).
Figure 5-3Flash Memory Card Locatio n
5 - 14 Promina Series Packet Modules
Caution: This product contains static sensitive devices. Wrist straps and proper
grounding procedures must be followed when handling any printed circuit
assemblies.
3. The flash memory card is held in place at each end by small metal
spring clips. T o release the card, pull the metal spr ing clips away with
your thumbs while bracing your index fingers against the sides of the
socket (Figure 5-4).
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.