Configuring Service on a T3 or E3 CESM

command is addcon. If the application requires NSAP addressing, use addchan to add the connection and cnfchan if you need to modify it. Refer to the command reference for the syntax. On the CESM CLI:

Step 1 Add a connection by executing addcon. (Alternatively, you can use addchan if your application requires the NSAP format of endpoint specification.) Execute addcon at both ends of the connection—unless the remote endpoint is on port 34 of a PXM (see the note at the end of this step).

The syntax for addcon is:

addcon <port_num> [mastership [remoteConnId] ]

•port_num is the logical port number and is always 1.

•mastership indicates whether this endpoint is the master or slave. 1=master. 2=slave (default).

•remoteConnId is the identification for the connection at the slave end. The format is nodename.slot_number.port_number.vpi.vci. For the MGX-CESM-T3 and MGX-CESM-E3, the vpi and vci are typically 0 or 1.

Note For the channel number, the system always returns the number 32 for the high speed CESM. If you execute dspchan, use the channel number 32 to see details about the channel (or dspchans—and no arguments—to see high level details about the channel). In contrast, the dspcon command takes the port number 1 to identify the connection even though it shows the same information as dspchan.

Step 2 Optionally, you can use cnfcon to modify the connection.

cnfcon <port_num> <CDVT> <CellLossIntegPeriod> <bufsize>

•port_num is the port number and is always 1.

•CDVT is a tolerable variation for the arrival time of cells. For T3, the range is 125–1447 micro seconds in 125-microsecond increments. For E3, the range is 125–1884 micro seconds in 125-microsecond increments.

•CellLossIntegrationPeriod is the amount of time a connection can be in an error condition before an alarm is declared. The range is 1000–65535 milli seconds.

•bufsize is the egress buffer size in bytes. You can let the CESM compute the size by entering 0 for bufsize or enter the number of bytes up to a maximum of 16224.

Step 3 Optionally, you can use cnfswparms on a BPX 8600-series switch to configure connection parameters for the network segment of a three-segment connection. For a stand-alone application, use whatever means are supported by the backbone switches.

cnfswparms <chan_num> <mastership> <vpcflag> <conn_service_type> (=cos) <route_priority> <max_cost> <restrict_trunk_type> <pcr> <mcr> <pct_util>

•chan_number is the channel (connection) number and is always 32.

•mastership specifies the current endpoint as master or slave. 1=master. 2=slave (default)

•vpcflag indicates whether the connection is a VPC or a VCC: 1=VPC, and 2=VCC.

•conn_service_type selects the type of service for the connection: 1=cbr, 2=vbr, 3 is not used, 4=ubr, 5=atfr, 6=abrstd, and 7=abrfst.

Card and Service Configuration 6-39

Page 38 Page 40
Page 39
Image 39
Cisco Systems MGX-FRSM-2CT3 manual Addcon portnum mastership remoteConnId, Cnfcon portnum Cdvt CellLossIntegPeriod bufsize
Page 38 Page 40

MGX-FRSM-HS2, MGX-FRSM-2T3E3, MGX-FRSM-2CT3 specifications

Cisco Systems is a leader in networking technology and infrastructure, providing solutions that drive innovation and efficiency for businesses worldwide. Among its diverse range of products, the MGX series stands out as a pivotal component for the network-centric era, especially with models like MGX-FRSM-2CT3, MGX-FRSM-2T3E3, and MGX-FRSM-HS2. These modules are primarily designed for the MGX 8800 series routers, facilitating efficient traffic management and service delivery.

The MGX-FRSM-2CT3 is a versatile module that supports two T3 connections. It allows network operators to seamlessly integrate high-capacity circuit-switched and packet-switched data on a unified platform. This versatility is crucial for service providers looking to enhance their bandwidth offerings while ensuring reliable performance across voice, video, and data applications.

In contrast, the MGX-FRSM-2T3E3 module caters to operators needing E3 support. This feature allows for efficient data transport over a broader bandwidth, catering to European standards. The E3 configuration is vital for service providers operating in Europe or regions that utilize E3 technology prominently.

The MGX-FRSM-HS2 module is another significant offering, designed to accommodate the increasing demand for high speed and high capacity. It supports higher-order TDM and packet technologies, enabling operators to implement advanced services such as VoIP, video conferencing, and other data-intensive applications. This module provides scalability and reliability, making it ideal for next-generation networks.

All three modules leverage Cisco’s advanced switching and routing technology, ensuring optimal performance and minimal latency. The integration of Quality of Service (QoS) features allows network administrators to prioritize traffic types effectively, ensuring mission-critical applications receive the necessary bandwidth.

Additionally, these MGX modules support various signaling protocols, enabling interoperability with existing network infrastructure while also facilitating the migration to newer technologies. They play an essential role in modernizing telecom networks, allowing service providers to adapt to changing market demands and technology landscapes.

In summary, the Cisco MGX-FRSM-2CT3, MGX-FRSM-2T3E3, and MGX-FRSM-HS2 modules are key components for businesses looking to enhance their networking capabilities. With their robust support for T3 and E3 technologies, high scalability, and advanced QoS features, these modules empower service providers to deliver a wide range of services, drive innovation, and meet the growing demands of users in an increasingly connected world.
Top Page Image Contents