> ATM Port Configuration Mode Commands
> The Asynchronous Transfer Mode (ATM) port configuration mode provides the commands to create, configure, bind, and manage the ATM ports on line cards that support ATM, such as the ATM/POS OC-3 single-mode and multi-mode optical line cards.
> Important: Before using these commands, card framing should be configured for either SDH or SONET with the framing command described in the Card Configuration Mode chapter.
> Important: The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
> default
> Restores the port’s default speed and communication mode.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> default { preferred slot | threshold { threshold_type } }
> preferred slot
> Sets the port for non-revertive operation for port redundancy auto-recovery; requiring an administrative user to manually issue a port switch to command to return service to the original port.
> threshold { threshold_type}
> Restores the system defaults for the selected threshold. The possible threshold types are:

> • | high-activity : High port activity threshold settings

> • | monitoring : Threshold monitoring configuration settings

> • | rx-utilization : Receive port utilization threshold settings

> • | tx-utilization : Transmit port utilization threshold settings

> Usage
> Restores port-level parameters to their default values.
> Example
> default preferred slot
> description
> Defines descriptive text that provides useful information about the port.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> description text
> no description
> no
> Erases the port’s defined description from the configuration file.
> text
> text must be a string of 1 to 79 alphanumeric characters with no spaces or a string within double quotes that includes printable characters. The description is case-sensitive.
> Usage
> Set the description to provide helpful information, for example the port’s primary function, services, end users. Define any information, the only limit is the number of characters.
> Example
> description samplePortDescriptiveText
> description “This is a sample description”
> end
> Exits the ATM Port configuration mode and returns to the Exec mode.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> end
> Usage
> Change the mode back to the Exec mode.
> exit
> Exits the ATM Port configuration mode and returns to the global configuration mode.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> exit
> Usage
> Return to the Global configuration mode.
> line-timing
> This command enables the SPIO to recover transmit timing source via line attached to the selected port. By default, line-timing is not enabled.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] line-timing
> no
> Disables line-timing as the source for the transmit clock.
> Usage
> The port must be enabled (no shutdown) to enable recovery of timing source via the line. As well, the card’s slot number must be entered in the recover line# command of the BITS port configuration mode.
> Example
> Disable timing clock recovery on this port.
> no line-timing
> preferred slot
> Identifies which card in a chassis should assume revertive (redundancy auto-recovery) functionality should the slot/port being configured go down. This command must be issued on a per port basis, allowing you to configure specific ports to be used on individual LCs or SPIO cards. For example, ports 1 through 4 could be configured as “preferred” on the LC in slot 17 while ports 5 through 8 are “preferred” on the LC in slot 33. In this scenario, both LCs would be in an Active operational state while still providing LC and port redundancy for the other.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> preferred slot slot#
> [ default | no ] preferred slot
> default
> Default: non-revertive operation.
> no
> Disables revertive, or auto-recovery, operation for the port.
> slot#
> Identifies the physical slot in the chassis where the preferred line card is installed.
> Usage
> This command enables or disables revertive port redundancy. So after a port failover, when the original port is restored to service (i.e. link up) the system will return service to that port automatically.
> Disabled, which is the default setting, causes non-revertive operation; requiring an administrative user to manually issue a port switch to command to return service to the original port.
> Example
> preferred slot 17
> pvc
> This command creates a Permanent Virtual Connection (PVC), including the definition of the associated Virtual Path Identifiers (VPI) and Virtual Connection Identifiers (VCI) for the PVC. By defining a PVC, this command enters into PVC configuration mode. The ATM port supports a maximum of 256 PVC definitions.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ no ] pvc vpi vpi# vci vci#
> no
> Deletes the PVC’s entry from the configuration.
> vpi vpi#
> VPI identifies a unique path to a destination point in the ATM portion of the network. The VPI and the VCI combine to create the PVC between the MS and the destination point. vpi# must be an integer, 0 to 255.
> vci vci#
> VCI identifies a unique virtual circuit within the associated VPI. vci# must be an integer, 0 to 65535.
> Usage
> Creates a virtual circuit between two specific points that the carrier will use repeatedly.
> Example
> Define a PVC with VPI 2 and VCI 353.
> pvc vpi 2 vci 353
> shutdown
> Terminates all processes supporting the port or blocks the shutting down of the port. Conversely, this command with the no keyword enables the port.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> shutdown
> no shutdown
> no
> Enables the port’s administrative state. When omitted the card is shutdown (removed from service).
> Usage
> Shut down a port prior to re-cabling and/or other maintenance activities.
> This command with the no keyword is required to bring a port into service.
> Example
> shutdown
> no shutdown
> snmp trap link-status
> Enables/disables the generation and sending of an SNMP (notification) trap when the port experiences a change of state (up or down).
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> snmp trap link-status
> no snmp trap link-status
> no
> Disables the sending of traps for link-status changes.
> Usage
> Enable the sending of link-status change traps if there is a monitoring facility that can use the information or if there are troubleshooting activities in progress.
> Example
> snmp trap link-status
> no snmp trap link-status
> threshold high-activity
> Configures the port’s high and low activity thresholds.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> threshold high-activity high_thresh [ clear low_thresh]
> high_thresh
> Default: 50
> Sets the threshold for the highest percentage of port activity that must be met or exceeded, within the polling interval, to generate an alert or alarm.
> high_thresh_% can be configured to any integer value between 0 and 100.
> clear low_thresh
> Default: 50
> Sets the threshold for the lowest percentage level of port activity that must be met to generate and send a clear alarm. If port activity does not drop to or below this threshold then the alarm is maintained.
> low_thresh_% can be configured to any integer value between 0 and 100.
> Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
> Usage
> High port activity thresholds generate alerts or alarms based on the utilization percentage of each configured port during the specified polling interval. This threshold is configured on a per-port basis.
> Alerts or alarms are triggered for high port activity based on the following rules:

