LightStream 1010 CES T1/E1 Port Adapter Module Configuration Note

Product Numbers: WAI-T1C-4RJ48, WAI-E1C-4RJ48, WAI-E1C-4BNC

This document contains instructions for installing and configuring the CES T1/E1 port adapter module for the LightStream 1010 ATM switch.

For a more complete description of the CLI commands used in configuring and customizing the CES T1/E1 port adapter module for your particular networking needs, refer to the LightStream 1010 ATM Switch Software Configuration Guide.

For complete procedures for preparing your site and network equipment for the installation of the LightStream 1010 ATM Switch carrier module (CM) and associated port adapter module (PAM) hardware, refer to the LightStream 1010 ATM Switch PAM Installation Guide.

For an in-depth description of CLI command syntax and command line options for configuring and maintaining the CES T1/E1 port adapter module, refer to the LightStream 1010 ATM Switch Command Reference publication.

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

What is a LightStream 1010 ATM Switch?

The LightStream 1010 ATM switch, hereinafter referred to as the LS1010 switch or LS1010 chassis, consists of a five-slot, modular chassis that features the option of including dual, fault-tolerant, load-sharing power supplies (see Figure 1).

The central slot in the LS1010 is dedicated to a single, field-replaceable ATM switch processor (ASP) module that supports a data rate of 5 Gbps through a fully non-blocking switch fabric. The ASP also supports the feature card and high performance reduced instruction set (RISC) processor that provides the central intelligence for the switch.

The remaining four slots support up to four hot-swappable carrier modules (CMs). Each CM supports up to two hot-swappable port adapter modules (PAMs) for a maximum of eight PAMs per switch, thereby enabling the LS1010 to support a variety of desktop, campus backbone, and wide-area network (WAN) interfaces.

Figure 1: Front View of LightStream 1010 ATM Switch

The LS1010 provides switched ATM connections to individual workstations, servers, local area network (LAN) segments, or other ATM switches and routers using fiber-optic cable, twisted-pair cable, and coaxial cable.

The LS1010 switch can accommodate up to eight CES modules in a standard 19-inch (48-centimeter) rack.

Warning Only trained and qualified personnel should install or replace the LightStream 1010 ATM Switch, chassis, power supplies, fan assembly, or port adapter modules.

Figure 2 shows an example of a network configuration that uses the LS1010 switch in a high-performance workgroup environment.

Figure 3 shows an example of a network configuration that uses several LS1010 switches in a campus backbone array.

Figure 2: LightStream 1010 Workgroup Configuration Example


Figure 3: LightStream 1010 Backbone Configuration Example

What is a CES T1/E1 Port Adapter Module?

A CES T1/E1 port adapter module (PAM) is an LS1010 interface module that supports the emulation of existing time division multiplexing (TDM) circuits over ATM networks. This circuit emulation service (CES) enables LS1010 users to interconnect the following types of devices in transporting constant bit rate (CBR) voice and video traffic through an ATM network:

• Private Branch eXchanges (PBXs)

A PBX is a device that provides local voice switching and voice-related services within a private network. PBXs often have a local ATM application program interface (API) that enables the use of ATM services, such as circuit emulation.

• Time division multiplexing (TDM) devices

TDM refers to a method in which the total bandwidth capacity of a transmission facility (a TDM device) is multiplexed among a number of channels on the basis of fixed time slots.

• Video conferencing devices

A video conferencing device is one that is capable of generating, conveying, or reproducing television audio/video signals.

The LS1010 CES modules (see Figure 4) are available in three distinct versions:

• CES T1 PAM--Equipped with four RJ-48C connectors (one per port).

• CES E1 PAM (120-ohm version)--Equipped with four RJ-48C connectors (one per port).

• CES E1 PAM (75-ohm version)--Equipped with eight BNC connectors (two per port).

Each CES module version contains four ports for CBR data transport.

Figure 4: CES Port Adapter Modules for LS1010 ATM Switch

For convenience throughout this document, these PAMs will be referred to collectively as "CES modules" or individually as a "CES module." Where specificity is appropriate to a particular discussion, the module in question will be explicitly identified.

Since ATM is a cell-oriented transmission technology, CES circuits in an ATM network must be emulated in order to provide required support for user voice and video traffic. Hence, circuit emulation services (CES) in an ATM network must be comparable in functionality to that currently provided by today's existing time division multiplexing (TDM) telephony devices.

For example, consider a situation in which a user is currently employing physical telephone circuits connected to PBXs (Private Branch eXchanges) as the primary means of CBR data transmission. For a variety of reasons, such a user may wish to have equivalent CBR functionality available within an ATM network.

A CES module, together with appropriate software, is the answer to such a user's needs. A CES module provides the means to emulate the user's current telephony technology and, more importantly, to migrate that functionality into an operational ATM network.

In so doing, an LS1010 user is able to reduce networking costs by consolidating separate voice, data, and video facilities into a single, reliable, multivendor ATM network. With equivalent CBR technology thus available within the ATM network, the user's view of CBR traffic does not change in any fundamental way--CBR data is still introduced into a circuit, and CBR data still emanates from a circuit.

The essential distinction, however, is that an emulated CBR circuit employs a different medium for data transport, namely, the ATM network. Nevertheless, an emulated circuit behaves logically as though the communicating entities were actually physically connected by wires.

The CES modules provide connectivity to other LS1010 interface modules and, hence, to an ATM network at large. This connectivity is provided by means of four CBR ports (0, 1, 2, and 3) on the faceplate of each module. Associated with each port is a set of LEDs that indicates the operational status of the port.

Functionality Supported by CES Modules

The functionality supported by a CES module includes the following:

• Circuit Emulation Services Interworking Function (CES-IWF). This function enables communications to occur between CBR and ATM UNI interfaces.

• T1/E1 CES unstructured services

• T1/E1 CES structured services

These CES services are described briefly in separate sections below.

Figure 5 is a simplified representation of how these types of circuit emulation services can coexist in an LS1010 ATM network and be performed by means of CES modules in LS1010 switches.

Figure 5: Circuit Emulation Services Supported by CES Modules

Circuit Emulation Services Interworking Function (CES-IWF)

CES-IWF is a service based on ATM Forum standards that allows communications to occur between CBR and ATM UNI interfaces, that is, between non-ATM telephony devices (such as classic PBXs or TDMs) and ATM devices (such as LS1010 switches). Thus, an LS1010 equipped with a CES module offers a migration path from classic T1/E1 CBR data communications services to emulated CES T1/E1 unstructured (clear channel) services or structured (N x 64) services in an ATM network.

Figure 6 is a simplified representation of CES-IWF functions in an LS1010 network.

Figure 6: CES-IWF Functions in an LS1010 Network

T1/E1 Unstructured (Clear Channel) CES Services

Unstructured CES services in an LS1010 network emulate point-to-point connections over T1/E1 leased lines. This service maps the entire bandwidth necessary for a T1/E1 leased line connection across the ATM network, allowing users to interconnect PBXs, TDMs, and video conferencing equipment, as shown in Figure 8. Unstructured CES operations do not decode or alter the CBR data in any way.

By means of a CES module, the following unstructured CES services are provided to LS1010 users:

• CES T1 PAM--Supports DSX-1 physical interfaces to provide T1 unstructured (clear channel) CBR data transmission services to LS1010 users at a rate of 1.544 Mbps.

Using a CES T1 PAM for unstructured CES services simulates a point-to-point T1 leased line across your ATM network.

• CES E1 PAM (either 120-ohm or 75-ohm version)--Supports G.703 physical interfaces to provide E1 unstructured (clear channel) CBR data transmission services to LS1010 users at a rate of 2.048 Mbps.

Similarly, using a CES T1 PAM for unstructured CES services simulates a point-to-point E1 leased line across your ATM network.

Figure 7 is a generalized representation of how T1/E1 unstructured CES services are accomplished in conjunction with an LS1010 switch equipped with a CES T1/E1 PAM.

Figure 7: T/E1 Unstructured CES Services Across Leased Lines

Figure 8 is a generalized example of unstructured CES applications in an LS1010 network. During unstructured CES services, user CBR data received from an edge device at one side of the network is segmented into ATM cells and propagated through the ATM network. After traversing the network, the ATM cells are reassembled into a CBR bit stream that matches the original user data. This CBR data is then passed out of the network to the edge device at the destination endpoint.

Figure 8: T1/E1 Unstructured CES Applications in LS1010 Network

T1/E1 Structured (N x 64) CES Services

The notation "N x 64" refers to a circuit bandwidth (data transmission speed) provided by the aggregation of N x 64 Kbps channels, where N is an integer greater than 1. The 64 Kbps data rate, or the DS0 channel, is the basic building block of the "T" carrier systems (T1, T2, and T3).

The T1/E1 structured (N x 64) CES services enable a CES module to function much in the manner of a classic digital access and crossconnect system (DACS) switch. By means of a CES T1/E1 module, the following structured services are provided to LS1010 users:

• CES T1 PAM--Supports DSX-1 physical interfaces to provide T1 channelized data transmission services at a rate of 1.544 Mbps.

Using a CES T1 PAM, you can map a single DS0 channel or multiple DS0 channels across an ATM network. Each T1 port has up to 24 time slots for allocation to structured CES circuits. Each time slot can transmit CBR data at a rate of 64 Kbps, or at 56 Kbps, if you choose to use optional channel associated signaling (CAS). The later section entitled "Channel Associated Signaling (for Structured CES Services Only)" describes the CAS mechanism.

• CES E1 PAM (either 120-ohm or 75-ohm version)--Supports G.703 physical interfaces to provide E1 channelized data transmission services at a rate of 2.048 Mbps.

Using either the 120- or 75-ohm version of a CES E1 PAM, you can map a single DS0 channel (64 Kbps) or multiple DS0 channels across an ATM network. Each E1 port has up to 31 available time slots for allocation to structured CES circuits. Each time slot can transmit CBR data at a rate of 64 Kbps.

If you choose to use optional channel associated signaling (CAS) in conjunction with a structured CES circuit, the effective data transfer rate of the circuit is limited to 56 Kbps, since 8 Kbps of the circuit's bandwidth is required for signaling purposes.

The later section entitled "Channel Associated Signaling (for Structured CES Services Only)" describes the CAS mechanism.

Figure 9 illustrates the digital crossconnect and channelized mapping functions supported by an LS1010 switch equipped with a CES module.

Figure 9: Digital Access and Crossconnect (DACS) Functions of CES Modules

Note that single or multiple DS0 time slots can be mapped across the ATM network. Each time slot (or DS0 channel) represents a single "N x 64" circuit that is capable of transmitting CBR data at a rate of 64-Kbps. Note also that multiple N x 64 circuits may be connected to a single port, using separate time slots.

With T1/E1 structured CES services, network designers can simplify networks by eliminating TDM devices, using LS1010 CES modules instead as a means of allocating T1/E1 bandwidth to PBXs and teleconferencing equipment.

As Figure 9 demonstrates, structured services in a CES module allow T1/E1-formatted CBR data to be provisioned into individual DS0 channels (PVCs) or groups of DS0 channels.

Data from these channels can be sent to multiple individual output ports on a CES module where the data can be combined with CBR data from other DS0 channels or groups of DS0 channels to form an outgoing T1/E1 bit stream. Thus, you can combine structured CBR data in a highly flexible way for transport across an ATM network.

Figure 10, for example, illustrates how 24 available "N x 64" DS0 time slots in a CES T1 PAM can be combined in any number of ways to accomplish structured CBR data transport in an ATM network. Note that the DS0 channels can be grouped as contiguous or non-contiguous time slots.

The DS0 time slots chosen for illustrative purpose in Figure 10 have no particular significance. In other words, you can allocate the available DS0 time slots for a CES T1 PAM in any way that suits the bandwidth requirements of a particular CES circuit.

Figure 10: Time Slots for Structured Services in CES T1 PAM

Note that the ingress (source) DS0 channels at one end of the CES circuit can be mapped into different egress (destination) DS0 channels at the other end of the CES circuit. The only requirement that you must observe in mapping DS0 channels is that the number of time slots so mapped at each end of the CES circuit must agree.

For example, Figure 10 shows DS0 time slots #7, #8, and #24 being bundled to form a single 192Kbps circuit; at the other end of the connection, you can bundle any of three (available, as well as different) DS0 time slots (such as #18, #19, and #20 ) to complete the CES circuit. Thus, if you allocate three DS0 time slots at one end of the connection, you must also allocate three DS0 time slots at the other end of the connection.

For CES structured services, each DS0 time slot represents a data bandwidth of 64 Kbps for CBR data transport. However, if you are using optional channel associated signaling (CAS) during CBR data transport, the data bandwidth is limited to 56 Kbps per DS0 time slot.

Figure 11 illustrates how 31 available "N x 64" DS0 time slots can be provisioned for structured CES services in a CES E1 PAM. The rule noted above for DS0 time slot allocation with a CES T1 PAM also applies to the CES E1 PAM. In other words, the specific DS0 time slot numbers assigned at one end of the circuit in a CES E1 PAM need not map identically one for one to the DS0 time slot numbers at the other end of the CES circuit. Only the aggregate number of such DS0 time slots provisioned at each end of the circuit must agree.

Figure 11: Time Slots for Structured CES Services in CES E1 PAM

Channel Associated Signaling (for Structured CES Services Only)

Since the CES T1/E1 PAM emulates constant bit rate services over ATM networks, it must be capable of providing support for handling channel associated signaling (CAS) information introduced into structured CES circuits by PBXs and TDMs (time-division multiplexing devices). An optional CAS feature for the CES T1/E1 PAM meets this requirement.

With respect to the CAS information carried in a CBR data stream, a CES module can be configured to operate as follows:

• Case 1--Without the optional CAS feature enabled (the default state).

In this case, the CES module does not sense the CAS information (carried as so-called "ABCD" bits in the CBR bit stream) and provides no support for CAS functions.

• Case 2--With the optional CAS feature enabled, but without the optional (Cisco-proprietary) "on-hook detection" feature enabled.

In this case, in addition to packaging incoming CBR data into ATM AAL1 cells in the usual manner for transport through the network, the CES module in the ingress LS1010 node (see Figure 12) senses the "ABCD" bit patterns in the incoming data, incorporates these patterns in the ATM cell stream, and propagates the cells to the next node in the network. The ATM cells are transported across the network from link to link until the egress LS1010 node is reached (see Figure 12).

At the egress node, the CES module strips off the ABCD bit patterns carried by the ATM cells, reassembles the CAS "ABCD" bits and the user's CBR data into original form, and passes the frames out of the ATM network on the proper DS0 time slot.

All these processes occur transparently without user notice.

• Case 3--With both the optional CAS and on-hook detection features enabled.

In this case, the CAS and on-hook detection features work together to provide a means for an ingress node in an ATM network to monitor "on-hook" and "off-hook" conditions for a specified 1 x 64 structured CES circuit. As implied by the notation "1 x 64," the on-hook detection (or bandwidth-release) feature is supported only in a structured CES circuit that involves a single DS0 time slot at each end of the connection, as shown in Figure 12.

Note from Figure 12, however, that the DS0 time slot configured for the structured CES circuit at the ingress node (time slot 2) can be different from the DS0 time slot configured at the egress node (time slot 4). These particular time slots were chosen merely for illustrative purposes; only one such time slot can be configured at each end of the circuit when using the on-hook detection feature.

When you invoke this feature, the ingress CES module monitors the ABCD bits in the incoming CBR bit stream to detect "on-hook" and "off-hook" conditions in the circuit. In an "off-hook" condition, all the bandwidth provisioned for the specified CES circuit is used for transporting ATM AAL1 cells across the network from the ingress node to the egress node.

Conversely, in an "on-hook" condition, the network periodically sends dummy ATM cells from the ingress node to the egress node to maintain the connection. However, these dummy cells consume only a fraction of the circuit's reserved bandwidth, leaving the rest of the bandwidth available for use by other network traffic. Hence, this bandwidth-release feature enables the network to make more efficient use of its resources.

