Configuring Service on an Eight-Port CESM

Adding and Modifying Connections

Use either the Cisco WAN Manager application or the CLI to add or modify connections. If you use the WAN Manager application, refer to the Cisco WAN Manager Operations Guide.

This section describes how to add a connection to a PXM in a stand-alone node according to the rules for a standard connection or a management connection in the form of either a three-segment connection or a DAX con. See “Rules for Adding Connections” earlier in this chapter. The preferred 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 through the preferred command 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 maximum number of connections for the MGX-CESM-8T1 is 248 and 192 for the MGX-CESM-8E1. Note that, because you can add only one connection per port, addcon does not request a connection number.

The system automatically assigns the next available channel number, so the addcon command does not require it. However, some related commands require a channel number. To see the channel number after you add a connection, use dspcons.

The syntax for addcon is:

addcon <port_num> <sig_type> <partial_fill> <cond_data> <cond_signalling> [controller_type] [mastership] [remoteConnId]

•port_num is the logical port number. This port must already exist (see addport).

•sig_type is a number indicating the type of signaling: 1 specifies basic signaling,

2 specifies E1 CAS, 3 specifies ds1SFCAS (DS1 Superframe CAS), and 4 specifies ds1ESFCAS (DS1 Extended Superframe CAS).

•partial_fill is a number representing the number of bytes in a cell. It can be either 0 to specify that the cell must contain 48 bytes or a non-0 value that fixes the number of bytes in each cell. For structured E1, the partial_fill range is 20–47 bytes. For structured T1, the range is 25–47 bytes. Unstructured T1 or E1 can be 33–47 bytes.

•cond_data is the conditioning data in case of loss of signal (LOS). It is always 255 for unstructured data transfer or 0–255 for structured data transfer. For a voice connection, the larger the cond_data value, the louder the hiss heard in case of LOS.

•cond_signalling is the string of condition signaling bits that you specify with a decimal number in the range 0–15, where, for example, 15=1111, and 0=0000. These bits represent the ABCD signaling to the line or network when an underflow occurs.

•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.

Card and Service Configuration 6-45

Page 44 Page 46
Page 45
Image 45
Cisco Systems MGX-FRSM-2CT3, MGX-FRSM-HS2, MGX-FRSM-2T3E3 manual Adding and Modifying Connections
Page 44 Page 46

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