> • | Enter condition: Actual percent utilization of a port ³ High Threshold

> • | Clear condition: Actual percent utilization of a port < Low Threshold

> If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
> Refer to the threshold poll command in the Global Configuration Mode Commands chapter of this reference to configure the polling interval and the threshold monitoring command in this chapter to enable thresholding for this value.
> Example
> The following command configures a high port utilization threshold percent of 70 and a low threshold of 50 for an system using the Alarm thresholding model:
> threshold high-activity 70 clear 50
> threshold monitoring
> Enables thresholding for port-level values.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> threshold monitoring
> no threshold monitoring
> no
> Disables threshold monitoring for port-level values. This is the default setting.
> Usage
> Thresholding on the system is used to monitor the system for conditions that could potentially cause errors or outage. Typically, these conditions are temporary (i.e high-activity) and are quickly resolved. However, continuous or large numbers of these error conditions within a specific time interval may be indicative of larger, more severe issues. The purpose of thresholding is to help identify potentially severe conditions so that immediate action can be taken to minimize and/or avoid system downtime.
> Thresholding reports conditions using one of the following mechanisms:

> • | SNMP traps: SNMP traps have been created that indicate the condition (high threshold crossing and/or clear) of each of the monitored values. Complete descriptions and other information pertaining to these traps is located in the starentMIB(8164).starentTraps(2) section of the SNMP MIB Reference.

> The generation of specific traps can be enabled or disabled on the system allowing you to view only those traps that are most important to you.

> • | Logs: The system provides a facility called threshold for which active and event logs can be generated. As with other system facilities, logs are generated Log messages pertaining to the condition of a monitored value are generated with a severity level of WARNING.

> • | Alarm System: High threshold alarms generated within the specified polling interval are considered “outstanding” until a the condition no longer exists and/or a condition clear alarm is generated.