Figure 12: Channel Associated Signaling in a Structured CES Circuit

When the CAS feature is enabled for a CES circuit, the bandwidth of the DS0 channel is limited to 56 Kbps for user data, since CAS functions consume eight Kbps of channel bandwidth for transporting the ABCD signaling bits. These signaling bits are passed transparently from the ingress node to the egress node as part of the ATM AAL1 cell stream.

In summary, when the optional CAS and on-hook detection features are enabled, the following conditions apply:

• The permanent virtual connection (PVC) provisioned for the CES circuit always exists.

• The bandwidth for the CES circuit is always reserved.

• During an "on-hook" state, most of the bandwidth reserved for the CES circuit is not in use. (Dummy cells are sent from the ingress node to the egress node to maintain the connection.) Therefore, this bandwidth becomes available for use by other network traffic, such as available bit rate (ABR) traffic.

• During an "off-hook" state, all the bandwidth reserved for the CES circuit is dedicated to that circuit.

A later section entitled "Configuring a Soft PVC for Structured CES Services (with CAS enabled)" outlines the procedures for enabling the CAS feature using CLI commands.

Also, a later section entitled "Configuring Structured CES Services (with CAS and on-hook detection enabled)" outlines the additional steps necessary in setting up a 1 x 64 structured circuit through CLI commands to take advantage of the bandwidth-release feature.

Specifications of CES Modules

Table 1 lists the specifications for the CES modules.

Table  1: CES Module Specifications

Description	Specifications
Dimensions (H x W x D)	PAM: 1.2 x 6.5 x 10 in. (3.0 x 16.5 x 25.4 cm)
Weight	1.25 lb. (0.57 kg.)
Operating temperature	32 to 104°F (0 to 40°C)
Nonoperating temperature	-40 to 167°F (-40 to 75°C)
Humidity	10 to 90%, noncondensing
Altitude	-500 to 10,000 ft. (-52 to 3,048 m)
Interface timing	Loop timing, Stratum 4 accuracy clock for self-timing; synchronous, SRTS, or adaptive clocking for CBR traffic.
Number of ports per module	CES T1 PAM (100-ohm): four ports with RJ-48C connectors; 24 DS0 time slots per port for structured CES services. CES E1 PAM (120-ohm): four ports with RJ-48C connectors; 31 DS0 time slots per port for structured CES services. CES E1 PAM (75-ohm): four ports with BNC connectors; 31 DS0 time slots per port for structured CES services.
Network management LEDs	S1, S2, and CD
Mean Time Between Failures	139,968 hours
Management Information Base (MIB) - Cisco chassis MIB	RFC 1406
Maximum station-to-station cabling distance	CES T1 PAM with RJ-48C connectors (100-ohm): Maximum station-to-station path loss is 5.5 dB. Typically, 5.5 dB equates to about 1000 feet of 24 gauge, 100-ohm cable, which has an attenuation of .55dB/100 feet at 772Khz. CES E1 PAM (120-ohm) with RJ-48C connectors: Maximum station-to-station path loss is 6 dB. Typically, 6 dB equates to about 1000 feet of 22 gauge, 120-ohm cable, which has an attenuation of .6dB/100 feet at 2 MHz. CES E1 PAM (75-ohm) with BNC connectors: Maximum station-to-station path loss is 6 dB. Typically, 6 dB equates to about 1000 feet of 75-ohm BNC cable, which has a 20-gauge solid core and an attenuation of .6dB/100 feet at 5Mhz.

Regulatory Compliance Requirements

Table 2 shows the applicable regulatory compliance requirements for the CES T1/E1 modules.

Table  2: Regulatory Compliance Requirements for CES T1/E1 Modules

Approval Requirement	CES T1 (100-ohm)	CES E1 (120-ohm)	CES E1 (75-ohm BNC)
Safety	UL 1950 (U.S. and Canada)	EN 60950 (Europe); IEC 950 (with all national deviations)	EN60950 (Europe); IEC 950 (with all national deviations)
EMI	FCC Part 15, Class A T1; VCCI Class I with UTP cables; VCCI Class II with shielded cables	EN55022/CISPR22 Class A with unshielded cables; EN55022/CISPR22 Class B with shielded cables	EN55022/CISPR22 Class A; EN55022/CISPR22 Class B with BNC capacitor clips. Use of these capacitor clips is required for compliance with European certification standards for emission control.
EMC		EN50082-1	EN50082-1
PTT	FCC Part 68 IC CS-03	CTR 12 (Pan-Euro, for unstructured service); TBR 13 (Pan-Euro, for structured service)	NTR 4 (U.K.)

Maximum CES Module Configurations

The four carrier modules (CMs) in an LS1010 chassis can accommodate a total of up to eight CES modules (two such modules per CM).

You can install any combination of up to eight different types of LS1010 interface modules in any of the eight available PAM slots in an LS1010 chassis. Aside from the limit of eight interface modules per chassis, no restrictions apply regarding the mix or placement of the interface modules in the LS1010 chassis or their proximity to the ATM Switch Processor (ASP) module.

CES Module Light Emitting Diodes (LEDs)

This section describes the LEDs on the faceplate of the CES modules, shows their possible illumination states, and defines the operational status of the associated ports, given certain illumination patterns of the LEDs.

The LEDs for the CES modules exhibit the illumination states shown in Table 3.

Table  3: Possible Illumination States of LEDs on CES Modules

