Banner
HomeTOCPrevNextGlossSearchHelp

Table of Contents

Installing LINF Cards in the Cisco HyperSwitch A100


Installing LINF Cards in the Cisco HyperSwitch A100

Installing LINF Cards in the Cisco HyperSwitch A100

This publication contains the following sections:


ATM Terms and Acronyms

The following are common ATM terms and acronyms for your reference:

AAL---ATM Adaptation Layer. An AAL defines the conversion of user information into cells. AAL1 and AAL2 handle isochronous traffic, such as voice and video; AAL3/4 and AAL5 pertain to data communications through the segmentation and reassembly of packets.

ATM---Asynchronous transfer mode. A cell-switching and multiplexing technology combining the benefits of circuit switching (constant transmission delay, guaranteed capacity) with those of packet switching (flexibility, efficiency for intermittent traffic). ATM is defined by ITU-T standards.

Average-rate---The average rate, in Kbps, at which a given virtual circuit (VC) will transmit.

BISDN---Broadband Integrated Services Digital Network. A set of standards under development by the ITU-T for services based on ATM switching and SONET/SDH transmission.

CCITT---Consultative Committee for International Telegraph and Telephone (This international standards body recently adopted the name International Telecommunication Union/Telecommunication Standardization Sector (ITU-T).

CLP---Cell loss priority.

DXI---Data exchange interface.

ILMI---Interim Local Management Interface---Described in the ATM Forum's UNI specification, ILMI allows end users to retrieve a basic set of information, such as status and configuration about virtual connections and addresses, for a particular UNI.

ITU-T---International Telecommunications Union Telecommunication Sector (formerly the Consultative Committee for International Telegraph and Telephone (CCITT))

LINF card---Line interface card. The LINF card contains the interface to the ATM cable. (See the section "HyperSwitch A100 LINF Card Types.")

MIB---Management Information Base.

MIC---Media Interface Connector.

MID---Message identifier---In AAL3/4 encapsulation, the 2-byte MID field allows multiplexing of streams of cells on one virtual channel.

NSAP---Network Service Access Point.

OAM---Operation and Maintenance (cells).

PDU---Protocol data unit---An OSI term for a packet.

Peak-rate---The maximum rate, in Kbps, at which VC can transmit.

PMD---Physical medium dependent. The lower half of BISDN Layer 1.

PVC---Permanent virtual circuit.

QOS---Quality of service.

Rate queues---Rate queues define the speed at which the individual VCs will transmit data to the remote end. Every VC must be associated with one rate queue. After attachment to this rate queue, the VC is assumed to have its peak rate set to that of the rate queue. Each rate queue can be configured independently to a portion of the overall bandwidth available on the ATM link. The combined bandwidths of all rate queues should not exceed the total bandwidth available. For E3, rate queues greater than 34 Mbps are disallowed. For DS3, rate queues greater than 45 Mbps are disallowed.

SAR---Segmentation and reassembly.

SDH---Synchronous Digital Hierarchy. International standard for optical digital transmission at hierarchical rates from 155 Mbps to 2.5 Gbps and greater.

SDU---Service data unit.

SONET---Synchronous Optical Network. An ATM UNI specification and American National Standards Institute (ANSI) standard (T1.1051988) for optical digital transmission at hierarchical rates from 51.840 Mbps (STS-N) to 2.5 Gbps and greater.

SONET OC3---Optical Carrier-3 specification.

SSCOP---Service Specific Connection Oriented Protocol---Resides in the service specific convergence sublayer of the ATM adaptation layer. SSCOP is used to transfer variable-length service data units between users of SSCOP. SSCOP provides for the recovery of lost or corrupted SDUs.

SSCS---Service specific convergence sublayer.

SVC---Switched virtual circuit.

UNI---User-to-Network Interface. An ATM interface defined by the ATM Forum for public and private ATM network access.

UTP---Unshielded twisted pair.

VC---Virtual circuit---Point-to-point connections to remote hosts/routers. Each ATM VC has the following characteristics associated with the VC: peak rate, average rate, burst rate, quality of service (QOS), AAL mode (AAL3/4 or AAL5), encapsulation type (LLC/SNAP, NLPID, SMDS, MUX, QSAAL). The VC characteristics are defined when the VC is created.

VCD---Virtual circuit descriptor.

VPI/VCI---Virtual path identifier/virtual channel identifier. ATM virtual connection information. A virtual path is a generic term for a bundle of virtual channels that have the same end point.


Confirming the Contents of the Shipment

The line interface (LINF) card shipping container contents includes the LINF card set (set of LINF card and front panel with window).


HyperSwitch A100 LINF Card Types

All HyperSwitch A100 LINF interfaces are full-duplex. You must use the appropriate ATM Physical Medium Dependent (PMD) interface cable to connect the HyperSwitch A100 with an external ATM network. The HyperSwitch A100 provides an interface to ATM switching fabrics for transmitting and receiving data at rates of up to 155 Mbps bidirectionally; the actual rate is determined by the PMD interface. The HyperSwitch A100 can support LINF cards that connect to the following physical layers:

For wide-area networking, ATM is currently being standardized for use in Broadband Integrated Services Digital Networks (BISDNs) by the International Telecommunications Union Telecommunication Standardization Sector (ITU-T) (formerly the Consultative Committee for International Telegraph and Telephone (CCITT)) and the American National Standards Institute (ANSI). BISDN supports rates from E3 (34 Mbps) to multiple gigabits per second (Gbps). The DS3 interface performs physical layer translation from the LINF card to a DS3 line interface in accordance with ATM Forum UNI Specification Version 3.1, ACCUNET T45 service specifications, and ANSI T1.107.


Note The quantity and card types depend on your system configuration.

Figure 1 shows the Category 5 155 Mbps UTP LINF card.

Figure 1 Category 5 UTP LINF Card

h2913.gif

Figure 2 shows the OC3 LINF card.

Figure 2 OC3 LINF Card

h2574.gif

Figure 3 shows the E3 or DS3 LINF card and Table 1 lists the distinguishing features of the two types.

Figure 3 E3 and DS3 LINF Card---Representative of Both

h2914.gif

Table 1 Distinguishing Between the E3 and DS3 LINF Cards

LINF Card Oscillator Part Number
E3 34 MHz P-8X1K
DS3 44.736 MHz P-8X1H

The jumpers shown in Figure 3 are as they should be to tie signal ground to frame ground---best for EMI as within a building. For safety compliance in certain European public carrier networks, it is required that the transmitter be connected only to signal ground and not to frame ground. To connect to signal ground, but not to frame ground, remove the jumpers on the pins indicated as frame ground in Figure 3.

Figure 4 shows the single-mode fiber-optic OC-3 LINF card.

Figure 4 Single-Mode Fiber-Optic OC-3 LINF Card

h2915.gif

Figure 5 shows the multimode fiber-optic TAXI LINF card.

Figure 5 Multimode Fiber-Optic TAXI LINF Card

h2916.gif


About Category 5 Unshielded Twisted Pair Connections

This section is derived from the ATM Forum Technical Committee ATM Physical Medium Dependent Interface Specification for 155 Mb/s over Twisted Pair Cable: AF-PHY-0015.000; September 1994. This section outlines methods of terminating the unshielded twisted pair cable for improved EMC performance including reduction of radiated emissions and increased immunity to electromagnetic noise.

Figure 6 shows the RJ-45 connectors and Table 1 shows the UTP-5 pinout (contact assignment) for the RJ-45 receptacle. Refer to Figure 6 for pin (contact) reference locations.

Figure 6 RJ-45 Connectors

h2936.gif

Table 2 Category 5 UTP Receptacle (Jack) Contact Assignment

Pin Number(1) ATM User Device ATM Network Equipment
1 Transmit + Receive +
2 Transmit -- Receive --
3 Unterminated Unterminated
4 Unterminated Unterminated
5 Unterminated Unterminated
6 Unterminated Unterminated
7 Receive + Transmit +
8 Receive -- Transmit --

(1)
The Category5 RJ-45 cable connects pin 1 on one cable end to pin 7 on the other end. Likewise, pin 2 connects to pin 8 on the other end.


Common Mode UTP Termination Guidelines

The following are proposed techniques for terminating the unused pairs of of the UTP connectors for Category 5 unshielded twisted pair (UTP) 155 Mbps unshielded twisted pair .


Example of Common Mode Resistive Termination of Pairs

Terminate the common mode impedence of the cable pairs resistively at the UNI. (See Figure 7.)

Figure 7 Example of Common Mode Resistive Termination of Pairs

h2927.gif


Example of Common Mode Termination to Chassis Reference

Terminate one or more the the unused cable pairs to the chassis reference of the equipment. (See Figure 8.)

Figure 8 Example of Common Mode Termination to Chassis Reference

h2925.gif


Example of Mode Termination to Chassis Reference with Chokes

Terminate one or more the the unused cable pairs to the chassis reference of the equipment with longitudinal chokes in the active pairs. (See Figure 9.)

Figure 9 Example of Mode Termination to Chassis Reference with Chokes

h2926.gif


Safety Recommendations

Follow these guidelines to ensure general safety:


Safety with Electricity

fig_2.gif


Warning Before working on equipment that is connected to power lines, remove jewelry (including rings, necklaces, and watches). Metal objects will heat up when connected to power and ground and can cause serious burns or can weld to the terminals.

Follow these guidelines when working on equipment powered by electricity:


Preventing Electrostatic Discharge Damage

Electrostatic discharge (ESD) can damage equipment and impair electrical circuitry. It occurs when electronic printed circuit cards are improperly handled and can result in complete or intermittent failures. Always follow ESD prevention procedures when removing and replacing cards. Ensure that the router chassis is electrically connected to earth ground. Wear an ESD-preventive wrist strap, ensuring that it makes good skin contact. Connect the clip to an unpainted chassis frame surface to safely channel unwanted ESD voltages to ground. To properly guard against ESD damage and shocks, the wrist strap and cord must operate effectively. If no wrist strap is available, ground yourself by touching the metal part of the chassis.

fig_3.gif

Caution Periodically check the resistance value of the antistatic strap, which should be within the range of 1 through 10 Mohms.


Required Equipment for Installation

Proper installation requires the following equipment:


Note Ensure all interface cables that connect to the HyperSwitch A100 are shielded cables with ferrite cores and connectors with metallic shells at both ends. Use of other cable types may result in interference to radio and TV reception.


Note No communications software is necessary if the PC or workstation operates in terminal mode; however, installing communications software simplifies operations.


Main Unit Parts

References throughout this publication refer to the HyperSwitch A100 front and rear panel layouts. Figure 10 shows the front panel layout and Figure 11 shows the rear panel layout.

Figure 10 HyperSwitch A100 Front Panel Layout

h2410.gif

Figure 11 HyperSwitch A100 Rear Panel Layout

h2411.gif

Figure 12 and Figure 13 show HyperSwitch A100 internal views.

Figure 12 HyperSwitch A100 Internal View

h2587.gif

Figure 13 Expanded Internal View (Motherboard)

h2567.gif


Opening the Cover

Do the following to open the HyperSwitch A100 cover:

Step 1 Provide protection against static electricity.

Step 2 Confirm that the HyperSwitch A100 power switch is in the OFF position.

Note O is OFF, and I is ON.

Step 3 Using a Phillips screwdriver, remove the six outer screws from the PROC card panel. Figure 14 shows the screw locations on the PROC card panel.

Step 4 Grasp the card ejectors on the PROC card panel and pull the card outward.

Step 5 Turn the HyperSwitch A100 on its side and then turn it upside down.

Step 6 Using a Phillips screwdriver, remove the seven outer screws from the bottom of the HyperSwitch A100. See Figure 15 for the screw locations.

Step 7 Return the HyperSwitch A100 to the upright position.

Figure 14 PROC Card Panel Layout

h2568.gif

Figure 15 HyperSwitch A100 Bottom View

h2569.gif

Step 8 Remove the three outer screws from the back of the HyperSwitch A100. See Figure 11 for the screw locations.

Step 9 Hold both sides of the HyperSwitch A100 cover and slide it slightly forward (approximately 25 millimeters or 1 inch). (See Figure 16.)

Step 10 Lift the cover upward. (See Figure 17.)

fig_1.gif Caution If the LINF cards are already installed, lifting the cover before properly sliding it forward may damage the optical connector on the LINF cards.

Figure 16 Sliding the HyperSwitch A100 Cover

h2570.gif

Figure 17 Lifting the HyperSwitch A100 Cover

h2571.gif


Preparing to Install LINF Cards

This section describes the initial installation method for the two LINF card types: OC3 (155 Mbps) and Transparent Asynchronous Transmitter/Receiver Interface (TAXI) (100 Mbps). All LINF card types install the same way. Before installing LINF cards, ensure the power switch on the back of the HyperSwitch A100 is OFF.

Table 3 provides recommended mounting positions in the slots where LINF cards are installed, depending on the number of cards installed. If designating the HyperSwitch A100 as a slave switch, always install OC3 LINF card in Slot 0.


Note The procedure to set the synchronization mode to slave occurs later when setting system configuration data.

Table 3 LINF Card Mounting Positions

Number of Interface Cards Suggested Slot Mounting Locations
1 0
2 0,2
3 0,2,4
4 0,2,4,6
5 0,2,4,6,8
6 0,2,4,6,8,10
7 0,2,4,6,8,10,12
8 0,2,4,6,8,10,12,14
9 0-2,4,6,8,10,12,14
10 0-...4,6,8,10,12,14
11 0-......6,8,10,12,14
12 0-........8,10,12,14
13 0-...........10,12,14
14 0-...............12,14
15 0-...................14
16 0-......................15


Installing LINF Cards

Perform the following procedure to install a LINF card:

Step 1 Remove the LINF card from the container.

Step 2 Install the LINF card from the top of the slot. Ensure the LINF card is securely fixed to the LINF stopper at the rear of the HyperSwitch A100 main unit.

Step 3 Match the screw holes on the LINF card with the screw holes on the HyperSwitch A100; then, insert the screws. (See Figure 18.) Use a standard screwdriver to fasten the screws.

Figure 18 Installing a LINF Card

h2577.gif


Replacing the Front Panel

Perform the following procedure to replace the front panel (without window) of the slot where the LINF card is installed with a front panel (with window) packed with the LINF card.

Step 1 From the opposite side of the cover, remove the front panel (without window) from the slot where the LINF card is installed. Use a Phillips screwdriver to remove the two screws at top and bottom that fasten the front panel on the opposite side of the cover. (See Figure 19.)

Step 2 Install the front panel (with window) and fasten it with the two screws to the top and bottom. Ensure the front panel is right side up.


Closing the Cover

Do the following to close the HyperSwitch A100 cover.

Step 1 Put the cover on the base starting approximately 25 millimeters or 1 inch from the front. Then slide the cover back until the screw holes align.

Step 2 Using a Phillips screwdriver, insert and fasten the three screws to the back of HyperSwitch A100.

Step 3 Turn the HyperSwitch A100 on its side and then turn it upside down.

Step 4 Insert and fasten the seven outer screws to the bottom of the HyperSwitch A100.

Step 5 Return the HyperSwitch A100 to the upright position.

Step 6 Grasp the card ejectors on the PROC card panel and insert the card into the HyperSwitch A100 front panel.

Step 7 Insert and fasten the six outer screws to the PROC card panel.

Figure 19 Screw Locations Seen from the Reverse Side of the Cover

h2578.gif


Connecting Optical Cable to a LINF Card

This section provides the procedure for connecting optical cables to the LINF cards installed in the HyperSwitch A100. The upper optical connector on LINF cards is for receive and the lower optical connector is for transmit. Use a single-core or two-core optical cable to connect the LINF cards installed on the HyperSwitch A100. Figure 20 shows the single-core and two-core cables.


Note Ensure all interface cables that connect to the HyperSwitch A100 are shielded cables with ferrite cores and connectors with metallic shells at both ends. Use of other cable types may result in interference to radio and TV reception.

Figure 20 Single-Core and Two-Core Cable

h2581.gif

When using a single-core optical cable, ensure the transmission end connects to the reception connector of one device and that the reception end connects to the transmission connector of the other device. Use the appropriate two-core cable, straight (A-C, B-D connections) or cross (A-D, B-C connections). When connecting two or more HyperSwitch A100 units with two-core cable, use cross-cable connection.

To connect optical cables, perform the following procedure:

Step 1 The type of optical cable differs depending on LINF card type. Have enough optical cables to accommodate the LINF card type and quantity.

Step 2 Connect the appropriate optical cable to the front panel (with window) of the slot where the LINF card is installed.


Connecting the Console Terminal

This section provides the procedure for connecting an EIA/TIA-232 cable to the HyperSwitch A100. To connect the cable, do the following:

Step 1 The EIA/TIA-232 connector for the console terminal configuration differs for each console terminal device. Use an EIA/TIA-232 cable that has a connector matching the console terminal on one end and a connector with D-sub 9-pin male connector for the HyperSwitch A100 on the other end. Figure 21 shows connectors for an IBM compatible PC and the HyperSwitch A100.

Step 2 Connect the EIA/TIA-232 cable (9-pin end) to the EIA/TIA-232 connector on the front of the HyperSwitch A100. The HyperSwitch A100 has two EIA/TIA-232 connectors on the front. Use the connector on the left-hand side (SIO-1). See Figure 22.

Step 3 Connect the other end of the EIA/TIA-232 cable to the console terminal.

Figure 21 EIA/TIA-232 Cable Connectors

h2582.gif

Figure 22 Console Terminal to HyperSwitch A100 Connection

h2583.gif


Connecting to the NMS

Using the Simple Network Management Protocol (SNMP) over User Datagram Protocol (UDP)/Internet Protocol (IP)/ATM Adaptation Layer 5 (AAL5), the HyperSwitch A100 communicates with the NMS manager via an ATM line. Figure 23 shows the connection of the HyperSwitch A100 to the console terminal and the NMS. Refer to the NMS configuration documentation to configure the interface between the HyperSwitch A100 and the NMS.

Figure 23 HyperSwitch A100 to Console Terminal and NMS Connection

h2584.gif


Connecting the Power Supply

Complete the tasks described in the preceding sections before connecting the power cable to the HyperSwitch A100 and turning the power ON.

fig_4.gif

Caution Use an uninterruptible power supply (UPS) power system to prevent system outage in case of a commercial power failure.

To connect the power cable, do the following:

Step 1 Connect the power cable to the power connector on the back of the HyperSwitch A100.

Step 2 Plug the power cable into a power outlet.

Note Never use an adapter to share the power outlet used for the HyperSwitch A100 with another electrical device.

Step 3 Set the power switch on the back of the HyperSwitch A100 to the ON position.

Step 4 Ensure the green Power light emitting diode (LED) on the front of the HyperSwitch A100 goes ON.

Step 5 Set the power switch on the back of the HyperSwitch A100 to the OFF position.

Note Turning OFF the power switch of the HyperSwitch A100 discontinues communications. Do not turn OFF the power switch unless necessary during operation.

To connect the console terminal power supply, plug the console terminal power cord into a power outlet. Refer to the documentation provided with the console terminal for additional information.


Note O is OFF and | is ON.

A self-diagnostic test runs when the HyperSwitch A100 is powered ON or reset. The results display on the console terminal. The following example shows self-diagnostic test output:

        Cisco Systems, Inc. ATM HyperSwitch
Software Version 1.2(0)
Boot ROM Version K07 10 Sep 94
ATMSIG Version 1.2(0)
Hardware Configuration:
CPU Board      : OK;
Bus Convertor  : OK;
Switch Core    : OK;
Gateway PAD    : OK;
Slot 0: OC-3C(MMF)     OK;
Slot 1: OC-3C(MMF)     OK;Slot 2: 100M-TAXI      OK;
Slot 3: 100M-TAXI      OK;
Slot 4: Not Installed;
Slot 5: Not Installed;
Slot 6: Not Installed;
Slot 7: Not Installed;
Slot 8: Not Installed;
Slot 9: Not Installed;
Slot10: Not Installed;
Slot11: Not Installed;
Slot12: Not Installed;
Slot13: Not Installed;
Slot14: Not Installed;
Slot15: Not Installed;
System Initialization finished.
A100>

To power OFF the HyperSwitch A100, set the power switch to the OFF position. The Power LED goes OFF.


Data Setting Procedure

Figure 24 and Figure 25 show two parts of a flowchart of the configuration data setting procedure. The following sections provide command input information that corresponds to the commands indicated in the flowchart.


Basic Command Input

Input commands entered at the console terminal provide instructions to the HyperSwitch A100. Commands for the HyperSwitch A100 comprise user commands, which show configuration data, and privileged commands, which show and configure system data.

Figure 24 Initial Installation Data Setting Procedure (Part 1)

h2585.gif

Figure 25 Initial Installation Data Setting Procedure (Part 2)

h2586.gif

The following example shows basic command input format:

 prompt command subcommand P1 P2 ...         

The system shows two prompt types: > and #. The > prompt indicates operation in user mode, and the # prompt indicates operation in privileged mode.

If the host name (for example, A100) is registered for the system, it shows before the prompt.

Following are mode examples.

User mode example:

A100>        

Privileged mode example:

A100#        

Enter a space between the command, subcommand, and each parameter. Parameters are indicated as P1, P2, and so on.

The system does not distinguish between uppercase and lowercase characters except in setting or reading the password.


Displaying LINF Card Data

The following list gives command information to display LINF data for cards installed in the HyperSwitch A100. Data does not display for a line without a LINF card installed or for a line whose information cannot be read because of a failure.

show interface

Command mode: user

Format:

A100> show interface        

Output:

Line Number UNI/NNI Physical Layer Forum/ITU Valid VPI Valid VCI         
     0         0       2               0         4         8
     1         0       2               0         4         8
     ·
     ·
     ·
     15        0       2               0         4         8

Confirm that the line numbers of the installed LINF cards display. When a specific line number does not display, the corresponding LINF card is not installed, the LINF card is improperly installed, or a LINF hardware error exists. Turn OFF the HyperSwitch A100 and check the LINF card.

The numbers displayed in fields to the right of the line number are line configuration parameters. The following list gives initial settings of these parameters:

Following are possible error messages.

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal

Explanation Parameter(s) was entered.

Recommended Action Reenter the command without specifying a parameter.


Enter Privileged Command Mode

The following list gives command information to enter the privileged command mode and to set a password that allows entry to the privileged command mode.

enable

Command mode: user

Format:

A100> enable        

Enter the enable command.

When the command name is wrong, the following messages display:

Error Message Command name is illegal

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal

Explanation Parameter(s) was entered.

Recommended Action Reenter the command without specifying a parameter.


Set Clock Synchronization Mode

The following list gives command information to set the clock synchronization mode. When a HyperSwitch A100 unit connects to another HyperSwitch A100 unit or to a different type of device, this function designates this HyperSwitch A100 as master or slave.

set clock

Command mode: privileged

Format:

A100# set clock p1         

Explanation:

P1: Master/slave identifier

Before setting the slave mode, ensure an OC3 LINF card is installed in Slot 0 of the HyperSwitch A100.

Output:

Operational Mode: xxxxxx        

The console terminal displays the set mode: Master or Slave.


Set Clock Synchronization Mode Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal.

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Too many parameters are entered.

Recommended Action Reenter the command.

Error Message Specified parameter is out of range.

Explanation The specified parameter value is out of the allowable range.

Recommended Action Reenter the command.


Register Line

The following list gives command information to register a line. This function can change the following initial settings of a line:

To confirm the initial settings, enter the show interface command.

set interface

Command mode: privileged

Format:

A100# set interface p1 p2 p3 p4 p5        

Explanation:

P1: Line number (0-15)

P2: Interface type

P3: Standard body conformance

P4: Length of valid VPI bits (0-12; default = 4.)

P5: Length of valid VCI bits (5-12; default = 8.)

Output:

Line interface P1 has been registered.        

The initial setting of line number specified in P1 changed.


Register Line Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal.

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Too many or not enough parameters are entered.

Recommended Action Reenter the command.

Error Message Specified line is invalid.

Explanation The specified line cannot be used.

Recommended Action Use the show alarm command to check the error status, or use the show interface command to check the installation status of the LINF card.

Error Message Specified UNI/NNI is out of range.

Explanation A value other than 0 or 1 is entered in P2 (UNI/NNI).

Recommended Action Reenter the command.

Error Message Specified Forum/ITU parameter is out of range.

Explanation A value other than 0 or 1 is entered in P3 (ATM Forum/ITU).

Recommended Action Reenter the command.

Error Message Specified VALID VPI is out of range.

Explanation A value more than 7 is entered in P4 (valid VPI).

Recommended Action Reenter the command.

Error Message Specified VALID VCI is out of range.

Explanation A value less than 5 or more than 12 is entered in P5 (valid VCI).

Recommended Action Reenter the command.

Error Message Specified VALID VPI+VALID VCI is out of range.

Explanation The sum of P4 and P5 values is more than 12.

Recommended Action Reenter the command.

Error Message Connection is already established on this line.

Explanation Because the pvc command established the connection, the line interface cannot be changed.

Recommended Action Clear the connection before using this command.


Set Permanent Virtual Circuit

The following list gives command information to set a point-to-point permanent virtual circuit (PVC). This command becomes effective immediately after it is set.

pvc establish

Command mode: privileged

Format:

A100# pvc establish p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13        

Explanation:

P1: Connection type

P2: Traffic type

P3: Transmission rate (specify in Mbps; when P2=1, specify P3=0)

P4: Low line number (0-15, corresponds to slot number)

P5: Low VPI (0-4095)

P6: Low VCI (0-4095)

P7: Low Usage Parameter Value Peak (UPVP) (0-512)

P8: Low Cell Overflow Option Peak (COOP) action taken when Usage Parameter Control (UPC) cell loss occurs

P9: High line number (0-15, corresponds to slot number)

P10: High VPI (0-4095)

P11: High VCI (0-4095)

P12: High UPVP (0-512) (when P1=0, specify P12=0)

P13: High COOP action taken when UPC cell loss occurs

Output:

Uni/Bi/Multicast direction Guaranteed/Best Effort Connection has been established.        
Low:       xx, xxxx, xxxxx, xxx, x

High:      xx, xxxx, xxxxx, xxx, x

The entered values for line number, VPI, VCI, UPVP, and COOP display.


Set Permanent Virtual Circuit Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal.

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Too many or not enough parameters are entered.

Recommended Action Reenter the command.

Error Message Specified line is invalid.

Explanation The specified line cannot be used.

Recommended Action Use the show alarm command to check the error status, or use the show interface command to check the LINF card installation status.

Error Message Specified VPI is out of range.

Explanation The specified VPI value (P5 or P10) is out of the range of 0 to 4095.

Recommended Action Reenter the command.

Error Message Specified VCI is out of range.

Explanation The specified VCI value (P6 or P11) is out of the range of 0 to 4095.

Recommended Action Reenter the command.

Error Message Specified UPVP parameter is out of range.

Explanation The specified UPC window size UPVP (P7 or P12) is out of the range of 0 to 512.

Recommended Action Reenter the command.

Error Message Specified COOP parameter is out of range.

Explanation The specified UPC cell loss parameter COOP (P8 or P13) is neither 0 nor 1.

Recommended Action Reenter the command.

Error Message Specified VPI+VCI is out of range.

Explanation The specified VPI+VCI is inconsistent with the value set by the set interface command.

Recommended Action Use the set interface command to check parameters.


Deleting a PVC

If a PVC is set incorrectly, first delete the PVC using the pvc delete command; then, reenter the pvc establish command. Use the pvc delete command as follows:

Format:

A100# pvc delete p1 p2 p3 p4 p5 p6 p7 p8        

Explanation:

P1: Connection type

P2: Traffic type

P3: Low line number (0-15, corresponds to slot number)

P4: Low VPI (0-4095)

P5: Low VCI (0-4095)

P6 High line number (0-15, corresponds to slot number)

P7: High VPI (0-4095)

P8: High VCI (0-4095)

Output:

Uni/Bi/Multicast direction Best Effort/Guaranteed Connection has been deleted.         
Low:  xx, xxxx, xxxxx, xxxx, x
High: xx, xxxx, xxxxx, xxxx, x

Line number, VPI, VCI, UPVP, and COOP data for the deleted line display. UPVP and COOP values were registered with the pvc establish command.


Error Message

Error Message No such connection

Explanation The specified connection does not exist.


Note Some error messages explained in the pvc establish command discussion may display.


Setting Multicast Command

To set a multicast (point-to-multipoint) connection, use the pvc establish command, which establishes a connection, and the pvc add command, which adds a PVC endpoint for multicast.

The system accepts only multicast connection when the connection is added or when an endpoint is deleted. When deleting the multicast connection, delete the endpoints one by one. (The deletion order need not be the same as the setup order.)

Use the pvc establish command to set the connection type to multicast; then, use the pvc add command to add the endpoint. Enter the same source parameters (line number, VPI, and VCI) as those specified in the pvc establish command.


Note The traffic type (bit rate type) on the endpoint becomes the same as that specified by pvc establish command.

pvc add

Command mode: privileged

Format:

A100# pvc add p1 p2 p3 p4 p5 p6         

Explanation:

P1: Low line number (0-15, corresponds to the slot number)

P2: Low VPI (0-4095)

P3: Low VCI (0-4095)

P4: High line number (0 to 15, corresponds to the slot number)

P5: High VPI (0-4095)

P6: High VCI (0-4095)

Output:

Connection endpoint has been added.        
Modified Connection: 
Low: xx, xxxx, xxxxx, xxxx, x
High: xx, xxxx, xxxxx
  ·
  ·
  ·

Line number, VPI, VCI, UPVP, and COOP data display for added endpoints. UPVP and COOP were registered with the pvc establish command. Output continues to display up to the last endpoint.


Setting Multicast Command Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal.

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Too many or not enough parameters are entered.

Recommended Action Reenter the command.

Error Message Specified line is invalid.

Explanation The specified line cannot be used.

Recommended Action Use the show alarm command to check the error status or the show interface command to check LINF card installation status.

Error Message Specified VPI is out of range.

Explanation The specified VPI value (P2 or P5) is out of the range of 0 to 4095.

Recommended Action Reenter the command.

Error Message Specified VCI is out of range.

Explanation The specified VCI value (P3 or P6) is out of the range of 0 to 4095.

Recommended Action Reenter the command.

Error Message Specified VPI+VCI is out of range.

Explanation The specified VPI+VCI is inconsistent with the value set by the SET interface command.

Recommended Action Use the set interface command to check parameters.

Error Message Specified connection is uni/bi-direction

Explanation The specified low endpoint in the connection is registered as unidirectional or bidirectional.

Recommended Action Change the PVC setting to multicast by deleting the connection using the pvc delete command and reentering the connection using the pvc establish command with multicast connection type specified (P1=2).

Error Message ICI Hunt Error.

Explanation The memory for point-to-point connection is exhausted.

Recommended Action None. New allocation is not allowed.

Error Message BCI Hunt Error

Explanation The memory for multicast connection is exhausted.

Recommended Action None. New allocation is not allowed.


Note If a registered endpoint is set incorrectly using the pvc add command, first delete the endpoint using the pvc remove command; then, reenter the PVC using the pvc add command.

Use the pvc remove command as follows. This command deletes one endpoint at a time.

Format:

A100# pvc remove p1 p2 p3 p4 p5 p6        

Explanation:

P1: Low line number (0-15, corresponds to the slot number)

P2: Low VPI (0-4095)

P3: Low VCI (0-4095)

P4: High line number (0-15, corresponds to the slot number)

P5: High VPI (0-4095)

P6: High VCI (0-4095)

Output:

Connection endpoint has been removed.         
Modified Connection: 
Low:: xx, xxxx, xxxxx, xxxx, x 
High: : xx, xxxx, xxxxx 
 ·
 ·
 ·


Line number, VPI, VCI, UPVP, and COOP data display for the removed endpoint. UPVP and COOP values were registered with the pvc establish command. Output continues to display up to the last endpoint.


PVC Remove Error Message

Error Message No such connection

Explanation The specified connection does not exist.


Note Some error messages explained in the pvc add command discussion may display.


Setting Switched Virtual Circuits

The following are commands to set switched virtual circuits (SVC).


Note Command descriptions relating to switched virtual circuits may change because the SVC specification is in the developmental stage.

route add

Command mode: privileged

Format:

A100# route add P1 P2 P3 P4        

Explanation:

P1: Address (arbitrary bit string in 20 bytes hexadecimal for Network Service Access Point (NSAP) format or in 15 bytes hexadecimal for E.164 format.)

To perform partial collation, use the value X. For E.164 format, system appends X.

Note If all 20 bytes are used for the address, the routing table increases in size, thereby lowering the processing capacity. To enhance the processing capacity, use a tree structure in which the upper address is allocated to the switch identifier. Then, only the switch identifier can specify the destination address.

P2: Address format (NSAP or E.164)

P3: First choice line number

P4: Second choice line number (When first choice line number specified in P3 has errors or is not installed, system uses this line number.)

Output:

SVC route has been added.        


Setting Switched Virtual Circuits Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal.

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Too many or not enough parameters are entered.

Recommended Action Reenter the command.

Error Message Specified parameter is invalid.

Explanation An invalid parameter was entered.

Recommended Action Reenter the command with valid parameters.

Error Message Routing Table Overflow.

Explanation The memory for the routing table is exhausted.

If an SVC is set incorrectly, delete the SVC using the route delete command or the route flush command. Use either the command to delete an individual SVC or the SVC routing table as follows:


Deleting an Individual SVC

Format:

A100# route delete p1 p2        

Explanation:

P1: Address (arbitrary bit string in 20 bytes hexadecimal for NSAP format or in 15 bytes hexadecimal for E.164 format. To perform partial collation, use the value X. For E.164 format, the system appends X.)

P2: Address format (NSAP or E.164)

Output:

SVC route has been deleted.        


Deleting an SVC Error Message

Error Message Specified routing table is non-existing.


Note Some error messages explained under the route add command may display.


Deleting the Entire SVC Routing Table

Format:

A100# route flush        

Output:

SVC routing table has been flushed.         

All contents of the SVC routing table are deleted.


Note No specific error messages display for this command; however, some messages explained in the route add command discussion may display.


NMS-Related Information Input

The network management system (NMS) executes display functions over an ATM network. Set NMS-related information in the privileged command mode. Use NMS-related privileged commands only when the NMS connects to the HyperSwitch A100 for control using SNMP.


Setting IP Address, Mask, and HyperSwitch A100 Host Name

The following list gives command information to set the IP address, mask, and host name of the HyperSwitch A100.

set local

Command mode: privileged

Format:

A100# set local p1 p2 p3        

Explanation:

P1: Host name (up to eight alphabetic characters)

P2: IP address (dot notation)

P3: Mask (dot notation)

Output:

Local configuration data has been set.        


Set Command Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal.

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Too many or not enough parameters are entered.

Recommended Action Reenter the command.

Error Message Specified HOST NAME is out of range.

Explanation An escape sequence was entered as the host name.

Recommended Action Reenter the command.

Error Message Specified IP ADDRESS is out of range.

Explanation The dotted decimal notation (four decimal values separated by dots) does not specify the IP address, or a decimal value more than 256 was entered.

Recommended Action Reenter the command.

Error Message Specified MASK is out of range.

Explanation The dotted decimal notation (four decimal values separated by dots) does not specify the mask, or a decimal value more than 256 was entered.

Recommended Action Reenter the command.


Set NMS IP Address, Mask, and Access Information

The following lists command information to set NMS IP address, mask, and access information.

set nms

Command mode: privileged

Format:

A100# set nms p1 p2 p3 p4 p5        

Explanation:

P1: NMS number (0-3)

P2: IP address (dot notation)

P3: Mask (dot notation)

P4: Community name (up to 16 alphanumeric characters)

P5: Access privileged

Output:

NMS information has been set.        


NMS Error Messages

Error Message Command name is illegal

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal.

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Too many or not enough parameters were entered.

Recommended Action Reenter the command.

Error Message Specified NMS Number is out of range.

Explanation The value of the specified NMS number parameter is out of range.

Recommended Action Reenter the command.

Error Message Specified IP ADDRESS is out of range.

Explanation The dotted decimal notation (four decimal values separated by dots) does not specify an IP address, or a decimal value more than 256 was entered.

Recommended Action Reenter the command.

Error Message Specified MASK is out of range.

Explanation The dotted decimal notation (four decimal values separated by dots) does not specify mask, or a decimal value more than 256 was entered.

Recommended Action Reenter the command.

Error Message Specified COMMUNITY NAME is out of range.

Explanation An escape sequence is entered as the community name.

Recommended Action Reenter the command.

Error Message Specified ACCESS privilege is out of range.

Explanation The specified access privilege parameter is neither 0 nor 1.

Recommended Action Reenter the command.


Delete an NMS Connection

The set nmsdelete nms command deletes up to four NMS connections at once.

set nmsdelete p1

Format:

A100# set nmsdelete p1        

Format explanation:

P1: NMS number (0-3)

Command example:

A100# set nmsdelete 1        
NMS information and NMS route information has been deleted.


Set Communications Path Between the HyperSwitch A100 and NMS

The following list gives command information to set a communication path between the HyperSwitch A100 and NMS.

set nmsroute

Command mode: privileged

Format:

A100# set nmsroute p1 p2 p3 p4        

Explanation:

P1: NMS number (0-3)

P2: Line number (0-15)

P3: VPI (0-4095)

P4: VCI (0-4095)

Output:

NMS ROUTE information has been set.        


Set Route Command Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal.

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Too many or not enough parameters are entered.

Recommended Action Reenter the command.

Error Message Specified line is invalid.

Explanation The specified line cannot be used.

Recommended Action Use the show alarm command to check the error status, or use the show interface command to check the LINF installation status.

Error Message Specified VPI is out of range.

Explanation The VPI parameter (P3) value is out of range.

Recommended Action Reenter the command.

Error Message Specified VCI is out of range.

Explanation The VCI parameter (P4) value is out of range.

Recommended Action Reenter the command.

Error Message Specified Valid VPI+VCI is out of range.

Explanation The specified VPI+VCI is inconsistent with the set interface command.

Recommended Action Use the set interface command to check the parameters.

Error Message Connection is already established on this line

Explanation Because a connection is already established on this line by the pvc command, the line interface cannot be changed.

Recommended Action Clear the connection first.


Setting MIB II Administrator and Installation Site

The following list gives the command to set information defined in Management Information Base (MIB) II sysContact (administrator) and sysLocation (installation site).

set mib

Command mode: privileged

Format:

A100# set mib p1 p2        

Explanation:

P1: sysContact (administrator) (up to 32 alphanumeric characters)

P2: sysLocation (installation site) (up to 32 alphanumeric characters)

Output:

MIB information has been set.        


Set MIB Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Sub command name is illegal.

Explanation The specified subcommand is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Too many or not enough parameters are entered.

Recommended Action Reenter the command.

Error Message Specified sysContact is out of range.

Explanation The number of characters specified for the administrator is out of the allowable range.

Recommended Action Reenter the command.

Error Message Specified sysLocation site is out of range.

Explanation The number of characters specified for the installation site is out of the allowable range.

Recommended Action Reenter the command.


Saving Configuration Data

The following list gives command information to save configuration data set by the privileged commands in Flash memory. To make NMS-related data effective, always save the data and then reset the HyperSwitch A100.

save

Command mode: privileged

fig_5.gif

Caution To avoid the loss of your entered configuration data, after entering the save command and before pushing the reset button, wait for the displayed output system data has been saved . The save process can take over five minutes.

Format:

A100# save        

Output:

Now Data saving ! Please do NOT push reset button till        
the "save" is complete........
System data has been saved.


Save Command Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Parameter(s) was entered.

Recommended Action Reenter the command without specifying a parameter.


Leaving Privileged Mode

The following list gives command information to exit the privileged mode and return to the user mode.

exit

Command mode: privileged

Format:

A100# exit        

Output:

A100>        

The prompt changes from # to >.


Exit Command Error Messages

Error Message Command name is illegal.

Explanation The specified command is not defined.

Recommended Action Reenter the command.

Error Message Number of parameter is illegal.

Explanation Parameter(s) was specified.

Recommended Action Reenter the command without specifying a parameter.


Resetting the HyperSwitch A100

When NMS-related commands are set, always save the data, exit the privileged mode, and press the Reset button on the HyperSwitch A100 front panel.


Disconnecting the Console Terminal

When verification detects no abnormality, the HyperSwitch A100 is ready for normal operation.

The HyperSwitch A100 does not require a console terminal for normal operation. If the console terminal is dedicated to operating and administering the HyperSwitch A100, do not disconnect it. However, if the console terminal is used for other purposes, remove the EIA/TIA-232 connector to disconnect the console terminal from the HyperSwitch A100.


Note If the console terminal is disconnected and the system requires maintenance, reconnect the EIA/TIA-232 cable to the console terminal and the HyperSwitch A100, and verify operation.

fig_6.gif

fig_7.gif

HomeTOCPrevNextGlossSearchHelp
-

Copyright 1988-1995 © Cisco Systems Inc.