Adding Connections on a PXM in a Stand-Alone Node

Adding Connections on a PXM in a Stand-Alone Node

This section describes the CLI commands for provisioning connections on a PXM in a stand-alone node. Connection addition abides by 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. In addition this section describes the commands for modifying certain features for a connection and policing connections by way of usage parameter control.

The CLI commands correspond to functions in the Cisco WAN Manager application. The preferred CLI 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.) In addition, On the PXM CLI:

Step 1 Execute the addcon command according to the following syntax:

addcon <port_num> <conn_type> <local_VPI> <local_VCI> <service> [CAC] [mastership] [remoteConnId]

•port_no is the logical port in the range 1–32 for a user connection or 34 for management connection.

•conn_type is a number identifying the connection type—1 for VPC or 2 for VCC.

•local_VPI is the local VPI in the range 0–4095.

•local_VCI is the local VCI in the range 0–65535.

•service is a number in the range 1–4 to specify the type of service: 1=CBR, 2=VBR, 3=ABR, and 4=UBR.

•CAC optionally lets you turn off the addition of the loading affect of a connection to the aggregated load on a port.

•mastership specifies whether the endpoint you are adding is the master or slave. 1=master. 2=slave (default). The syntax shows this parameter as optional because you need to enter it at only the master end. Slave is the default, so you do not explicitly need to specify it when entering a DAX con.

•remoteConnId identifies the connection at the slave end. The format for remoteConnId is Remote_nodename.slot_num.remote_VPI.remoteVCI. Note that the slot number of the active PXM is always 0 when you add a connection because the PXM slot number is a fixed, logical value.

Step 2 If necessary, modify a connection by using cnfcon:

cnfcon <conn_ID> <route_priority> <max_cost> <restrict_trunk_type> [CAC]

•conn_ID identifies the connection. The format is logical_port.VPI.VCI.

•route_priority is the priority of the connection for re-routing. The range is 1–15 and is meaningful only in relation to the priority of other connections.

•max_cost is a number establishing the maximum cost of the connection route. The range is 1–255 and is meaningful only in relation to the cost of other connections for which you specify a maximum cost.

•restrict_trunk_type is a number that specifies the type of trunk this connection can traverse. The numbers are 1 for no restriction, 2 for terrestrial trunk only, and 3 for satellite trunk only.

•CAC optionally lets you turn on or off the addition of the loading affect of a connection to the aggregated load on a port.

Card and Service Configuration 6-9

Page 8 Page 10
Page 9
Image 9
Cisco Systems MGX-FRSM-2CT3, MGX-FRSM-HS2, MGX-FRSM-2T3E3 manual Adding Connections on a PXM in a Stand-Alone Node
Page 8 Page 10

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