LED	Illumination States
S1 (status1)	Steady green, red, or yellow; flashing green, red, or yellow; or off.
S2 (status2	Steady green, red, or yellow; flashing green, red, or yellow; or off.
CD (carrier detect)	Either on (green) or off.

Table 4 shows the status conditions indicated by specific settings of the LEDs on the CES modules.

Table  4: Status Conditions Indicated by CES Module LEDs

Port Status Indication	S1 LED State	S2 LED State	CD LED State
Port not configured	Off	Off	Off
Port administratively down	Off	Off	Off
Normal	Green	Green	Green
Red alarm due to framing error	Red	Red	Off
Red alarm due to loss of cells	Red	Red	Green
Yellow alarm	Yellow	Off	Green
Blue alarm	Off	Yellow	Green
Port in loop state	Flashing green	Flashing green	Green

---

Note During alarm integration, the indicated LEDs will flash the "upcoming" or "next" state combination indicated in Table 4 above. For example, when the line conditioning state machine is notified of loss of signal (LOS), it will cause S1 and S2 to flash red, since a continued LOS will put the port in the red alarm state.

---

Making CES Network Connections

The CES modules provide an interface to ATM switching fabrics for transmitting and receiving CBR data bidirectionally at speeds up to 1.544 Mbps for T1 modules and 2.048 Mbps for E1 modules.

You must use the appropriate CES interface cable to interconnect a CES module to an external CES network. Table 5 shows the cable type appropriate to each version of a CES module.

Table  5: Cabling Requirements for CES Modules

Module	Connector Type	Interface Data Rate	Physical Layer
CES T1 PAM	RJ-48C	1.544 Mbps	DSX-1 with ami or b8zs (default) line coding
CES E1 PAM (120-ohm)	RJ-48C	2.048 Mbps	G.703 with ami or hdb3 (default) line coding
CES E1 PAM (75-ohm)	BNC	2.048 Mbps	G.703 with ami or hdb3 (default) line coding

Maximum Cabling Distance Between Stations

The maximum distance between CES modules or network segments depends on the attenuation characteristics of the interface cables used for CES interconnection purposes. The maximum cable lengths for CES connections are shown in Table 6.

For more detail regarding the attenuation characteristics of CES T1/E1 cables, see Table 1.

Table  6: Maximum Cabling Distance Between Stations

CES Module	Cable Type	Maximum Distance Between Stations
CES T1 PAM	Twisted pair cable with RJ-48C connectors	1000 feet (304.8 meters)
CES E1 PAM (120-ohm)	Twisted pair cable with RJ-48C connectors	1000 feet (304.8 meters)
CES E1 PAM (75-ohm)	75-ohm coaxial cable with BNC connectors	1000 feet (304.8 meters)

---

Note For RJ-48C T1/E1 connections in the U.S. and Canada, unshielded twisted pair (UTP) cables can be used to meet FCC Part 15 Class A EMI requirements. For RJ-48C T1/E1 connections in Japan and other countries, shielded twisted pair (STP) cables must be used to meet VCCI Class II EMI requirements.

---

RJ-48C CES Connections

For interface connections on a CES T1 PAM or a CES E1 PAM (120-ohm version), you use a twisted pair cable with RJ-48C connectors. This cable, as well as the pin assignments for the connectors on the module faceplate, are shown in Figure 13.

Figure 13: CES Interface Cable with RJ-48C Connectors

BNC (75-ohm) CES Connections

For interface connections to a CES E1 PAM (75-ohm version), you use a 75-ohm coaxial cable with the bayonet-style, twist-lock BNC connectors shown in Figure 14.

Note the presence of the ferrite beads on this 75-ohm coaxial cable. If compliance with European certification standards for emission control is required (EN55022/CISPR22 Class B for radiated emission levels), these beads must be installed on the cable.

This cable is not shipped with the CES E1 (BNC) PAM. You can order this item separately using Cisco part number 72-0875-01.

Figure 14: CES Interface Cable with BNC Connectors

Connecting CES Modules to External Devices and Networks

Figure 15 is a simplified network diagram that shows how CES T1/E1 PAMs in an LS1010 chassis can be connected to external devices or networks.

Figure 15: Example of CES T1/E1 PAM Connections and Interfaces

CES E1 PAM (BNC) - Special Considerations

As a user of the BNC version of the CES E1 PAM, you have the option to take certain steps that will help you to:

• Maintain the grounding integrity of BNC cabling

• Reduce circuit susceptibility to radiated EMI

• Reduce EMI radiated from the board

The following sections describe the actions you can take to promote these benefits.

E1 Jumpers

The CES E1 (BNC) board has been designed in a way that gives you the option to install jumpers for the four E1 ports on the board. The location of these jumpers are shown in Figure 16. When installed, these jumpers tie the outer shell of the BNC cable for the receive (RX) port to ground, as shown in Detail A of Figure 16.

Under certain circumstances, it may be desirable to take advantage of this option. For example, suppose that user CBR equipment at the transmit (TX) end of a CES circuit is tied to ground, while the receive (RX) end of the circuit (such as an E1 BNC PAM) is not.

Such an arrangement not only makes the CBR data arriving at the E1 BNC PAM more vulnerable to noise on the line, but also increases the likelihood of EMI being radiated from the board.

By installing these jumpers on the board, you not only maintain the grounding integrity of the BNC cabling system, but you also minimize the likelihood of problems related to line noise and radiated EMI.

E1 Receive (RX) Port EMI Capacitor Clips

A device called an EMI capacitor clip is available for use with a CES E1 (BNC) PAM. This clip is designed to reduce the emissions radiated from the four receive (RX) ports on this module.

The EMI clip embodies two spring-loaded clamps that enable the device to be secured over the mated BNC connectors on each RX port of a CES E1 (BNC) PAM. Detail B of Figure 16 shows how these clips are installed on the module.

Compliance with European certification standards for emission control (EN55022/CISPR22 Class B radiated emission levels) is contingent upon the use of these EMI capacitor clips on the module.

These capacitor clips do not ship with a CES E1 (BNC) PAM. You can order them separately using Cisco part number 800-00327-01.

Figure 16: E1 Jumpers and Capacitor Clips for CES E1 (BNC) Module

For Further Reference

The following publications contain information about determining signal attenuation and the required power budget:

• T1E1.2/92-020R2 ANSI, the Draft American National Standard for Telecommunications entitled "Broadband ISDN Customer Installation Interfaces: Physical Layer Specification."

• Power Margin Analysis, AT&T Technical Note, TN89-004LWP, May 1989.

• ANSI/EIA/TIA-568.

• T1E1.2/94-003 Annex D, Draft American National Standard for Telecommunications - Network to Customer Installation - DS1 Metallic Interface.

Safety Recommendations

The guidelines in this section are intended to ensure your safety and protect your equipment. Since these guidelines may not be comprehensive, you are cautioned to be alert and use good judgment under all circumstances when working with the LS1010 chassis or its modules.

• Do not try to lift the LS1010 chassis alone; two people are required to lift the chassis.

• Always unplug all power cords before installing or removing a chassis.

• Always turn off all power supplies and unplug all power cords before removing the chassis front panel.

• Keep the chassis area unobstructed and dust free during and after installation.

• Keep all tools and chassis components away from walkways.

• Do not wear loose-fitting clothes (such as ties, scarves, unbuttoned sleeves), jewelry (including rings and chains), or any other items that could get caught in the chassis.

Warning Metal objects (power supplies, components, and modules) inside the LS1010 chassis heat up when connected to power and ground and can cause serious burns.

Safety with Electricity

The port adapter modules and redundant power supplies are designed to be removed and replaced while the system is operating without presenting an electrical hazard or damaging the system. However, before removing a redundant power supply, make sure the primary (first) supply is powered on.

You must shut down the system before removing or replacing any of the replaceable components inside the front panel, such as the backplane. Never install equipment that appears to be damaged.

Observe the following guidelines when working with any electrical equipment:

• As a precaution, before beginning any procedures requiring access to the chassis interior, locate the emergency power-off switch for the room in which you are working.

• Disconnect all power and external cables before installing or removing a chassis.

• Do not work alone when potentially hazardous conditions exist in the workplace.

• Never assume that power has been disconnected from a circuit; always check to make sure.

• Never perform any action that creates a potential hazard to others or renders the equipment unsafe.

• Carefully examine your work area for possible hazards such as damp or wet floors, ungrounded power extension cables, and missing safety grounds.

In addition, observe the following guidelines when working with equipment that is disconnected from a power source, but which is still connected to telephone wiring or other network cabling.

Warning Do not work on the system or connect or disconnect chassis or network cables during electrical storms.

• Never install telephone jacks in wet or damp locations unless the jack is specifically designed for such use.

• Never touch uninsulated telephone wires or terminals unless the telephone line has been disconnected at the network interface.

• Use caution when installing or modifying telephone lines.

Preventing Electrostatic Discharge Damage

Electrostatic discharge (ESD) damage can result from improper handling of electronic cards or components. Such damage can result in complete or intermittent failure of the component.

Each PAM consists of a printed circuit card that is secured in a metal carrier. Electromagnetic interference (EMI) shielding, connectors, and a handle are integral elements of the metal carrier. Although the carrier helps to protect the cards from ESD, use a preventive antistatic strap whenever you handle a PAM.

Manipulate the carriers only by means of the handles or the carrier edges; never touch the cards or connector pins.

Caution  Always tighten the captive installation screw on the faceplate when installing a PAM. This screw prevents accidental removal of the CM/PAM, provides proper grounding for the system, and ensures that the bus connectors are properly seated in the backplane.

Observe the following guidelines to prevent ESD damage to LS1010 components:

• Always use an ESD-preventive wrist or ankle strap when installing or removing chassis components; ensure that the strap makes ample contact with your skin.

• When removing any chassis module, connect the equipment end of the strap to the installation screw on a filler panel, the captive installation screw on the faceplate of an installed PAM, or a similar screw on a power supply (see Figure 17).

• Handle carriers by the faceplates and carrier edges only; avoid touching the card proper or any of its connector pins.

• When removing a module, place it component-side up on an antistatic surface or in a static shielding bag. If the module is to be returned to the factory, immediately place it in a static shielding bag.

• Avoid contact between chassis modules and your clothing. The wrist strap protects the card only from ESD voltages from your body; ESD voltages from clothing can still cause damage to chassis components.

Caution  For safety, periodically check the resistance value of the antistatic strap. The resistance value should be between 1 and 10 megohms (Mohms).

Figure 17: Use of Electrostatic Discharge Wrist Strap

Installing Interface Components

The following sections describe the procedures for installing CMS and PAMs in the LS1010 chassis.

Whenever you handle PAMs, you should use a wrist strap or other grounding device to prevent electrostatic discharge (ESD) damage to the electric components on the module. See the section "Preventing Electrostatic Discharge Damage" in the chapter entitled "Preparing for Installation" in the LightStream 1010 ATM Switch User Guide.

Installation Tools Required

You need a 3/16-inch flat-blade screwdriver to remove any blank filler panels present in the front of the LS1010 chassis and to tighten the captive installation screws that secure CMs and PAMs to the chassis.

It is recommended that you install blank filler panels to cover unoccupied CM slots in the chassis. This practice ensures a consistent flow of cooling air through the LS1010 chassis.

What is Hot-Swapping?

All LS1010 CMs and PAMs support a feature called hot-swapping. This feature allows you to add, remove, replace, or rearrange interface modules in the LS1010 chassis while the system is running. This hot-swapping capability provides a seamless method for maintaining the integrity of network routing information and preserving network communication sessions.

You do not need to notify the software or shut the system down when performing hotswapping operations.

Installing a Carrier Module (CM)

You can install a CM in any of the four slots numbered 0 , 1, 3, or 4 in the front of the LS1010 chassis (see Figure 18). Slot 2 is reserved for the ATM switch processor (ASP).

Each CM contains a bus-type connector affixed to the back edge of the CM that mates with the system backplane.

Caution The ASP is a required system component. Removing an ASP while the system is running will shut the system down and may damage the ASP.

To install a CM in the LS1010 chassis, perform the following procedure:

Step 1 Select any unused slot in the LS1010 chassis into which you wish to install the CM (see Figure 18).

Figure 18: Chassis Slot Numbers

Step 2 If the selected CM slot is covered with a blank filler panel (extending the width of the LS1010 chassis), unscrew the captive installation screw at each end of the panel (see Figure 18) using a 3/16th-inch flat-blade screwdriver. Remove the CM filler panel.

Step 3 Grasp the CM by its sides or its faceplate and align its rear edges with the grooved CM installation slot on each side of the LS1010 chassis.

Step 4 Gently slide the CM into the installation slot until its backplane connector (see Figure 19) makes contact with the system backplane.

Step 5 Firmly seat the CM into the system backplane by locking into place the CM ejector levers (see Figure 19) on each side of the CM. This action ensures that the backplane connector pins mate properly with the system backplane.

Step 6 Tighten down the captive installation screw (see Figure 19) on each side of the CM using a 3/16th-inch flat-blade screwdriver. This action secures the CM firmly within the LS1010 chassis.

Figure 19: Carrier Module Components

Installing and Removing a PAM

To install a PAM, perform the steps below.

Caution Handle a PAM only by its faceplate or its edges to prevent ESD damage to its electronic components.

Step 1 Choose a PAM slot in a CM and ensure that enough clearance exists to accommodate any interface cabling or communications equipment that you intend to connect directly to PAM ports.

As you face the front of the LS1010 chassis, PAM slot 0 is on the left, and PAM slot 1 is on the right (see Figure 20).

Figure 20: PAM Slot Numbers

Step 2 If a blank PAM filler panel is covering the selected PAM slot (see Figure 21), loosen the captive installation screw in the center of the filler panel using a 1/4-inch flat-blade screwdriver. Remove the PAM filler panel from the CM.

Figure 21: PAM Blank Filler Panel

Step 3 Grasp the PAM by its faceplate or its sides and place its rear edges in the grooved PAM installation slot in the CM (see Figure 22). Avoid touching the electronic components on the PAM.

Figure 22: Installing PAM in CM

Step 4 Gently slide the PAM into the CM installation slot, as shown in Figure 22, until its connectors make contact with the two Futurebus connectors on the CM.

The Futurebus connectors on the CM incorporate tiered pins of three different lengths. Upon PAM insertion into the CM, the Futurebus pins mate with the PAM in a certain order, sending specific signals to the system for evaluation.

The longest pins in the Futurebus connector make contact with the PAM first, and the shortest pins make contact last. Thus, the LS1010 expects to receive signals from the tiered pins in the Futurebus connector in a certain sequence.

The system assesses these signals and the order in which they are received to determine what event is occurring and how it should respond, such as initializing a new PAM that has been installed in the CM or shutting down a PAM that has been removed from the CM.

Step 5 After inserting the PAM, tighten the captive installation screw on the PAM faceplate using a 1/4-inch flat-blade screwdriver. This action fully seats the PAM into the Futurebus connectors on the CM and draws the PAM faceplate flush against the CM.

---

Note Always tighten the captive installation screw when installing a PAM. An interface module that is partially seated in the CM causes the system to halt and subsequently crash.

---

Step 6 Attach the appropriate interface cables and communications equipment to the PAM interface ports.

Step 7 Check the status of the interface as follows:

• If you are installing a replacement PAM, use the show configuration or show atm interface [card/subcard/port] command to verify that the system acknowledges the new interface module and brings it up successfully.

• See the publication LightStream 1010 ATM Switch Software Configuration Guide and LightStream 1010 ATM Switch Command Reference for detailed software instructions and related information.

To remove a PAM from the LS1010 chassis, such as during hotswapping operations, you need only unscrew the captive installation screw on the PAM faceplate and remove the PAM from the slot.

If you intend to replace an old PAM with a new one, proceed with Step 3 in the procedure above to complete the installation of the new PAM.

Effects of Installing or Removing a PAM

When you install or remove a PAM, the backplane pins send signals to the system to notify it of the event. The system then does the following:

1. Rapidly scans the backplane for configuration changes.
   
   
2. Initializes all newly-inserted PAMs, noting any removed modules and placing them in an administratively shut down state.
   
   
3. Restores all previously-configured interfaces on the PAM to their states prior to removal. If a PAM similar to one that was removed is reinserted, its ports are configured and brought online with the same port count as the removed PAM.
   

Unconfigured PAMs installed for the first time start up in a "shut down" state. The system identifies such modules as present, but unconfigured. Therefore, each new PAM must be manually configured using IOS command line interface (CLI) commands. Instructions for initial configuration of LS1010 interfaces can be found in the publication LightStream 1010 ATM Switch Software Configuration Guide.

When you insert a new PAM, the system runs a diagnostic test on the new module and compares certain parameters to the existing configuration information. If this initial diagnostic test fails, the system remains offline for another 15 seconds while it performs a second set of tests to determine whether the PAM is faulty or whether normal system operation is possible.

If the second diagnostic test passes (indicating that the system is operating normally), but the new PAM is faulty, the system resumes normal operation, but leaves the new module disabled.

If the second diagnostic test fails, the system crashes, indicating that the new PAM has created a problem in the system bus and should be removed.

Caution To avoid erroneous diagnostic failure messages, allow at least 15 seconds for the system to re-initialize and record the configuration of all installed modules before removing or inserting any other module.

Sample Screen Display for Hot-Swapping Procedure

When you remove and replace CMs and PAMs, the system provides status messages on the console screen. The messages are for information only. In the following sample display, you can follow the events logged by the system when a PAM was removed from slot 3/0. When the PAM is reinserted, the system marks the module as ready again.

Switch#
%OIR-6-REMCARD: Card removed from slot 3/0, interfaces disabled
%LINK-5-CHANGED: Interface 155UTP 3/0, changed state to administratively down
%LINK-5-CHANGED: Interface 155UTP 3/0, changed state to administratively down
Switch#
%OIR-6-INSCARD: Card inserted in slot 3/0, interfaces administratively shut down
%LINK-5-CHANGED: Interface 155UTP 3/0, changed state to up
%LINK-5-CHANGED: Interface 155UTP 3/0, changed state to up

Configuring CES Module Interfaces

After you install a CES module, use the following information to configure the module and the individual interfaces on the Module. In the LightStream 1010 ATM Switch User Guide, the section entitled "LightStream 1010 ATM Switch Hardware" contains an overview of the port and module numbering scheme used to configure PAMs. The section entitled "Configuring the LightStream 1010 ATM Switch" describes how to configure the ports on a CES module. The section entitled "Confirming the Installation" describes the procedures you use to confirm that the CES T1/E1 ports are configured correctly.

Port Addresses

Each interface (or port) in an LS1010 switch is designated by several different types of addresses. The physical address is the actual physical location (card/subcard/port) of the interface connector within the chassis. The system software uses physical addresses to control activity within the switch and to display status information. These physical card/subcard/port addresses are not used by other devices in the network; they are specific to the LS1010 switch and its internal components and software.

The following sections describe how the LightStream 1010 switch assigns and controls both the physical (card/subcard/port) and Media Access Control (MAC)-layer addresses for interfaces within the chassis.

Port IDs

Port IDs are used to identify the actual physical location of each interface module in the front of an LS1010 switch and to specify its associated ports (see Figure 23).

A Port ID consists of a three-part number in the format card/subcard/port. A representative port ID, for example, might be CBR 0/1/3.

The first number is used to identify the chassis slot in which the module is installed. Chassis slots are numbered vertically from 0 to 4, beginning at the top left of the chassis. The second number identifies the subcard or PAM slot number. The PAM slots are numbered horizontally from 0 to 1, beginning with the leftmost slot as you face the front of the LS1010 switch. The third number identifies the specific port on the module. Port numbers always begin with 0 and are numbered from the leftmost port to the rightmost port on the module as you face the front of the chassis. The actual number of ports on an interface module is always hardware-dependent.

Using the example port ID above, CBR 0/1/3, you would conclude that the CBR module is located in chassis slot 0, PAM slot 1, and that port 3 on the module is specifically identified, that is, the rightmost port of four (0, 1, 2, and 3) on the module.

Figure 23: LS1010 ATM Switch Port IDs

You can identify module ports by visually examining the card/subcard/port location on the front of the LS1010 switch. You can also use software commands to display information about a specific interface, or all interfaces, in the switch.

To display information about every interface in the LS1010 chassis, you can issue the CLI show interface command. To display details about a specific interface, you can issue use the CLI show interface command with appropriate keywords and parameters. Such a command, for example, might take the form show ces circuit interface cbr0/1/0 0, as shown in Step 3 in the section entitled "Verifying a Configured Hard PVC (with Adaptive Clocking)."

System Configuration Defaults

When the LS1010 switch is powered on initially without any previous configuration data, the ATM interfaces are configured automatically on the physical ports. The Interim Local Management Interface (ILMI) and the physical card type are used to automatically derive the interface defaults.

If ILMI has been disabled or if the connecting end node does not support ILMI, the following system defaults are assigned to all interfaces:

• ATM interface type = UNI

• UNI version = 3.0

• Maximum VPI bits = 8

• Maximum VCI bits = 14

• ATM interface side = network

• ATM UNI type = private

CES Port Default Parameters

The port default configuration parameters and values listed in Table 7 apply for all LS1010 CES modules, unless you change them manually by issuing specific CLI commands during CES module configuration:

Table  7: CES Port Default Configuration Parameters/Values

Port Type	Parameter Description	Default Value
T1	Line type	dsx1ESF
T1	Line coding	dsx1B8Zs
T1	Line state	dsx1NoAlarm
E1	Line type	dsx1E1
E1	Line coding	dsx1HDB3
E1	International bits	0x3
E1	National bits	0x1f
E1	Multiframe spare bits	0xb
T1/E1	Loop configuration	dsx1NoLoop
T1/E1	Signal mode	dsx1NoSignalling
T1/E1	Transmit clock source	throughTiming
T1/E1	Data format	dsx1ClearChannel
T1/E1	Clocking mode	dsx1Synchronous
T1/E1	Line length	line_0_110 (in feet)
T1/E1	Cell delay variation (CDV)	2000 /* In microseconds */
T1/E1	Channel associated signaling (CAS)	FALSE
T1/E1	Partial fill	47

You can accept these defaults or overwrite them using appropriate CLI commands. Where applicable, such commands are detailed in the later sections in this document entitled "Before You Begin" and "Configuring CES PAMs for Structured CES Services." For a complete description of the CLI commands used to manually change any of these CES port configuration default values, refer to the LightStream 1010 ATM Switch Software Configuration Guide.

Network Clock Synchronization Services for CES Operations

Circuit emulation services-interworking functions (CES-IWF) and constant bit rate (CBR) traffic relate to a quality of service (QOS) classification defined by the ATM Forum for Class A (AAL1) traffic in ATM networks. In general, Class A traffic pertains to voice and video transmissions.

In an LS1010 environment, CBR refers to a particular class of traffic that is generated by edge (source) devices and propagated into ATM networks for transmission to other edge (destination) devices in the network. Each CBR edge device communicating in this manner must be driven by a clocking signal of identical frequency, since this signal controls the rate of CBR data insertion into the network, as well as the rate of extraction of CBR data from the network

If the clock frequency is not the same at both the ingress and egress nodes of the circuit, the data queues and buffers in the network will either overflow or underflow, resulting in periodic line errors.

The CES modules have been designed specifically to handle CBR traffic in an ATM networking environment. To provide requisite timing functions in support of CES operations, you can specify any one of three clocking modes:

• Synchronous clocking mode (required for T1/E1 structured CES operations)

• Synchronous Residual Time Stamp (SRTS) clocking mode

• Adaptive clocking mode

However, to support synchronous clocking or SRTS clocking in your LS1010 operating environment, your network must incorporate the following facilities:

• A primary reference source (PRS)--Throughout this document, the term PRS is used to refer to a precision reference timing signal that must be made available, wherever required, to synchronize the flow of CBR data from its source to its destination.

• Network clock synchronization services--This refers to a network clock synchronization and distribution service that provides a PRS to those user and network devices that require a precision reference timing signal for synchronizing the flow of CBR traffic.

This clock distribution service enables you to distribute a PRS to, or by means of, the following network entities:

• A CES module in an LS1010 chassis.

• An OC3 or OC12 PAM in an LS1010 chassis.

• A quad DS-3 module in an LS1010 chassis.

• Any T1/E1, OC3, or OC12 trunk line, or other means of interconnecting an ATM network. Note that a trunk port can propagate a clocking signal in either direction.

Planning for Network Clocking

There are many considerations that must be taken into account in planning, designing, and implementing an ATM network. Such considerations may include, but are not limited to, the specific hardware to be used in the network, the purposes to be served by the network, the protocols to be implemented within the network, and the physical topology of the network.

How a clocking signal is to be distributed within the network is among these important considerations. In all cases, the purpose of distributing a clocking signal within the network is to ensure that each constant bit rate device has access to a common reference clocking signal for synchronizing CBR data transport.

For this reason, the planning for distributing a timing signal must be done on a per-chassis basis. Furthermore, this planning must also include a means for distributing up to three alternative clocking signals in the event of failure of the primary clock signal. Thus, you can think of network clocking in general as a kind of "protocol" to be implemented in the network.

In summary, for the reasons outlined above, network administrators must make provision beforehand for the following:

• A primary reference source (PRS)--that is, a common clocking signal to be used by CBR devices.

• Up to three alternative clocking sources in the event of failure of the primary reference source.

• A means for distributing a clocking signal wherever required in the networking environment.

Once these network clocking facilities are established and operational, they tend to remain static until the primary clock is lost for any reason. In this case, network clocking is dynamic in the sense that an alternate clocking signal must be placed into effect immediately in order for the network to remain operational.

A Word to the Wise

As noted in the preceding section, network clock signal distribution in an ATM network is not a trivial consideration. The task of determining a network clocking source and designing a distribution topology for the clocking signal is a task best left to network designers, planners, and engineers.

The information provided herein relative to network timing services is intended only as a general introduction to the subject for readers who may be unfamiliar with the topic, but who could profit from some knowledge of such services as they pertain to CBR data transport.

Accordingly, this document is limited to a description of the means provided to LS1010 users for selecting a clock source and defining its priority relative to other alternative clocking sources that may be available within the network.

For purposes of this document, it is sufficient to say that an LS1010 chassis derives a network clocking signal from a particular port in the chassis that you have configured to receive such a signal from a clock source available within the networking environment.

The port that you have thus designated to receive the clocking signal then distributes it within the LS1010 chassis to all other ports which require such a clocking signal for synchronizing CBR data transport.

Sources of Network Clocking Signals

In many cases, using a clocking signal from a telephone company is the simplest and best solution to your need for a stable and reliable clocking signal, especially in those instances where you are already using a CES circuit to interconnect telephone equipment.

For example, to meet its own need for internal consistency, a telephone company typically distributes a timing signal to govern its own networking operations. Therefore, the telephone company has already addressed timing requirements similar to those that an LS1010 user must address in relation to his own CES operations. Consequently, a PBX can serve as a ready means for providing a timing signal to any user CBR device.

An LS1010 network administrator can define up to four clocking signal sources per chassis, assigning a priority to each one. Under normal operating conditions, the priority 1 signal serves as the primary clocking signal. The remaining signal sources are listed in priority order for backup purposes in the event of failure of the primary (priority 1) clock.

The clock sources configured for a CES module are revertive. For example, assume that a clock of lower priority is currently in effect due to failure of a higher priority clock source. When the higher priority clock is again restored to service for at least one minute, the system automatically reverts to this signal for network clock synchronization purposes.

To make use of network timing services in an LS1010 chassis, the user need only define the port from which a network timing signal is to be taken and list the alternative clock sources for the port in the same order of priority as specified for the network at large.

You can accomplish these clock configuration tasks by issuing the CLI network-clock-select command, as described in a later section entitled "Defining Network Clock Sources and Priorities for an LS1010 Chassis."

A PRS from one of the following sources is often the timing signal of choice, because such signals from major carriers are known to be highly stable, reliable, and accurate:

• AT&T

• Ameritech

• MCI

• Bell South

Clocking Modes for CES Operations

For CES operations, as noted earlier, three clocking modes can be used in conjunction with any CES module. These clocking modes are described briefly below in their recommended order of consideration and use:

• Synchronous clocking mode--This mode requires a PRS and network clock synchronization services. Note that synchronous clocking can be used for both unstructured (clear channel) and structured (N x 64 Kbps) CES services.

First, this clocking mode is the only one that supports full CES functionality. SRTS and adaptive clocking do not support structured CES services. For these reasons, synchronous clocking is the default clocking mode for all CES services.

Second, synchronous clocking exhibits superior stability, reliability, and wander/jitter characteristics.

Third, synchronous clocking is typically used in public telephony systems, making a precision reference signal readily and widely available for synchronizing CBR data transport.

This clocking mode is described in greater detail in a later section entitled "Synchronous Clocking."

• Synchronous Residual Time Stamp (SRTS) clocking mode--SRTS clocking also requires a PRS and network clock synchronization services. However, SRTS clocking can be used only for unstructured (clear channel) CES services.

This mode allows user equipment at the edges of an ATM network to use a clocking signal that is different (and completely independent) from the clocking signal being used in the ATM network proper.

For example, user equipment at the edges of the network can be driven by clock A, while the devices within the ATM network are being driven by clock B. The SRTS clocking mode enables these different timing signals to be reconciled in the course of CBR data transport through the ATM network.

This clocking mode is described in greater detail in a later section entitled "Synchronous Residual Time Stamp (SRTS) Clocking."

• Adaptive clocking mode--This mode requires neither a PRS nor network clock synchronization services to accomplish effective CBR data transport. However, as is the case with SRTS clocking, adaptive clocking can be used only for unstructured (clear channel) CES services.

Although this clocking mode is the simplest and easiest to implement in an ATM network, it exhibits the poorest wander and jitter performance of all the available clocking modes. Therefore, its use is not recommended, except in instances where a PRS and network clock synchronization services are not available.

The term adaptive clocking derives from the fact that the rate at which CBR data is propagated through an ATM network is driven essentially by the rate at which such data is introduced into the network by the user's edge equipment.

For example, adaptive clocking in a CES module infers appropriate timing for data transport by calculating an "average" data rate upon arrival and conveying that data to the output port of the module at an equivalent rate.

For this reason, the actual rate of CBR data flow through the network may "wax and wane" from time to time during adaptive clocking, depending on how rapidly (or how slowly) CBR data is being introduced into the network.

Nevertheless, CBR data transport through the network occurs in a "pseudo synchronous" manner that ensures the integrity of the data.

This clocking mode is described in greater detail in a later section entitled "Adaptive Clocking."

Network Timing Modules in an LS1010 Chassis

Any module in an LS1010 chassis that is capable of receiving and distributing a network timing signal can propagate that signal to any similarly-capable module in the chassis.

By issuing the CLI network-clock-select command with appropriate parameters, you can define a particular port in an LS1010 chassis to serve as the source of a PRS for the entire chassis or for other devices in the networking environment. The use of this CLI command is described in a later section entitled "Defining Network Clock Sources and Priorities for an LS1010 Chassis."

In effect, through the network-clock-select command, you can designate a particular port in an LS1010 chassis to serve as a "master clock" source in distributing a single clocking signal throughout the chassis or to other network devices. Hence, this reference signal can be distributed wherever needed in the network to globally synchronize the flow of CBR data.

The following LS1010 modules are capable of receiving and distributing a primary reference signal (PRS):

• CES modules

• OC3 modules

• OC12 modules

• Quad DS-3

• E1/T1 trunk modules

Description of Clocking Modes

The following sections describe the clocking modes in greater detail, presenting them in the preferred order of use in your LS1010 environment.

Synchronous Clocking

When equipped with a CES module and appropriate software, any LS1010 switch can serve as a means for:

• Receiving and distributing a PRS to other devices in the network.

• Synchronizing the flow of user CBR traffic through the network.

Figure 24 shows that an LS1010 switch can make use of a PRS that originates from any one of several sources in the networking environment.

For illustrative purposes, Figure 24 shows four possible sources of a PRS. However, you should not interpret Figure 24 to mean that only four such clocking signals can be made available for use in the ATM network. In fact, numerous clocking signals may be present in the LS1010 operating environment.

The important concepts that you should take from Figure 24 include the following:

• Up to four clocking signals can be defined per LS1010 chassis in the network.

• Each LS1010 chassis must be assigned the same clocking signal sources.

• These clocking signal sources must be specified in the same order of priority for each LS1010 chassis in the network.

Figure 24: Synchronous Clocking Sources in ATM Network

Note that each PRS depicted in Figure 24 is externally generated--that is, the timing signal originates from a source outside the ATM network proper. Also shown is an OC3 or OC12 trunk line that can propagate a PRS between adjacent ATM networks.

In the event that the priority 1 PRS fails for any reason, the network clock synchronization service automatically recovers network timing by using a priority 2 PRS available from another source.

Assume, for example, that the T1/E1 trunk at the top of Figure 24 is currently supplying a priority 1 PRS to the network. Assume further that this PRS fails for some reason. In this event, the OC3/OC12 trunk line (linking the adjacent ATM networks) can provide a secondary (priority 2) PRS for network synchronization purposes.

Similarly, either of the other PBXs connected to the network could each, in turn, provide a PRS to the ATM network in the event of failure of a higher priority PRS.

Note further that, upon restoration to service of the priority 1 PRS, the network clock synchronization service automatically reverts to this PRS for timing purposes, regardless of which lower priority PRS may be active at the time.

Figure 25 shows how a PRS for synchronous clocking can be provided to an edge node of an ATM network and propagated through the network to synchronize the flow of CBR data between the communicating ATM end nodes.

In this particular network scenario, a PRS is available to the network by means of the PBX at the edge of the network. Therefore, this PRS is present at the port of a CES module in edge node A (the ingress node). From there, the PRS is propagated into the first ATM network through an ATM port and conveyed across an OC3 trunk to an adjacent ATM network. This same clocking signal is then used to synchronize the handling of CBR data in edge node B (the egress node).

Figure 25: Synchronous Clocking in LS1010 ATM Network

Synchronous Residual Time Stamp (SRTS) Clocking

Synchronous Residual Time Stamp (SRTS) clocking can be used if the user's edge equipment is being driven by a different clocking signal than that being used in the ATM network proper. Figure 26 shows such an operating scenario in which a timing signal is being provided to edge nodes independently from the ATM network.

Figure 26: SRTS Clocking in LS1010 ATM Network

Using Figure 26 as a frame of reference, assume that the user of edge node 1 wants to send CBR data to a user at edge node 3. In this scenario, SRTS clocking works as follows:

1. Clock A is driving the devices within the ATM network.
   
   
2. At edge node 1, the user introduces CBR traffic into the ATM network according to clock B.
   
   
3. As edge node 1 segments the CBR bit stream into ATM cells, it measures the difference between user clock B by which it is being driven and network clock A.
   
   
4. Edge node 1 generates the ATM cell stream, it incorporates this delta value into every eighth cell.
   
   
5. The cells are then propagated through the network in the usual manner.
   
   
6. As the cells are received at destination edge node 3, this node not only reassembles the ATM cells into the original CBR bit stream, but also reconciles, or reconstructs, the user clock B timing signal from the delta value carried within every eighth ATM cell.
   

Thus, during SRTS clocking, CBR traffic is synchronized between the ingress (segmentation) side of the CES circuit and the egress (reassembly) side of the circuit according to user clock signal B, while the ATM network continues to function according to clock A.

Adaptive Clocking

Adaptive clocking requires neither the network clock synchronization service nor a global PRS for effective handling of CBR traffic. Rather than using a clocking signal to convey CBR traffic through an ATM network, adaptive clocking infers appropriate timing for data transport by calculating an average data rate for the CBR traffic.

For example, if CBR data is arriving at a CES module at a rate of so many bits per second, then that rate is used, in effect, to govern the flow of CBR data through the network. What happens behind the scenes, however, is that the CES module automatically calculates the average data rate by means of microcode (firmware) built into the board. This calculation occurs dynamically "on the fly" as user data traverses the network.

Thus, when the CES module senses that its segmentation and reassembly (SAR) buffer is filling up, it increases the rate of the transmit (TX) clock for its output port, thereby "draining" the buffer at a rate that is consistent with rate of the data's arrival.

Similarly, the CES module slows down the transmit clock of its output port if it senses that the buffer is being "drained" faster than CBR data is being received. In this manner, adaptive clocking attempts to minimize wide excursions in SAR buffer loading while, at the same time, providing an effective means of propagating CBR traffic through the network.

Relative to the other clocking modes, implementing adaptive clocking is simple and straightforward, since it does not require network clock synchronization services, a PRS, or the advance planning typically associated with developing a logical network timing map. However, adaptive clocking does not support structured CES services, and it exhibits relatively high wander characteristics.

Summary of Clocking Modes

Table 8 summarizes the characteristics of the three clocking modes available for handling CBR traffic in an LS1010 networking environment. Although the wander and jitter characteristics of these clocking modes differ, all clocking modes function in a way that preserves the integrity of the user's CBR data, ensuring error-free data transport from source to destination.

Table  8: Characteristics of CES Clocking Modes

Clocking Mode	Advantages	Limitations
Synchronous	Supports both unstructured (clear channel) and structured CBR traffic. Exhibits superior wander and jitter characteristics.	Requires network clock synchronization services. Ties the CES interface to the network clock synchronization services clocking signal (PRS).
SRTS (Synchronous Residual Time Stamp)	Conveys externally-generated user clocking signal through ATM network, providing independent clocking signal for each CES circuit.	Requires network clock synchronization services. Supports only unstructured (clear channel) CBR traffic. Exhibits moderate wander characteristics.
Adaptive	Does not require network clock synchronization services.	Supports only unstructured (clear channel) CBR traffic. Exhibits poorest wander characteristics.

Other Factors Relevant to CES Operations

The following factors enter into proper functioning of CES circuits:

• The intended source and destination nodes for CES circuits.

• The clocking mode that best suits your particular network topology and timing requirements in handling CBR data.

Although synchronous clocking is the recommended (default) clocking mode for CES operations, this fact does not preclude other clocking modes from consideration.

• The cell delay variation (CDV) characteristics of the network, measured in microseconds (usecs).

Each end-to-end CES circuit exhibits delay characteristics, based on the following factors:

• The delay characteristics of the individual devices participating in the CES circuit.

Each network device contributes some increment of delay, reflecting that device's unique electrical characteristics.

• The number of intermediate hops through which the CBR data must pass in traversing the network from source to destination.

The network designer/administrator calculates a CDV value for each hop in the data path in order to establish a maximum allowable CDV value for the network at large.

• The type and speed of the trunk lines interconnecting the ATM networks.

• The volume of traffic being handled by the trunk lines at any given time, that is, the degree to which the network may be experiencing congestion conditions.

A maximum allowable CDV value for the network is calculated by network designers and administrators in order to establish the cell delay tolerance limits for the network. Thus, to some degree, the network's maximum allowable CDV value is a measure of the network's expected performance.

By establishing this CDV threshold for the network, appropriate buffer sizing can be derived for the network devices involved in any given CES circuit, thereby ensuring that the network will operate as expected.

In the case of a CES module, for example, the maximum allowable CDV value for the network is used to determine an appropriate size (depth) for the segmentation and reassembly (SAR) buffer built into the board. This sizing of the SAR buffer is done to prevent buffer overflow or underflow conditions. An overflow condition can cause a loss of frames, while an underflow condition can cause frames to be repeated.

The actual CDV value for a circuit varies according to the particular data path used for the circuit. Consequently, the depth of the SAR buffer may increase or decrease in proportion to the CDV value for the CES circuit being set up.

Note that you can issue the CLI show ces circuit interface command in an unstructured (clear channel) circuit to measure the current CDV value. See Step 3 in the later section entitled "Verifying a Configured Hard PVC (with Adaptive Clocking)."

For an unstructured hard PVC, the CDV value for the circuit (including all hops) should not exceed a maximum allowable CDV value. The procedure for setting up a hard PVC is described in a later section entitled "Configuring CES PAMs for Unstructured CES Services."

For an unstructured soft PVC, the network automatically determines the best data path through the network and handles the routing of CBR traffic. The network accomplishes this dynamically by means of the ATM connection admission control (CAC) mechanism, which determines the best path through the network by executing a routing algorithm that consults local routing tables in network devices.

If the requested data path is equal to or less than the maximum allowable CDV value established by the network administrator, the connection request is granted. If the requested CES circuit exceeds the maximum allowable CDV value, the connection request is denied. These connection admission control processes occur "on the fly" as network connection requests are initiated.

For example, when a user requests a connection from source node A at one edge of the network to destination node B at the opposite edge of the network, the CAC mechanism takes into account the CDV value for each hop in the requested connection to determine a suitable path through the network that does not exceed the network's maximum allowable CDV value.

The procedure for setting up a soft PVC is described in a later section entitled "Configuring a Soft PVC (with Synchronous Clocking)."

Before You Begin

This section presents information common to configuring CES modules for both unstructured and structured CES services.

If you are new to the task of configuring port adapter modules in an LS1010 chassis, you are advised to read the information in this section before attempting to configure a CES module.

However, if you feel prepared by virtue of previous knowledge/experience to deal with configuration tasks, you may proceed directly to the section entitled "Configuring CES PAMs for Unstructured CES Services."

Methods Available for Configuring CES Modules

Basically, two methods are available for configuring a CES module for use in an LS1010 operating environment:

• From a local console or workstation--Using a local console connected to the console port of an LS1010 switch or a workstation connected to the Ethernet port of an LS1010 switch (see Figure 27), you can issue CLI commands directly to the LS1010 chassis to configure an installed CES module.

• From a remote console or workstation--Using a remote console or workstation to initiate a Telnet connection to a target LS1010 switch (see Figure 27), you can issue CLI commands to that chassis to configure an installed CES module.

Figure 27: Methods of Configuring a CES Module in LS1010 Environment

Conventions Adopted for CES Module Configuration Procedures

The configuration procedures throughout this document are based on the following assumptions/conventions:

• The default host name (or node name) for the target LS1010 chassis is "condor4."

• Unless otherwise indicated, the target LS1010 chassis is assumed to be in the privileged EXEC mode. In this mode, the chassis exhibits the "condor4#" prompt, indicating that it is ready to receive privileged EXEC commands.

• CLI command input is intended to demonstrate the use and syntax of commands for the specific configuration task at hand.

These sample procedures demonstrate typical or common configuration tasks and may not reflect your particular CES module configuration requirements.

• CLI command input is highlighted in bold typeface.

System Prompts

The prompts that you will encounter in the configuration procedures in this document include the following:

• User EXEC mode: condor4>

This user level prompt appears on login to the target LS1010 chassis.

• Privileged EXEC mode: condor4#

This prompt results from issuing the enable command at the user EXEC mode prompt.

• Global configuration mode: condor4(config)#

This prompt results from issuing the configure command at the privileged EXEC mode prompt.

• Interface configuration mode: condor4(config-if)#

This prompt results from issuing the interface command at the global configuration mode prompt.

Establishing a CLI Session to Target LS1010

To establish a CLI session with the target LS1010 switch, take any one of the following actions, as appropriate:

• If you are configuring a CES module from a local console attached directly to the target chassis by means of its console port (see Figure 27), enter the following command and password at the user EXEC mode prompt:
  condor4>enable
  password: XXXXXXXX (privileged EXEC mode password)
  condor4#
  
  

This command and password set the target chassis to the privileged EXEC mode. The privileged EXEC mode is password-protected to prevent unauthorized access to the chassis.

• If you are configuring a CES module by means of a Telnet connection from a remote console (see Figure 27), enter the following commands at the remote console:
  switch> ping condor4
  condor4 is alive
  switch> telnet condor4
  Trying 172.27.32.146 ...
  Connected to condor4.
  Escape character is '^]'.
  
  User Access Verification
  
  Password: xxxxxxxx (your privileged EXEC mode password)
  condor4#
  condor4#
  
  

The ping command sends an echo message to the target chassis to determine if it is reachable; the telnet command initiates a Telnet connection to the target chassis; and a correctly entered password grants you access to the chassis in privileged EXEC mode, enabling you to perform configuration tasks.

• If you are configuring a CES module by means of a Telnet connection from a remote workstation (see Figure 27), enter the following commands at the remote workstation:
  sun% ping condor4
  condor4 is alive
  sun% telnet condor4
  Trying 172.27.32.146 ...
  Connected to condor4.
  Escape character is '^]'.
  
  User Access Verification
  
  Password: xxxxxxxx (your privileged EXEC mode password)
  condor4#
  condor4#
  
  

The ping command sends an echo message to the target chassis to determine if it is reachable; the telnet command initiates a Telnet connection to the target chassis; and a correctly entered password grants you access to the chassis in privileged EXEC mode, enabling you to perform configuration tasks.

Having established a privileged CLI session on the target chassis, you can begin the configuration of the CES module by proceeding to the later section entitled "Configuring CES PAMs for Unstructured CES Services."

However, if you are not familiar with the LS1010 network clock synchronization services and the various clocking modes applicable to handling CBR traffic in an LS1010 environment, you should read the earlier section entitled "Network Clock Synchronization Services for CES Operations" before attempting to configure your CES module for service.

Defining Network Clock Sources and Priorities for an LS1010 Chassis

To establish the sources and the priorities of the requisite network clocking signals for an LS1010 chassis and, hence, for CES modules, perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#configure terminal
condor4(config)#

Step 2 To establish a priority 1 network clock source for the LS1010 chassis, enter the following command at the global configuration mode prompt:

condor4(config)#network-clock-select 1 cbr 0/1/0
condor4(config)#

This command establishes the CBR 0/1/0 port as the priority 1 network clock source for the LS1010 chassis.

Step 3 To establish a priority 2 clock source for the chassis, enter the following command:

condor4(config)#network-clock-select 2 atm 0/0/0
condor4(config)#

This command establishes the ATM 0/0/0 port as the priority 2 network clock source for the LS1010 chassis.

Step 4 At the global configuration mode prompt, enter the following command:

condor4(config)#^Z
condor4#

This command exits from the global configuration mode and returns you to the privileged EXEC mode prompt.

You can specify up to four network clock sources for an LS1010 chassis. The highest priority active port in the chassis will supply the PRS to all other chassis interfaces that require network clock synchronization services.

Verifying Clock Signal Sources and Priorities

To verify the network clock sources and priorities that you established in the previous procedure, issue the following command at the privileged EXEC mode prompt:

condor4#show network-clocks
Priority 1 clock source: CBR0/1/0
Priority 2 clock source: ATM0/0/0
Priority 3 clock source: not configured
Priority 4 clock source: not configured

Current clock source:CBR0/1/0, priority:1
condor4#

This command displays the priorities and clock sources currently defined for your LS1010 chassis. Under normal operating conditions, the priority 1 clock source is always assumed to be the active clock.

The LS1010 chassis distributes the clocking signal derived from the network clock source to all the ports on the chassis that require network clock synchronization services. To direct a CBR port to use the network-derived clock, you issue the CLI command ces dsx1 clock source network-derived, as shown in Step 3 of the later section entitled "Configuring a Hard PVC (with Synchronous Clocking)."

Framing Formats and Line Coding Options for CES Modules

The CES modules support the framing formats and line coding options indicated in Table 9.

Table  9: CES Module Framing and Line Coding Options

Module	Framing Options/Description	Line Coding Options
CES T1 PAM	Super frame (SF) Extended super frame (ESF)	ami or b8zs (default)
CES E1 PAM (120-ohm)	E1 CRC multiframe (e1_crc_mf_lt). Configure line type to e1_crc_mf, without CAS enabled. E1 CRC multiframe (e1_crc_mfCAS_lt). Configure line type to e1_crc_mf, with CAS enabled. E1 (e1_lt). Configure line type to e1_lt. E1 multiframe (e1_mfCAS_lt). Configure line type to e1_mf, with CAS enabled.	ami or hdb3 (default)
CES E1 PAM (BNC)	E1 CRC multiframe (e1_crc_mf_lt). Configure line type to e1_crc_mf, without CAS enabled. E1 CRC multiframe (e1_crc_mfCAS_lt). Configure line type to e1_crc_mf, with CAS enabled. E1 (e1_lt). Configure line type to e1_lt. E1 multiframe (e1_mfCAS_lt). Configure line type to e1_mf with CAS enabled.	ami or hdb3 (default)

Guidelines for Creating Soft PVCs for CES Services

As a CES T1/E1 PAM user, you can create either hard PVCs or soft PVCs, depending on your particular CES application requirements. The differences between these two types of CES circuits are noted, where appropriate, in later sections dealing with the actual configuration of unstructured (clear channel) and structured (N x 64 Kbps) CES circuits.

For current purposes, however, the differences between these two types of CES circuits are not important. What you should understand for the moment is that certain steps must be performed in a prescribed order when you configure soft PVCs for either unstructured or structured CES services. These steps follow:

Step 1 Determine which two ports you want to define as participants in the soft PVC.

Step 2 Decide which of these two ports you wish to designate as the destination (or passive) side of the soft PVC.

This is an arbitrary decision--it makes no difference which port you define as the destination end of the circuit. However, you must decide which port is to function in this capacity and proceed accordingly.

Step 3 Configure the destination (passive) side of the soft PVC.

You must configure the destination end of the soft PVC first, because so doing defines an ATM Forum compliant CES-IWF ATM address for that port.

Furthermore, you must retrieve this address (see Step 4), as well as the VPI/VCI values for the circuit (see Step 5), and embody these elements as part of the command string when you configure the source (active) end of the soft PVC (see Step 6).

Step 4 Retrieve the CES-IWF ATM address of the destination end of the soft PVC by issuing the CLI show ces address command. This command typically produces output in the following form:

condor4#show ces address

CES-IWF ATM Address(es):
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 CBR-PVC-A
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.20 CBR-PVC-AC
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 CBR-PVC-B
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1038.10 CBR-PVC-CA

condor4#

Step 5 Retrieve the VPI/VCI values for the circuit by issuing the CLI show ces circuit interface cbrx/x/x # command. This command typically produces output in the following form:

condor4#show ces circuit interface cbr 0/1/1 1
Circuit: Name CBR-PVC-B, Circuit-state ADMIN_UP / OPER_DOWN
Interface CBR0/1/1, Circuit_id 1, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 10-13
Channels used by this circuit: 10-13
Cell-Rate: 681, Bit-Rate 256000
cas OFF, cell_header 0x4100 (vci = 1040)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcInactive, maxQueueDepth 57, startDequeueDepth 40
Partial Fill: 47, Structured Data Transfer 1
Passive SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0, vci 1040
Dst: atm addr default vpi 0, vci 0

condor4#

Step 6 Configure the source (active) end of the soft PVC; at the same time, complete soft PVC setup using the information derived from Step 4 and Step 5 above.

You must configure the source end of the soft PVC last, because doing so not only defines the configuration information for the source port proper, but also requires you to enter at the same time the CES-IWF ATM address and VPI/VCI values for the destination port.

Thus, if you had not already defined the destination port for the soft PVC (as required by Step 3), this CES-IWF ATM address would not have been defined for the destination port, nor would the VPI/VCI values have been available as required by Step 6 for use in completing the soft PVC.

Determining Currently Configured CES Interfaces in LS1010 Chassis

Before configuring new interfaces for a CES module, it may be useful to determine which interfaces have already been defined for CES modules in your LS1010 chassis. You can determine presently configured CES interfaces by issuing the following CLI command at the privileged EXEC mode prompt:

condor4#show ces status 
   Interface      IF      Admin        Port  Channels in
     Name       Status   Status        Type      use    
------------- -------- --------- ----------- -----------
    CBR3/1/0     UP       UP      E1-120ohms    1-10
    CBR3/1/1     UP       UP      E1-120ohms    2-4
    CBR3/1/2     UP       UP      E1-120ohms    1-27
    CBR3/1/3     UP       UP      E1-120ohms    5-30
condor4#

As you can see, this command displays key information about presently configured CES E1 interfaces in an LS1010 chassis.

Configuring CES PAMs for Unstructured CES Services

This section presents the CLI-based procedures you use in configuring CES modules for unstructured (clear channel) CES services.

A circuit that you set up on a CBR port for unstructured service is always identified as "circuit 0," since there can only be one such circuit established on any given CBR port. Such a circuit consumes the entire bandwidth of a T1/E1 port, as indicated below:

• A hard PVC on a T1/E1 port--The entire bandwidth of a T1 port (1.544 Mbps) or an E1 port (2.048) Mbps) is provisioned manually at the time you set up the unstructured circuit and remains dedicated to that port, whether that port is actively transmitting CBR data or not.