> “Outstanding” alarms are reported to through the system’s alarm subsystem and are viewable through the system’s CLI.
> The following table indicates the reporting mechanisms supported by each of the above models.
> Thresholding Reporting Mechanisms by Model

> Model | SNMP Traps | Logs | Alarm System
> Alert | X | X |
> Alarm | X | X | X

> ‌
> This command enables thresholding for port-level values. Refer to the sections covering threshold high-activity, threshold rx-utilization, and threshold tx-utilization commands in this chapter for information on configuring these values. In addition, refer to the threshold poll command in the Global Configuration Mode Commands chapter of this reference for information on configuring the polling interval over which these values are monitored.
> threshold rx-utilization
> Configures thresholds for receive-port utilization.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> threshold rx-utilization high_thresh [ clear low_thresh ]
> high_thresh
> Default: 80
> The high threshold receive port utilization percentage that must be met or exceeded within the polling interval to generate an alert or alarm.
> The percentage can be configured to any integer value between 0 and 100.
> clear low_thresh
> Allows the configuration of the low threshold.
> Default: 80
> The low threshold receive port utilization percentage that maintains a previously generated alarm condition. If the utilization percentage falls below the low threshold within the polling interval, a clear alarm will be generated.
> The percentage can be configured to any integer value between 0 and 100.
> Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
> Usage
> Receive port utilization thresholds generate alerts or alarms based on the utilization percentage of each configured port in relation to data received during the specified polling interval. This threshold is configured on a per-port basis.
> Important: Ports configured for half-duplex do not differentiate between data received and data transmitted. Therefore, to avoid redundant alarms, it is recommended that only the receive or transmit utilization threshold be configured.
> Alerts or alarms are triggered for receive port utilization based on the following rules:

> • | Enter condition: Actual percent utilization of a port for received data ³ High Threshold

> • | Clear condition: Actual percent utilization of a port for received data < Low Threshold

> If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
> Refer to the threshold poll command in the Global Configuration Mode Commands chapter of this reference to configure the polling interval and the threshold monitoring command in this chapter to enable thresholding for this value.
> Example
> The following command configures a receive port high utilization threshold percent of 70 and a low threshold of 50 for an system using the Alarm thresholding model:
> threshold rx-utilization 70 clear 50
> threshold tx-utilization
> Configures thresholds for transmit port utilization.
> Product
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> threshold tx-utilization high_thresh [ clear low_thresh ]
> high_thresh
> Default: 80
> The high threshold transmit port utilization percentage that must be met or exceeded within the polling interval to generate an alert or alarm.
> The percentage can be configured to any integer value between 0 and 100.
> clear low_thresh
> Allows the configuration of the low threshold.
> Default: 80
> The low threshold transmit port utilization percentage that maintains a previously generated alarm condition. If the utilization percentage falls below the low threshold within the polling interval, a clear alarm will be generated.
> The percentage can be configured to any integer value between 0 and 100.
> Important: This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
> Usage
> Transmit port utilization thresholds generate alerts or alarms based on the utilization percentage of each configured port in relation to data transmitted during the specified polling interval. This threshold is configured on a per-port basis.
> Important: Ports configured for half-duplex do not differentiate between data received and data transmitted. Therefore, to avoid redundant alarms, it is recommended that only the receive or transmit utilization threshold be configured.
> Alerts or alarms are triggered for transmit port utilization based on the following rules:

> • | Enter condition: Actual percent utilization of a port for transmit data ³ High Threshold

> • | Clear condition: Actual percent utilization of a port for transmit data < Low Threshold

> If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
> Refer to the threshold poll command in the Global Configuration Mode Commands chapter of this reference to configure the polling interval and the threshold monitoring command in this chapter to enable thresholding for this value.
> Example
> The following command configures a transmit port high utilization threshold percent of 70 and a low threshold of 50 for an system using the Alarm thresholding model:
> threshold tx-utilization 70 clear 50

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883