• A soft PVC on a T1/E1 port--The entire bandwidth of a T1 port (1.544 Mbps) or an E1 port (2.048 Mbps) is also provisioned manually at the time you set up the circuit, but this bandwidth is consumed by the unstructured circuit only when it is active.

The procedures in this section begin with the simplest of the configuration tasks for unstructured CES services, namely, configuring a hard PVC to use adaptive clocking. This simplistic approach is being taken for the benefit of readers who may be new altogether to the task of configuring CES modules.

However, you should also be aware that synchronous clocking is the default clocking mode for all CES modules. It is the clocking mode appropriate to most CES applications. Accordingly, you may proceed directly to the later section entitled "Configuring a Hard PVC (with Synchronous Clocking)" if so doing meets your particular CES application requirements.

Configuring a Hard PVC (with Adaptive Clocking)

The primary purpose of a CES module is to convert CBR traffic into ATM cells for propagation through an ATM network. Hence, CBR traffic arriving on a given CES module port must first be segmented into ATM cells. This cell stream is then directed to an outgoing ATM port or CBR port. If the outgoing port is an ATM port on the same LS1010 chassis, then the PVC is called a "hard PVC."

Thus, as a general rule in setting up a hard PVC, you must interconnect a CBR port and an ATM port in the same LS1010 chassis.

For procedural purposes, assume that a CES module (identified as CBR0/1/0) and an ATM module (identified as ATM0/0/0) are the two interface modules to be involved in the hard PVC; assume further that this hard PVC will use adaptive clocking.

To set up a hard PVC on the target LS1010 switch that satisfies the above assumptions, perform the following steps:

Step 1 At the privileged EXEC mode prompt for the target chassis, enter the following command:

condor4#configure terminal
condor4(config)#

The configure command sets the chassis to the global configuration mode; terminal is a keyword that identifies the terminal (console) as the source of subsequent global configuration commands.

Step 2 At the global configuration mode prompt, enter the following command:

condor4(config)#interface CBR0/1/0
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies interface CBR0/1/0 as the chassis element to which subsequent configuration commands are to be applied.

This command also causes particular VPI and VCI values to be assigned automatically (implicitly) to the source port (CBR0/1/0) by LS1010 software (see Figure 28). These implicit VPI/VCI values are hardware dependent, that is, they are assigned by the system, based on the particular port being configured.

In effect, the CBR0/1/0 parameter is the port ID for the CES module--which tells you that the PAM is installed in the module 1 position of chassis slot 0.

For a more detailed description of the port ID parameter, see the earlier section entitled "Port IDs."

Step 3 At the interface configuration mode prompt, enter the following commands:

condor4(config-if)#no shutdown
condor4(config-if)#ces aal1 service unstructured
condor4(config-if)#ces aal1 clock adaptive

Respectively, these commands:

(a) Place the CES module in a fully operational or "UP" state, enabling all CES functions on the module.

(b) Direct the module to perform unstructured CES services.

(c) Direct the module to use adaptive clocking.

Step 4 To define the destination port (ATM 0/0/0) for the hard PVC, enter the following commands:

condor4(config-if)#ces circuit 0 circuit-name CBR-PVC-A
condor4(config-if)#ces pvc 0 interface ATM 0/0/0 vpi 0 vci 100
condor4(config-if)#^Z
condor4#

Respectively, these commands:

(a) Identify the hard PVC as "circuit 0" and assign it the logical circuit name "CBR-PVC-A" (see Figure 28). This logical name has been chosen for demonstration purposes only--it can be any ASCII string of your choosing. If you do not explicitly specify the "circuit-name" and "logical-name" parameters in the command line, the system automatically assigns a unique default name for the circuit being configured. This default name takes the form CBRx/y/z:#. Hence, the default name for this particular circuit would be "CBR0/1/0:0," where the notation preceding the colon uniquely identifies the port being configured, and the number following the colon identifies the circuit number (which, for unstructured CES services, is always 0).

(b) Identify a particular ATM interface module, port, and VPI/VCI value for the destination end of the hard PVC (see Figure 28).

---

Note The VPI/VCI values shown in the second line of the command sequence above ("vpi 0 vci 100") are for demonstration purposes only. If you were creating an actual hard PVC, you would know beforehand the applicable VPI/VCI values for the destination end of the hard PVC. For example, it can be safely assumed that you have already purchased a service from a common carrier (such as U.S. West) that provides a virtual path for CBR data transmission. However, from the 32,000 VCI numbers made available to you by the service provider, you must select a particular VCI for carrying your CBR traffic. You assign this VCI number beforehand, depending on the intended destination of your CBR data. In summary, the service provider gives you a virtual path for your data, but you must decide which VCI number to assign to the circuit.

---

(c) Exit from the interface configuration mode and return you to the privileged EXEC mode prompt.

After performing the above procedure, a hard PVC (circuit number 0) named CBR-PVC-A exists between the specified source port in the CES module and the specified destination port in the ATM module.

This CES circuit enables bidirectional, unstructured CBR traffic to flow between these two modules. Figure 28 is a logical representation of this circuit.

Figure 28: Hard PVC Configured for Unstructured CES Services

Verifying a Configured Hard PVC (with Adaptive Clocking)

To verify the hard PVC established in the procedure above, perform the following steps:

Step 1 To display the configured CES-IWF ATM address(es) for the local LS1010 chassis, enter the following command at the privileged EXEC mode prompt:

condor4#show ces address
CES-IWF ATM Address(es):
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 CBR-PVC-A

condor4#

This command displays the CES-IWF ATM address for the destination end of the circuit named CBR-PVC-A (see Figure 28). This address results from Step 4 in the section above entitled "Configuring a Hard PVC (with Adaptive Clocking)."

Step 2 To display basic information about the hard PVC, enter the following command:

condor4#show ces circuit
Interface Circuit Circuit-Type X-interface X-vpi X-vci Status
CBR0/1/0 0 HardPVC ATM0/0/0 0 100 UP

condor4#

This command verifies the source and destination port IDs of the hard PVC and indicates that the circuit is "UP, " that is, fully operational.

Step 3 To display detailed information about the hard PVC, enter the following command:

condor4#show ces circuit interface cbr0/1/0 0
Circuit: Name CBR-PVC-A, Circuit-state ADMIN_UP /
Interface CBR0/1/0, Circuit_id 0, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_ADAPT
Channel in use on this port: 1-24
Channels used by this circuit: 1-24
Cell-Rate: 4107, Bit-Rate 1544000
cas OFF, cell_header 0x100 (vci = 16)
cdv 2000 usecs, Measured cdv 350 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcAlarm, maxQueueDepth 883, startDequeueDepth 493
Partial Fill: 47, Structured Data Transfer 0
HardPVC
src: CBR0/1/0 vpi 0, vci 16
Dst: ATM0/0/0 vpi 0, vci 100

condor4#

This command displays all the configuration information relevant to the hard PVC that you set up in the preceding section.

Note that the "Port-Type" field in the third line of the output example above identifies the type of CES module that you have configured (which, in this case, is a T1 interface).

Note also that any hard PVC that you set up for unstructured CES services always carries the circuit identifier "Circuit_id 0," as shown in the third line of the output example above, since there can be only one such circuit in an unstructured hard PVC.

In other words, a hard PVC that you set up for unstructured CES services on any CBR port is always labeled circuit 0, since the entire bandwidth of the T1/E1 port is dedicated to that circuit.

Configuring a Hard PVC (with Synchronous Clocking)

For consistency, this procedure refers to the same port IDs that you used in setting up a hard PVC in the earlier section entitled "Configuring a Hard PVC (with Adaptive Clocking)."

To set up a hard PVC on the target LS1010 chassis with synchronous clocking, perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#configure terminal
condor4(config)#

Step 2 At the resulting global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/0
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies interface CBR0/1/0 as the chassis element to which subsequent interface configuration commands are to be applied.

Step 3 At the interface configuration mode prompt, enter the following commands:

condor4(config-if)#ces dsx1 clock source network-derived
condor4(config-if)#ces circuit 0 shutdown
condor4(config-if)#ces aal1 clock synchronous
condor4(config-if)#no ces circuit 0 shutdown
condor4(config-if)#^Z
condor4#

Respectively, these commands:

(a) Direct interface CBR0/1/0 to use the network-derived clocking signal (PRS) for network clock synchronization services. In the synchronous clocking mode, the PRS is always derived from the networking environment. Thus, you must set the CBR port to use this clocking signal for synchronizing CBR data transport.

(b) Temporarily disable all functions relating to circuit 0 on port CBR0/1/0.

(c) Define the synchronous clocking mode for use by port CBR0/1/0.

(d) Enable all functions for circuit 0 on the CES module.

(e) Exit from the interface configuration mode and return you to the privileged EXEC mode prompt.

Verifying a Configured Hard PVC (with Synchronous Clocking)

To verify the configuration information for a hard PVC with synchronous clocking, perform the following step:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#show ces circuit interface cbr 0/1/0 0
Circuit: Name CBR-PVC-A, Circuit-state ADMIN_UP /
Interface CBR0/1/0, Circuit_id 0, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 1-24
Channels used by this circuit: 1-24
Cell-Rate: 4107, Bit-Rate 1544000
cas OFF, cell_header 0x100 (vci = 16)
cdv 2000 usecs, Measured cdv 350 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcAlarm, maxQueueDepth 879, startDequeueDepth 491
Partial Fill: 47, Structured Data Transfer 0
HardPVC
src: CBR0/1/0 vpi 0, vci 16
Dst: ATM0/0/0 vpi 0, vci 100

condor4#

The output from this command verifies the configuration information for the source and destination ports for the hard PVC, confirms synchronous clocking for the circuit named CBR-PVC-A, and indicates that the circuit is operational ("UP").

Configuring a Soft PVC (with Synchronous Clocking)

In a soft PVC, as in a hard PVC, you also configure both ends of the CES circuit. However, a soft PVC typically involves CES modules at opposite edges of an ATM network. Thus, a soft PVC can be set up between any two CES modules anywhere in your network.

Accordingly, the destination address of a soft PVC can point to either of the following:

• A port in the same LS1010 chassis

• A port in any other CES module in the network

For example, if you wish to set up a soft PVC involving a local node and a destination node at the opposite edge of the network, you would need to determine the CES-IWF ATM address of the port in the destination node in order to complete soft PVC setup.

To obtain the destination address (dest-address) for an already configured port in a CES module elsewhere in the network, you would log into the remote LS1010 chassis containing that module and issue the show ces address command. This command displays all the CES-IWF ATM addresses currently configured for that node.

For simplicity, however, the procedure in this section assumes that you will be creating a soft PVC between interface modules in the same LS1010 chassis. Furthermore, this soft PVC will involve the same port IDs (CBR0/1/0 and CBR0/1/1) as those used in previous configuration procedures.

To obtain the address for a destination port that you are currently configuring as part of a new soft PVC, you would issue the show ces address, as shown in Step 4 of the following procedure.

To set up a soft PVC involving port IDs CBR0/1/0 and CBR0/1/1 on the target chassis (with synchronous clocking), perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#configure terminal
condor4(config)#

Step 2 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/1
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies interface CBR0/1/1 as the chassis element to which subsequent interface configuration commands are to be applied.

Step 3 At the interface configuration mode prompt, enter the following commands:

condor4(config-if)#ces dsx1 clock source network-derived
condor4(config-if)#no shutdown
condor4(config-if)#ces aal1 service unstructured
condor4(config-if)#ces aal1 clock synchronous
condor4(config-if)#ces circuit 0 circuit-name CBR-PVC-B
condor4(config-if)#^Z
condor4#

Respectively, these commands:

(a) Direct interface CBR0/1/1 to use the network-derived clocking signal (PRS) for network clock synchronization purposes. In the synchronous clocking mode, the PRS is always derived from a source within the networking environment. Therefore, you must set the CBR port to use this global clocking signal for synchronizing CBR data transport.

(b) Ensure that the target LS1010 chassis remains in an operational, or "UP" state.

(c) Set unstructured CES service for the soft PVC.

(d) Set the synchronous clocking mode for the circuit.

(e) Identify circuit 0 with the name "CBR-PVC-B." This logical name has been chosen for demonstration purposes only--it can be any ASCII string of your choosing. If you do not explicitly specify the "circuit-name" and "logical-name" parameters in this command line, the system automatically assigns a unique default name in the form CBRx/y/z:# for the circuit being configured. Hence, the default name for this particular circuit would be "CBR0/1/1:0," where the notation preceding the colon uniquely identifies the port being configured, and the number following the colon identifies the circuit number (which, for unstructured CES services, is always 0).

(f) Exit from the interface configuration mode and return you to the privileged EXEC mode prompt.

Step 4 At the privileged EXEC mode prompt, enter the following command:

condor4#show ces address
CES-IWF ATM Address(es):
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 CBR-PVC-A
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 CBR-PVC-B
condor4#

This command displays the CES-IWF ATM addresses for the circuit: CBR-PVC-A is the active (or source) side of the circuit, while CBR-PVC-B is the destination (or passive) side of the circuit (see Figure 29). You will need the address of the destination side of the circuit in completing Step 7 below.

Step 5 Establish the global configuration mode by entering the following command:

condor4#configure terminal
condor4(config)#

Step 6 Establish interface configuration mode by entering the following command:

condor4(config)#interface cbr 0/1/0
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies interface CBR0/1/0 as the chassis element to which subsequent interface configuration commands are to be applied.

Step 7 At the interface configuration mode prompt, enter the following commands:

condor4(config-if)#ces circuit 0 shutdown
condor4(config-if)#ces pvc 0 dest-address \
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0 vci 1040
condor4(config-if)#no ces circuit 0 shutdown
condor4(config-if)#^Z
condor4#

Respectively, these commands:

(a) Temporarily disable circuit 0.

(b) Assign the destination ATM address for circuit CBR-PVC B. This is the CES-IWF ATM address that you displayed by issuing the CLI show ces address command in Step 4 above.

(c) Re-enable the circuit, that is, return it to an operational state.

(d) Exit from the interface configuration mode and return you to the privileged EXEC mode prompt.

Figure 29 shows a logical representation of the soft PVC that you created in performing the procedure above.

Figure 29: Soft PVC Configured for Unstructured CES Services

Verifying a Configured Soft PVC (with Synchronous Clocking)

To verify the configuration information established above in creating the soft PVC, perform the following steps:

Step 1 To display the CES circuit, issue the following command at the privileged EXEC mode prompt:

condor4#show ces circuit
Interface Circuit Circuit-Type X-interface X-vpi X-vci Status
CBR0/1/0 0 Active SoftVC UNKNOWN 0 0 UP
CBR0/1/1 0 Passive SoftVC UNKNOWN 0 0 UP

condor4#

Step 2 To show detailed circuit information for port 1 (CBR0/1/1) of the soft PVC, issue the following command:

condor4#show ces circuit interface cbr 0/1/1 0
Circuit: Name CBR-PVC-B, Circuit-state ADMIN_UP /
Interface CBR0/1/1, Circuit_id 0, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 1-24
Channels used by this circuit: 1-24
Cell-Rate: 4107, Bit-Rate 1544000
cas OFF, cell_header 0x4100 (vci = 1040)
cdv 2000 usecs, Measured cdv 316 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcAlarm, maxQueueDepth 879, startDequeueDepth 491
Partial Fill: 47, Structured Data Transfer 0
Passive SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0, vci 1040
Dst: atm addr default vpi 0, vci 0

condor4#

Step 3 To show detailed circuit information for port 0 (CBR0/1/0) of the soft PVC, issue the following command:

condor4#show ces circuit interface cbr 0/1/0 0
Circuit: Name CBR-PVC-A, Circuit-state ADMIN_UP /
Interface CBR0/1/0, Circuit_id 0, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 1-24
Channels used by this circuit: 1-24
Cell-Rate: 4107, Bit-Rate 1544000
cas OFF, cell_header 0x100 (vci = 16)
cdv 2000 usecs, Measured cdv 316 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcAlarm, maxQueueDepth 879, startDequeueDepth 491
Partial Fill: 47, Structured Data Transfer 0
Active SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 vpi 0, vci 16
Dst: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0, vci 1040

condor4#

Deleting Previously-Established PVCs

This section assumes that you will be referencing the same port IDs (CBR0/1/0 and CBR0/1/1) as used in previous configuration procedures and that you will be deleting previously configured hard PVCs.

In deleting previously configured soft PVCs, the order and substance of the following procedure also applies.

To delete previously configured hard PVCs, perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#show ces circuit
Interface Circuit Circuit-Type X-interface X-vpi X-vci Status
CBR1/0 0 HardPVC ATM0/0 0 100 UP
CBR1/1 0 HardPVC ATM0/0 0 101 UP
condor4#

This command displays the hard PVCs (or soft PVCs) that are currently configured for your CES T1/E1 PAM.

Step 2 To establish the global configuration mode and identify the console as the source of subsequent command input, enter the following command:

condor4#configure terminal
condor4(config)#

Step 3 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/0
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies port CBR0/1/0 as the chassis element to which subsequent configuration commands are to be applied.

Step 4 At the interface configuration mode prompt, enter the following commands:

condor4(config-if)#no ces circuit 0
condor4(config-if)#exit
condor4(config)#

Respectively, these commands:

(a) Delete the previously-configured hard PVC on port 0.

(b) Exit from the interface configuration mode and return you to the global configuration mode.

Step 5 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/1
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies port CBR0/1/1 as the chassis element to which subsequent configuration commands are to be applied.

Step 6 At the interface configuration mode prompt, enter the following commands:

condor4(config-if)#no ces circuit 0
condor4(config-if)#exit
condor4(config)#^Z
condor4#

Respectively, these commands:

(a) Delete the previously-configured hard PVC on port 1.

(b) Exit from the interface configuration mode and return you to the global configuration mode.

(c) Exit from the global configuration mode and return you to the privileged EXEC mode prompt.

Verifying Deletion of Previously-Established PVCs

This procedure, based on the actions taken in the preceding section, enables you to verify the deletion of a previously-configured CES circuits.

To verify the deletion of a previously-established CES circuits, perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#show ces circuit
condor4#

The absence of output verifies that all CES circuits have been deleted.

Step 2 Similarly, at the privileged EXEC mode prompt, enter the following command:

condor4#show ces address

CES-IWF ATM Address(es):

condor4#

Again, the absence of output verifies that all previous CES-IWF addresses have been deleted.

Configuring CES PAMs for Structured CES Services

This section presents the CLI-based procedures you use in configuring CES modules for structured (N x 64 Kbps) CES services.

An important distinction that sets structured CES services apart from unstructured CES services is that the former allows you to allocate T1/E1 bandwidth in a highly flexible and efficient manner that consumes only the T1/E1 bandwidth actually required to support the active structured circuit(s) that you configure.

For example, in configuring a CES module for structured service, you can define multiple hard PVCs or soft PVCs for any given CES T1/E1 PAM port, as outlined below:

• CES T1 PAM--This module provides up to 24 DS0 time slots per T1 port for defining structured CES circuits. This represents a total CBR data transmission capacity of 1.536 Mbps (24 x 64 Kbps).

• CES E1 PAM (either 120-ohm or 75-ohm)--These modules provide up to 31 DS0 time slots per E1 port for defining structured CES circuits. This represents a total CBR data transmission capacity of 1.984 Mbps (31 x 64 Kbps).

In both module types, any bits not available for structured CES services are used for framing and out-of-band control.

For structured CES services, you can invoke an optional feature called channel associated signaling (CAS) that enables the ABCD signaling bits of a CBR bit stream to be incorporated into the ATM AAL1 cell stream and transported through the network. The section below entitled "Configuring a Soft PVC for Structured CES Services (with CAS enabled)" provides specific procedures for configuring such a circuit.

Also, in conjunction with the CAS feature, you can invoke an optional bandwidth-release feature that enables "on-hook" (idle) and "off-hook" (in use) conditions to be detected dynamically in a 1 x 64 (single DS0 time-slot) structured circuit. The section below entitled "Configuring Structured CES Services (with CAS and on-hook detection enabled)" describes how such a circuit is set up.

For simplicity in demonstrating configuration tasks for structured CES services, the procedures in this section are directed primarily to setting up a single CES circuit per T1/E1 port. However, these procedures outline the essential steps and CLI command syntax that you would use if you were to set up multiple CES circuits on a T1/E1 port.

Another important distinction of structured CES services is that such services require network clock synchronization by means of the synchronous clocking mode.

As noted in the earlier section entitled "Defining Network Clock Sources and Priorities for an LS1010 Chassis," you must select the clock source and define its priority locally for each LS1010 chassis in your network. You do this by means of the network-clock-select command.

For continuity, the structured CES configuration procedures in this section are based on the conventions outlined earlier in the section entitled "Conventions Adopted for CES Module Configuration Procedures."

Also, the assumptions pertaining to a particular structured CES configuration task are listed at the beginning of the procedure. Such information is provided as context for the task at hand and, hopefully, will promote a better understanding of structured CES configuration tasks in general.

Configuring a Hard PVC for Structured CES Services (without CAS enabled)

The assumptions relating to configuring a hard PVC for structured CES services include the following:

• Four time slots (DS0 channels 1-3, and 7) will be configured for a circuit named CBR-PVC-A.

• Channel associated signaling (CAS) will not be used.

• An ATM port in the LS1010 chassis will be designated as the destination port of the hard PVC.

To set up a hard PVC for structured CES services according to the assumptions above, perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#configure terminal

This command sets the LS1010 chassis to the global configuration mode and identifies the console (terminal) as the source of subsequent global configuration commands.

Step 2 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/0

This command sets the LS1010 chassis to the interface configuration mode and identifies port CBR0/1/0 as the chassis element to which subsequent configuration commands will be applied.In effect, this port becomes the source port of the hard PVC (see Figure 30).

The VPI/VCI values shown for the source port in Figure 30 are automatically (implicitly) assigned by PAM hardware. In other words, these values are hardware-dependent entities that uniquely identify the port being configured.

Step 3 At the interface configuration mode prompt, enter the following command:

condor4(config-if)#ces dsx1 clock source network-derived

This command directs port CBR0/1/0 to use the network-derived clocking signal (PRS) for network clock synchronization services. In the synchronous clocking mode, the PRS is always derived from the networking environment. Therefore, you must set the CBR port to use this clocking signal for synchronizing CBR data transport.

Step 4 To direct the port to support b8zs coding for the DSX-1 physical layer, enter the following command:

condor4(config-if)#ces dsx1 line-coding b8zs

Step 5 To direct the port to use the extended super frame (ESF) framing format for the T1/E1 interface, enter the following command:

condor4(config-if)#ces dsx1 framing esf

Step 6 To enable the port, that is, set it to a fully operational state, enter the following command:

condor4(config-if)#no shutdown

Step 7 To establish structured CES services for the port, enter the following command:

condor4(config-if)#ces aal1 service structured

Step 8 To establish the synchronous clocking mode for the port, enter the following command:

condor4(config-if)#ces aal1 clock synchronous

At the conclusion of Step 8, you have completed the configuration of the desired port for the structured CES circuit. You can now proceed with the actual creation of the hard PVC.

Step 9 To specify the four DS0 time slots to be used by the hard PVC, enter the following command:

condor4(config-if)#ces circuit 1 timeslots 1-3,7

Step 10 To give the hard PVC a logical name by which it will be identified, enter the following command:

condor4(config-if)#ces circuit 1 circuit-name CBR-PVC-A

Note that the logical name CBR-PVC-A is used for demonstration purposes only--it can be any ASCII string of your choosing. If you do not explicitly specify the "circuit-name" and "logical-name" parameters in the command line, the system automatically assigns a unique default name in the form CBRx/y/z:# for the circuit being configured.

Hence, the default name for this particular circuit would be "CBR0/1/0:1," where the notation preceding the colon uniquely identifies the port, and the number following the colon uniquely identifies the circuit being configured. For structured CES services, the circuit number sequence always begins at 1 for each port in a CES module.

---

Note You need not specify individual circuit options on a separate command line, as shown in Step 9 and Step 10 above. If you wish, you can specify all the desired circuit options on the same command line, provided that you observe the following rules: a) specify the DS0 time slots as the first option; b) specify each desired option thereafter in strict alphabetic order; and, c) separate each command line option with a space. You can display the options available for any structured CES circuit. For example, in this particular case, you would issue a CLI ces circuit1 ? command, which would display in alphabetic order all the options available for use in the command line.

---

Step 11 To enable the hard PVC, enter the following command:

condor4(config-if)#no ces circuit 1 shutdown

Step 12 To define the destination end of the hard PVC and exit from the interface configuration mode, enter the following commands:

condor4(config-if)#ces pvc 1 interface atm 0/0/0 vpi 0 vci 100
condor4(config-if)#^Z
condor4#

Respectively, these commands:

(a) Define a particular ATM port as the destination end of the hard PVC.

(b) Return you to the privileged EXEC mode prompt.

At the conclusion of this procedure, you have created a hard PVC configured for structured CES services, as shown in Figure 30.

Figure 30: Hard PVC Configured for Structured CES Services

Verifying a Configured Hard PVC (without CAS enabled)

To verify the hard PVC that you set up in the previous procedure, perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#show ces address

CES-IWF ATM Address(es):
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 CBR-PVC-A

This command displays the 20-byte CES-IWF ATM address assigned to the source end of the hard PVC. This address is automatically (implicitly) assigned by the CES hardware to identify the source end of the hard PVC.

Step 2 To display the details of the hard PVC, enter the following command:

condor4#show ces circuit
Interface Circuit Circuit-Type X-interface X-vpi X-vci Status
CBR0/1/0 1 HardPVC ATM0/0/0 0 100 UP

condor4#

Step 3 To display the interface details for port CBR0/1/0, enter the following command:

condor4#show ces circuit interface cbr 0/1/0 1
Circuit: Name CBR-PVC-A, Circuit-state ADMIN_UP /
Interface CBR0/1/0, Circuit_id 1, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 1-3,7
Channels used by this circuit: 1-3,7
Cell-Rate: 681, Bit-Rate 256000
cas OFF, cell_header 0x100 (vci = 16)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcLoc, maxQueueDepth 57, startDequeueDepth 40
Partial Fill: 47, Structured Data Transfer 1
HardPVC
src: CBR0/1/0 vpi 0, vci 16
Dst: ATM0/0/0 vpi 0, vci 100

condor4#

Configuring a Soft PVC for Structured CES Services (without CAS enabled)

The procedure below for configuring a soft PVC for structured service is based on the following assumptions:

• Four time slots (DS0 channels) will be configured for the soft PVC, as follows:

  • For circuit CBR-PVC-A--DS0 channels 1-3 and 7 will be operative on port CBR0/1/0, as configured previously in Step 9 of the section above entitled "Configuring a Hard PVC for Structured CES Services (without CAS enabled)."

  • For circuit CBR-PVC-B--DS0 channels 10-13 will be used on port CBR0/1/1.

• Channel associated signaling (CAS) will not be used.

• The source (active) side of the soft PVC will be named "CBR-PVC-A."

• The destination (passive) side of the soft PVC will be named "CBR-PVC-B."

To set up a soft PVC for structured CES services according to the assumptions above, perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#configure terminal

This command sets the LS1010 chassis to the global configuration mode and identifies the console (terminal) as the source of subsequent global configuration commands.

Step 2 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/1
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies interface CBR0/1/1 as the chassis element to which subsequent configuration commands are to be applied.

In effect, this port is the destination end of the soft PVC (see Figure 31). Refer to the section entitled "Guidelines for Creating Soft PVCs for CES Services," wherein you are instructed to configure the destination end of the soft PVC first.

Step 3 To direct port CBR0/1/1 to use the network-derived clocking signal (PRS) for network clock synchronization services, enter the following command at the interface configuration mode prompt:

condor4(config-if)#ces dsx1 clock source network-derived

In the synchronous clocking mode, the PRS is always derived from a source within the networking environment. Therefore, you must set the CBR port to use this clocking signal for synchronizing CBR data transport.

Step 4 To direct the CES module to use b8zs line coding, enter the following command:

condor4(config-if)#ces dsx1 line-coding b8zs

Step 5 To direct the CES module to use the extended super frame (ESF) framing format, enter the following command:

condor4(config-if)#ces dsx1 framing esf

Step 6 To enable the destination port (CBR0/1/1), that is, set it to a fully operational state, enter the following command:

condor4(config-if)#no shutdown

Step 7 To establish structured services for the port, enter the following command:

condor4(config-if)#ces aal1 service structured

Step 8 To establish the synchronous clocking mode for port, enter the following command:

condor4(config-if)#ces aal1 clock synchronous

Upon completion of this step, you have completed the configuration of the destination port (CBR0/1/1) on the CES module. You now proceed with the actual creation of the soft PVC on the module.

Step 9 To specify the four DS0 time slots to be used by the soft PVC, enter the following command:

condor4(config-if)#ces circuit 1 timeslots 10-13

Step 10 To identify the destination (passive) end of the soft PVC, enter the following command:

condor4(config-if)#ces circuit 1 circuit-name CBR-PVC-B

The logical name "CBR-PVC-B" is used for demonstration purposes only--it can be any ASCII string of your choosing. If you do not explicitly specify the "circuit-name" and "logical-name" parameters in the command line, the system automatically assigns a unique default name in the form CBRx/y/z:# for the circuit.

The default name in this case would be "CBR0/1/1:1," where the notation preceding the colon uniquely identifies the destination port being configured, and the number following the colon uniquely identifies the circuit. For structured CES services, the circuit number sequence always begins at 1 for each port on a CES module.

---

Note You need not specify individual circuit options on a separate command line, as shown in Step 9 and Step 10 above. If you wish, you can specify all the desired circuit options on the same command line, provided that you observe the following rules: a) specify the DS0 time slots as the first option; b) specify each desired option thereafter in strict alphabetic order; and, c) separate each command line option with a space. You can display the options available for any structured CES circuit. For example, in this particular case, you would issue a CLI ces circuit1 ? command, which would display in alphabetic order all the circuit options available for use in the command line.

---

Step 11 To enable the interface for the destination (passive) end of the soft PVC, that is, make it operational, enter the following command:

condor4(config-if)#no ces circuit 1 shutdown

Step 12 To exit from the interface configuration mode and return to the privileged EXEC mode prompt, enter the following command:

condor4(config-if)#^Z

condor 4#

Step 13 To retrieve the ATM address for the destination (passive) end of the soft PVC (CBR-PVC-B), enter the following command:

condor4#show ces address

CES-IWF ATM Address(es):
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 CBR-PVC-A
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 CBR-PVC-B

condor4#

The second of the two lines above is the CES-IWF ATM address for circuit CBR-PVC-B, that is, the destination end of the soft PVC. You will use this address in Step 18 below.

Step 14 To retrieve the VCI number for circuit CBR-PVC-B, enter the following command:

condor4#show ces circuit interface cbr 0/1/1 1
Circuit: Name CBR-PVC-B, Circuit-state ADMIN_UP / OPER_DOWN
Interface CBR0/1/1, Circuit_id 1, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 10-13
Channels used by this circuit: 10-13
Cell-Rate: 681, Bit-Rate 256000
cas OFF, cell_header 0x4100 (vci = 1040)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcInactive, maxQueueDepth 57, startDequeueDepth 40
Partial Fill: 47, Structured Data Transfer 1
Passive SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0, vci 1040
Dst: atm addr default vpi 0, vci 0


condor4#

This command displays the interface details for circuit CBR-PVC-B, among which is the "vpi 0 vci 1040" field near the end of the output example above. You will need this value in configuring the destination ATM address in conjunction with defining the source end of the soft PVC on CBR0/1/0 (see Step 18 below).

Step 15 To set the LS1010 chassis to the global configuration mode and identify the console (terminal) as the source of subsequent global configuration commands, enter the following command:

condor4#configure terminal

Step 16 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/0
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies interface CBR0/1/0 as the chassis element to which subsequent configuration commands are to be applied. In effect, this command identifies the source (active) side of the soft PVC.

Step 17 To temporarily disable interface CBR0/1/0, enter the following command:

condor4(config-if)#ces circuit 1 shutdown

Step 18 To establish the destination CES-IWF ATM address to be used by CBR port 0/1/0 in completing the soft PVC, enter the following command:

condor4(config-if)#ces pvc 1 dest-address \
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0 vci 1040

The command string in the second line above is the CES-IWF ATM address of the destination end of the soft PVC. You obtained this address in Step 13 above.

Note also that the "vpi 0 vci 1040" values that you entered as the last element in the command string above were obtained as a result of Step 14 above.

Step 19 To re-enable the source port (CBR0/1/0), that is, make it operational, enter the following command:

condor4(config-if)#no ces circuit 1 shutdown

Step 20 To exit from the interface configuration mode, enter the following command:

condor4(config-if)#^Z

condor4#

This command returns you to the privileged EXEC mode prompt.

After performing this procedure, you have created a soft PVC configured for structured CES services (without channeling associated signaling), as shown in Figure 31.

Figure 31: Soft PVC Configured for Structured CES Services (without CAS enabled)

Verifying a Configured Soft PVC (without CAS enabled)

To verify the soft PVC that you set up in the previous procedure, perform the following steps:

Step 1 To display the CES-IWF ATM addresses for the soft PVC, enter the following command at the privileged EXEC mode prompt:

condor4#show ces address

CES-IWF ATM Address(es):
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 CBR-PVC-A
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 CBR-PVC-B

condor4#

Step 2 To display the details of the CES circuit, enter the following command:

condor4#show ces circuit
Interface Circuit Circuit-Type X-interface X-vpi X-vci Status
CBR0/1/0 1 Active SoftVC UNKNOWN 0 0 UP
CBR0/1/1 1 Passive SoftVC UNKNOWN 0 0 UP

condor4#

Step 3 To display the interface details for the source port (CBR0/1/0), enter the following command:

condor4#show ces circuit interface cbr 0/1/0 1
Circuit: Name CBR-PVC-A, Circuit-state ADMIN_UP /
Interface CBR0/1/0, Circuit_id 1, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 1-3,7
Channels used by this circuit: 1-3,7
Cell-Rate: 681, Bit-Rate 256000
cas OFF, cell_header 0x100 (vci = 16)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcActive, maxQueueDepth 57, startDequeueDepth 40
Partial Fill: 47, Structured Data Transfer 1
Active SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 vpi 0, vci 16
Dst: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0, vci 1040

condor4#

Step 4 To display the interface details for the destination port (CBR0/1/1), enter the following command:

condor4#show ces circuit interface cbr 0/1/1 1
Circuit: Name CBR-PVC-B, Circuit-state ADMIN_UP /
Interface CBR0/1/1, Circuit_id 1, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 10-13
Channels used by this circuit: 10-13
Cell-Rate: 681, Bit-Rate 256000
cas OFF, cell_header 0x4100 (vci = 1040)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcActive, maxQueueDepth 57, startDequeueDepth 40
Partial Fill: 47, Structured Data Transfer 1
Passive SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0, vci 1040
Dst: atm addr default vpi 0, vci 0

condor4#

Configuring a Soft PVC for Structured CES Services (with CAS enabled)

The procedures in this section build on the configuration information already established for the soft PVC created in the earlier section entitled "Configuring a Soft PVC for Structured CES Services (without CAS enabled)."

In other words, the only difference between the earlier procedure and the one that follows is that the latter enables channel association signaling (CAS) for the soft PVC.

Hence, the following procedure is based on the following assumptions:

• Four time slots (DS0 channels) will remain as previously configured for the soft PVC:

  • For circuit CBR-PVC-A--DS0 channels 1-3 and 7 on port CBR0/1/0

  • For circuit CBR-PVC-B--DS0 channels 10-13 on port CBR0/1/1

• Channel associated signaling (CAS) is to be enabled for the circuit.

• The signaling mode for the CBR ports is to be set to "robbedbit."

• The source (active) side of the soft PVC (CBR-PVC-A) will remain as previously configured.

• The destination (passive) side of the soft PVC (CBR-PVC-B) will remain as previously configured.

To set up a soft PVC for structured CES services with channel associated signaling (CAS) according to the assumptions above, perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#configure terminal

This command sets the LS1010 chassis to the global configuration mode and identifies the console (terminal) as the source of global configuration command input.

Step 2 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/0
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies port CBR0/1/0 as the chassis element to which configuration commands are to be applied.

In effect, this port is the source port for the soft PVC (see Figure 32).

Step 3 At the configuration interface mode prompt, enter the following commands:

condor4(config-if)#ces dsx1 signalmode robbedbit
condor4(config-if)#ces circuit 1 shutdown
condor4(config-if)#ces circuit 1 cas
condor4(config-if)#no ces circuit 1 shutdown
condor4(config-if)#

Respectively, these commands:

(a) Set the signaling mode for the source port to "robbedbit."

(b) Temporarily disable the source port, that is, make it non-operational.

(c) Enable channel associated signaling for the CES circuit.

(d) Re-enable the source port to make it fully operational.

Step 4 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/1
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and identifies port CBR0/1/1 as the chassis element to which subsequent configuration commands will be applied.

In effect, this port is the destination port for the soft PVC (see Figure 32).

Step 5 At the configuration interface mode prompt, enter the following commands:

condor4(config-if)#ces dsx1 signalmode robbedbit
condor4(config-if)#ces circuit 1 shutdown
condor4(config-if)#ces circuit 1 cas
condor4(config-if)#no ces circuit 1 shutdown
condor4(config-if)#^Z
condor4#

Respectively, these commands:

(a) Set the signaling mode for the destination port to "robbedbit."

(b) Temporarily disable the destination port to make it non-operational.

(c) Enable channel associated signaling for the CES circuit.

(d) Re-enable the destination port to make it operational.

(e) Exit from the interface configuration mode and return you to the privileged EXEC mode prompt.

After performing this procedure, you have created a soft PVC configured for structured CES services (with CAS), as shown in Figure 32.

Figure 32: Soft PVC Configured for Structured CES Services (with CAS)

Verifying a Configured Soft PVC (with CAS)

To verify the soft PVC that you set up in the previous procedure, perform the following steps:

Step 1 To display the details of the CES circuit, enter the following command at the privileged EXEC mode prompt:

condor4#show ces circuit
Interface Circuit Circuit-Type X-interface X-vpi X-vci Status
CBR0/1/0 1 Active SoftVC UNKNOWN 0 0 UP
CBR0/1/1 1 Passive SoftVC UNKNOWN 0 0 UP

condor4#

Step 2 To display the CES-IWF ATM addresses for the soft PVC, enter the following command:

condor4#show ces address

CES-IWF ATM Address(es):
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 CBR-PVC-A
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 CBR-PVC-B

condor4#

Step 3 To display the interface details for the source port (CBR0/1/0), enter the following command:

condor4#show ces circuit interface cbr 0/1/0 1
Circuit: Name CBR-PVC-A, Circuit-state ADMIN_UP /
Interface CBR0/1/0, Circuit_id 1, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 1-3,7
Channels used by this circuit: 1-3,7
Cell-Rate: 697, Bit-Rate 256000
cas ON, cell_header 0x100 (vci = 16)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcActive, maxQueueDepth 57, startDequeueDepth 40
Partial Fill: 47, Structured Data Transfer 1
Active SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 vpi 0, vci 16
Dst: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0, vci 1040

condor4#

Step 4 To display the interface details for the destination port (CBR0/1/1), enter the following command:

condor4#show ces circuit interface cbr 0/1/1 1
Circuit: Name CBR-PVC-B, Circuit-state ADMIN_UP /
Interface CBR0/1/1, Circuit_id 1, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 10-13
Channels used by this circuit: 10-13
Cell-Rate: 697, Bit-Rate 256000
cas ON, cell_header 0x4100 (vci = 1040)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcActive, maxQueueDepth 57, startDequeueDepth 40
Partial Fill: 47, Structured Data Transfer 1
Passive SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 vpi 0, vci 1040
Dst: atm addr default vpi 0, vci 0

condor4#

Configuring Structured CES Services (with CAS and on-hook detection enabled)

This section outlines the additional steps that you must take to activate the on-hook detection (bandwidth-release) feature in a 1 x 64 structured CES circuit. These steps are summarized briefly below:

Step 1 Configure the structured CES circuit, with CAS enabled. Detailed steps for creating such a circuit are presented in the earlier section entitled "Configuring a Soft PVC for Structured CES Services (with CAS enabled)."

Step 2 Configure the circuit using only one DS0 time slot at each end of the connection.

Step 3 Enable the on-hook detection feature for the circuit by issuing the following CLI command:

condor4#CES circuit 1 on-hook-detect 2

The parameter "2" in the command example above is a decimal representation of the four hexadecimal "ABCD" bits of the CAS mechanism. Thus, for purposes of this example, you can assume that the hexadecimal number 2, or binary bit pattern 0010, has been chosen to represent the on-hook state for the CES circuit.

These four ABCD bits in the CAS mechanism are device-specific, depending on the manufacturer of the voice/video telephony device that is generating the CBR traffic. Hence, the ABCD bits of the CAS mechanism are said to be user-configurable.

Creating Multiple Soft PVCs on Same CES Port

The following procedure demonstrates the logical process that you would complete in creating more than one structured service PVC on the same T1/E1 port.

For example, Figure 33 is a logical representation of how multiple CES circuits can be configured on a single T1/E1 port.

The procedures in this section proceed from the premise that certain configuration information has already been established for a soft PVC, as shown in Figure 31, and that you are to create an additional soft PVC involving the same CES module.

Hence, the following assumptions apply for the task of creating a multiple soft PVC on the same T1/E1 port:

• The source (active) side of a soft PVC named "CBR-PVC-A" has already been created on port CBR0/1/0 (see Figure 33).

• The destination (passive) side of a soft PVC named "CBR-PVC-B" has already been created on port CBR0/1/1 (see Figure 33).

• A new source (active) side of a soft PVC named CBR-PVC-AC is to be created on port CBR0/1/0 of the CES module, thereby creating a multiple CES circuit on this particular port (see Figure 33).

• A new destination (passive) side of a soft PVC named CBR-PVC-CA is to be created on port CBR0/1/2 of the CES module (see Figure 33.

Figure 33: Configuring Multiple Soft PVCs on Same T1/E1 Port

To create multiple soft PVCs on the same port according to the assumptions above, perform the following steps:

Step 1 At the privileged EXEC mode prompt, enter the following command:

condor4#configure terminal

This command sets the LS1010 chassis to the global configuration mode and identifies the console (terminal) as the source of global configuration command input.

Step 2 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/2
condor4(config)#

This command sets the LS1010 chassis to the interface configuration mode and identifies port CBR0/1/2 as the chassis element to which further configuration commands are to be applied.

In effect, this port is the destination side of the new soft PVC. Refer to the section entitled "Guidelines for Creating Soft PVCs for CES Services," which describes the rationale that requires you to configure the destination end of the soft PVC first.

Step 3 At the interface configuration mode prompt, enter the following commands:

condor4(config-if)#ces dsx1 clock source network-derived
condor4(config-if)#ces dsx1 line-coding b8zs
condor4(config-if)#ces dsx1 framing esf
condor4(config-if)#no shutdown
condor4(config-if)#

Respectively, these commands:

(a) Direct the destination port (CBR0/1/2) to use a network-derived PRS for network clock synchronization services.

(b) Direct the port to use b8zs line coding.

(c) Direct the port to use the extended super frame (ESF) framing format.

(d) Enable the port to make it operational.

Step 4 Continue with the following commands to complete the configuration of the destination port:

condor4(config-if)#ces aal1 service structured
condor4(config-if)#ces aal1 clock synchronous
condor4(config-if)#ces circuit 1 timeslots 10 circuit-name CBR-PVC-CA
condor4(config-if)#no ces circuit 1 shutdown
condor4(config-if)#exit
condor4(config)#

Respectively, these commands:

(a) Establish structured CES services for the destination port (CBR0/1/2).

(b) Establish the synchronous clocking mode for the port.

(c) Establish CES circuit 1 on the port, direct the port to use 10 DS0 time slots for structured CES services, and assign the circuit the logical name "CBR-PVC-CA." This name is used for demonstration purposes only--it can be any ASCII string of your choosing. If you do not explicitly specify the "circuit-name" and "logical-name" parameters in the command line, the system automatically assigns a unique default name in the form CBRx/y/z:# for the circuit. The default name in this case would be "CBR0/1/2:1," where the notation preceding the colon uniquely identifies the port being configured, and the number following the colon uniquely identifies the circuit on that port. For structured CES services, the circuit number sequence always begins at 1 for each port on a CES module.

---

Note As shown in the third line of the command sequence above, you can specify multiple circuit options in the same command line. In fact, it is possible to specify all the desired circuit options on the same command line, provided that you observe the following rules: a) specify the DS0 time slots as the first command line option; b) specify each desired option thereafter in strict alphabetic order; and, c) separate each command line option with a space. To display all the CES circuits you have configured, you can issue the CLI ces circuit ? command. To display all the options available for any structured CES circuit, you can issue the CLI ces circuitx ? command, where "x" is a circuit identifier in the form of an integer (in a range from 1 - 24 for a 120-ohm E1 PAM or 1 - 31 for a BNC E1 PAM). This command displays in alphabetic order all the options available for the specified structured circuit. Note, however, that specifying zero (0) as the circuit identifier in this command will only display the options available for an unstructured (clear channel) circuit.

---

(d) Enable the destination port to make it operational.

(e) Exit from the interface configuration mode and return you to the global configuration mode.

Step 5 At the global configuration mode prompt, enter the following command:

condor4(config)#interface cbr 0/1/0
condor4(config-if)#

This command sets the LS1010 chassis to the interface configuration mode and sets port CBR0/1/0 as the chassis element to which further configuration commands are to be applied.

In effect, this is the source port of the new multiple soft PVC that you are configuring on the same port (port 0) of the CES module (see Figure 33).

Step 6 At the interface configuration mode prompt, enter the following commands:

condor4(config-if)#ces circuit 2 timeslots 24
condor4(config-if)#ces circuit 2 circuit-name CBR-PVC-AC
condor4(config-if)#no ces circuit 1 shutdown
condor4(config-if)#^Z
condor4#

Respectively, these commands:

(a) Establish circuit 2 on the same port (CBR0/1/0) and direct the port to use 24 DS0 time slots for the new soft PVC.

(b) Assign circuit 2 the logical name "CBR-PVC-AC." This name is used for demonstration purposes only--it can be any ASCII string of your choosing. If you do not explicitly specify the "circuit-name" and "logical-name" parameters in the command line, the system automatically assigns a unique default name in the form CBRx/y/z:# for the circuit. The default name in this case would be "CBR0/1/0:2," where the notation preceding the colon uniquely identifies the port being configured, and the number following the colon uniquely identifies the circuit on that port. For structured CES services, the circuit number sequence always begins at 1 for each port on a CES module.

(c) Enable the source port to make it operational for the new soft PVC.

(d) Exit from the interface configuration mode and return you to the privileged EXEC mode prompt.

Step 7 At this point, you need to display the CES-IWF ATM addresses assigned by the PAM hardware as the first step toward defining the CES-IWF ATM address for the destination port (CBR-PVC-CA).

To display the CES-IWF ATM addresses assigned by the PAM hardware, issue the following command:

condor4#show ces address

CES-IWF ATM Address(es):
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 CBR-PVC-A
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.20 CBR-PVC-AC
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 CBR-PVC-B
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1038.10 CBR-PVC-CA

condor4#

The last line in the output example above is the CES-IWF ATM address of the destination (passive) side of the new soft PVC that you are creating. Keep this address in mind in relation to Step 9 below.

Step 8 To retrieve the VPI/VCI values pertaining to the destination port (CBR-PVC-CA), enter the following command at the privileged EXEC mode prompt:

condor4#show ces circuit interface cbr 0/1/2 1
Circuit: Name CBR-PVC-CA, Circuit-state ADMIN_UP /
Interface CBR0/1/2, Circuit_id 1, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 10
Channels used by this circuit: 10
Cell-Rate: 171, Bit-Rate 64000
cas OFF, cell_header 0x8100 (vci = 2064)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcInactive, maxQueueDepth 0, startDequeueDepth 0
Partial Fill: 47, Structured Data Transfer 1
Passive SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1038.10 vpi 0, vci 2064
Dst: atm addr default vpi 0, vci 0

condor4#

Note the VPI/VCI values in the next to last line of the output example above, namely, "vpi 0, vci 2064." These are the VPI/VCI values that you must enter in Step 9, together with the CES-IWF ATM address of the destination port of the new soft PVC (CBR-PVC-CA) that you obtained in Step 7 above.

Step 9 To complete the creation of the new soft PVC from the source port (CBR-PVC-AC) to the destination port (CBR PCV-CA), enter the following commands:

condor4#configure terminal
condor4(config)#interface cbr 0/1/0
condor4(config-if)#ces pvc 2 dest-address \
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1038.10 vpi 0 vci 2064
condor4(config-if)#no ces circuit 2 shutdown
condor4(config-if)#^Z

condor4#

Respectively, these commands:

(a) Set the LS1010 chassis to the global configuration mode and establish the console (terminal) as the source of global configuration commands.

(b) Set the chassis to the interface configuration mode and establish CBR0/1/0 as the chassis element to which configuration commands are to be applied.

(c) Assign the CES-IWF ATM address to the destination port (CBR0/1/2) of the new soft PVC named CBR-PVC-CA (see Figure 33).

(d) Enable the circuit to make the new soft PVC operational.

(e) Exit from the interface configuration mode and return you to the privileged EXEC mode prompt.

After completing this procedure, you have, in effect, created two structured service soft PVCs on port 0 (CBR0/1/0) of the CES module.

Verifying Creation of Multiple Soft PVCs on Same CES Port

To verify the multiple soft PVCs that you created on the same port in the procedure above, perform the following steps:

Step 1 To display the circuit details for the soft PVCs that you created in the previous procedure, enter the following command at the privileged EXEC mode prompt:

condor4#show ces circuit
Interface Circuit Circuit-Type X-interface X-vpi X-vci Status
CBR0/1/0 1 Active SoftVC UNKNOWN 0 0 UP
CBR0/1/0 2 Active SoftVC UNKNOWN 0 0 UP
CBR0/1/1 1 Passive SoftVC UNKNOWN 0 0 UP
CBR0/1/2 1 Passive SoftVC UNKNOWN 0 0 UP

condor4#

Step 2 To display the CES-IWF addresses of the soft PVCs that you set up, enter the following command at the privileged EXEC mode prompt:

condor4#show ces address

CES-IWF ATM Address(es):
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.10 CBR-PVC-A
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.20 CBR-PVC-AC
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1034.10 CBR-PVC-B
47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1038.10 CBR-PVC-CA

condor4#

Step 3 To display the interface details for the new circuit 2 soft PVC that you set up on port CBR0/1/0, issue the following command:

condor4#show ces circuit interface cbr 0/1/0 2
Circuit: Name CBR-PVC-AC, Circuit-state ADMIN_UP /
Interface CBR0/1/0, Circuit_id 2, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 1-3,7,24
Channels used by this circuit: 24
Cell-Rate: 171, Bit-Rate 64000
cas OFF, cell_header 0x200 (vci = 32)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcActive, maxQueueDepth 128, startDequeueDepth 111
Partial Fill: 47, Structured Data Transfer 1
Active SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1030.20 vpi 0, vci 32
Dst: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1038.10 vpi 0, vci 2064

condor4#

This command displays the interface details pertaining to circuit 2 of the multiple CES soft PVC previously set up on port 0 of the CES module.

Step 4 To display the interface details for the new circuit 1 soft PVC that you set up on port CBR0/1/2, issue the following command:

condor4#show ces circuit interface cbr 0/1/2 1
Circuit: Name CBR-PVC-CA, Circuit-state ADMIN_UP /
Interface CBR0/1/2, Circuit_id 1, Port-Type T1, Port-State UP
Port Clocking network-derived, aal1 Clocking Method CESIWF_AAL1_CLOCK_SYNC
Channel in use on this port: 10
Channels used by this circuit: 10
Cell-Rate: 171, Bit-Rate 64000
cas OFF, cell_header 0x8100 (vci = 2064)
cdv 2000 usecs, Measured cdv -1 usecs
ErrTolerance 8, idleCircuitdetect OFF, onHookIdleCode 0x0
state: VcActive, maxQueueDepth 128, startDequeueDepth 111
Partial Fill: 47, Structured Data Transfer 1
Passive SoftVC
Src: atm addr 47.0091.8100.0000.0060.5c71.1f01.4000.0c80.1038.10 vpi 0, vci 2064
Dst: atm addr default vpi 0, vci 0

condor4#

At the conclusion of this procedure, you have verified that the procedure for creating multiple soft PVCs on the same CES port were correctly performed.

Cisco Connection Online

Cisco Connection Online (CCO), formerly Cisco Information Online (CIO), is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional content and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously--a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

• WWW:  http://www.cisco.com.

• WWW:  http://www-europe.cisco.com.

• WWW:  http://www-china.cisco.com.

• Telnet:  cco.cisco.com.

• Modem:  From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and baud rates up to 14.4 Kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

---

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

---