> Channelized Port Configuration Mode Commands
> The channelized port configuration mode provides the commands to create, configure, bind, and manage the Frame Relay service ports on the channelized line card.
> 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).
> alarm-disable
> Entering this command disables the alarm detection for designated sets of alarms.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> alarm-disable { all | ds1-e1 | none | sonet-sdh }
> [ no | default ] alarm-disable
> no
> Deletes the disable configuration.
> default
> Returns the settings for disabling alarms to the system default.
> all
> Disables detection of all SONET/SDH and DS1/E1 alarms.
> ds1-e1
> Disables detection of the DS1/E1 alarms.
> none
> None of the alarm detection is disabled so that all DS1/E1 and SONET/SDH alarms are detected.
> sonet-sdh
> Disables detection of SONE/SDH alarms.
> Usage
> Configure selected alarm detection for the port.
> Example
> Enter the following command to enable DS1/E1 and SONET/SDH alarm detection.
> alarm-disable none
> alarm-soak-timer
> This command sets the timer for the duration that a detected alarm will be soaked before the alarm is reported.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> alarm-soak-timer seconds
> default alarm-soak-timer
> default
> Returns the timer settings to the system default.
> seconds
> Defines the number of seconds the system waits (soaks the alarm) before reporting the alarm.
> seconds: any integer from 0 to 32767.
> Usage
> Configures the delay before reporting detected alarms.
> Example
> Configure a 20 second alarm report delay.
> alarm-soak-timer 20
> clock-source
> This command sets the source of the port’s transmit clock.
> Important: This command is only available for releases 8.1 or higher.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> clock-source { internal-timing | loop-timing }
> default clock-source
> default
> Using this command combination sets the port clock source to internal timing.
> internal-timing
> Sets the port clock to derive timing from the recovered receive clock.
> loop-timing
> Sets the port clock to transmit in sync with the system timing.
> Usage
> Use this command for either SONET or SDH channelized (Frame Relay) ports on the SGSN.
> Example
> The following command resets the transmit clock source to internal timing.
> default clock-source
> 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 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”
> dlci
> Identifies a data link connection identifier (DLCI), a frame relay logical connection, and binds it with a specific channelized path configuration. Once the DLCI is bound to the path, the system enters DLCI configuration mode.
> Important: The path command must be configured prior to attempting configuration with the dlci command.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> dlci path path_id { ds1 | e1 } connects { dlci dlci_id | timeslots slot# dlci dlci_id }
> no dlci path path_id { ds1 | e1 } connects
> no
> Disables the configured DLCI.
> path path_id
> Identifies a specific path configuration, set with the path command in this configuration mode, that will be associated with a DLCI.
> path_id must be an integer from 1 to 3.
> ds1 connects | e1 connects
> Selects the framing speed for the connection.
> DS1: Is associated with North American networks and would be the best choice to work with the SONET framing selected with the card configuration command.
> connects: Defines the number of logical connections supported via the DS1. The selection must be an integer from 1 to 28.
> E1: is associated with European networks and would be associated with the SDH framing selected with the card configuration command.
> connects: Defines the number of logical connections supported via the E1. The selection must be an integer from 1 to 21.
> dlci dlci_id
> Identifies a specific Frame Relay PVC DLCI to associate with the path.
> dlci_id: an integer from 16 to 991.
> timeslot slot#
> Identifies one of the timeslots within a timeslot group configured with the path command for the E1, DS1 or fractional E1 port. Identifying one slot in a group means that all the slots in that group will have the Frame Relay parameters configured in the same manner.
> slot#: Must be an integer from 1 to 31.
> Usage
> Associating a routing path with a specific frame relay DLCI is a significant part of the process for defining the frame relay interface.
> Example
> Associate path 1 with DLCI 123.
> dlci path 1 ds1 21 dlci 123
> end
> Exits the Channelized 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 Channelized 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.
> frame-relay
> Configures the parameters for the Frame Relay connections for E1, DS1 and fractional E1 ports created with the path command. Frame
> Important: The path command must be configured prior to attempting configuration with the frame-relay command.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> frame-relay path path_id { ds1 connects | e1 connects } timeslot slot# [ intf-type intf_type ] [ lmi_type lmi_type ]
> path path_id
> Identifies a specific path configuration, set with the path command in this configuration model.
> path_id must be an integer from 1 to 3.
> ds1 connects | e1 connects
> Selects the pipe splitting for the connection.
> DS1: Is associated with North American networks and would be the best choice to work with the SONET framing selected with the card configuration command. DS1 splits the path into 28 logical connections.
> connects: Defines the number of logical connections supported via the DS1. The selection must be an integer from 1 to 28.
> E1: is associated with European networks and would be associated with the SDH framing selected with the card configuration command. E1 splits the path into 21 logical connections.
> connects: Defines the number of logical connections supported via the E1. The selection must be an integer from 1 to 21.
> timeslot slot#
> Identifies one of the timeslots within a timeslot group configured with the path command for the E1, DS1 or fractional E1 port. Identifying one slot in a group means that all the slots in that group will have the Frame Relay parameters configured in the same manner.
> slot#: Must be an integer from 1 to 31.
> intf-type intf_type
> Selecting the interface type specifies signaling parameters for the DLCI, options include:

> • | dce: Selects data circuit-terminating equipment -type signaling.

> • | dte: Selects data terminal equipment -type signaling.

> • | nni: Selects the network-to-network interface

> Default: DTE for Release 8.0
> Default: DCE for Release 8.1
> frame-relay lmi_type lmi_type
> Default: none.
> Line management options include:

> • | ansi - ANSI ANNEXED LMI, may include option:

> • | cisco - Cisco/Gang Of Four LMI

> • | none - LMI Disabled

> • | q933a - Q.933A LMI

> Any of the above LMI types can take one or more additional options

> • | n391 value - Number of keep exchanges before requesting a full status message. Default is 6. value must be an integer from 1 to 255.

> • | n392 value - Error Threshold value. Default is 2. value must be an integer from 1 to 10.

> • | n393 value - Monitored events count value. Default is 2. value must be an integer from 1 to 10.

> • | t391 value - Timer to send messages. Default is 10. value must be an integer from 5 to 30.

> • | t392 value - Polling verification timer value. Default is 15. value must be an integer from 5 to 30.

> Usage
> Use this command to define LMI type and timers and to associate time group 2 with the Frame Relay connection.
> Example
> frame-relay path 1e1 3 timeslot 2
> hopath-sdsf
> Configures the high-order path for degrade/signal failure (SDSF) bit error rate (BER) thresholds.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> hopath-sdsf hopath_value
> hopath_value

> • | 0: Disabled

> • | 1 -1.E-03

> • | 2 - 1.E-04

> • | 3 - 1.E-05

> • | 4 - 1.E-06

> • | 5 - 1.E-07

> • | 6 - 1.E-08

> • | 7 - 1.E-09

> • | 8 - 1.E-10

> Usage
> Sets a standard option for the high-order path for SDSF.
> The SD is kept at a value of 100 erroredBits/sec less than the corresponding value of the SF. So if the SD threshold is configured at 1 error in every 100000 bits/sec, then the SF threshold automatically becomes 1 error in every 1000 bits/sec.
> Example
> hopath-sdsf 1
> 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 (with the no shutdown command ) 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
> loopback
> Configures the type of loopback mode used for diagnostic testing.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> loopback { ds1-e1-diag | ds1-e1-line | none | sonet-sdh-diag | sonet-sdh-line }
> ds1-e1-diag
> Enables a system generated diagnostic lookback signal at the DS1/E1 layer.
> ds1-e1-line
> Loops back a network diagnostic signal at the DS1/E1 layer.
> none
> Stops diagnostic loopback signalling.
> sonet-sdh-diag
> Enables a system generated diagnostic lookback signal at the SONET/SDH layer.
> sonet-sdh-line
> Loops back a network diagnostic signal at the SONET/SDH layer.
> Usage
> Setup diagnostic loopback signals for troubleshooting purposes.
> Example
> loopback ds1-e1-diag
> lopath-sdsf
> Configures the low-order path for signal degrade/signal failure (SDSF) bit error rate (BER) thresholds.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> lopath-sdsf lopath_value
> lopath_value

> • | 0: Disabled

> • | 1 -1.E-03

> • | 10 - 1.E-12

> • | 2 - 1.E-04

> • | 3 - 1.E-05

> • | 4 - 1.E-06

> • | 5 - 1.E-07

> • | 6 - 1.E-08

> • | 7 - 1.E-09

> • | 8 - 1.E-10

> • | 9 - 1.E-11

> Usage
> Sets a standard option for the low-order path for SDSF.
> The SD is kept at a value of 100 erroredBits/sec less than the corresponding value of the SF. So if the SD threshold is configured at 1 error in every 100000 bits/sec, then the SF threshold automatically becomes 1 error in every 1000 bits/sec.
> Example
> lopath-sdsf 1
> path
> This command configures the parameters that define the routing path for a DLCI. It must match with the DLCI configuration parameters. The values entered with these commands should be noted as they will be needed to configure the frame-relay and dlci commands also in this configuration mode.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> path path_id { ds1 connects | e1 connects } frame-mapping multiplexing index# index# framing mode mapping-mode { bit-sync | byte-sync } [ timeslots slot# [ slot# ] | frame-relay [ intf-type intf_type [ lmi_type lmi_type ] ] ]
> no path path_id { ds1 | e1 }connects
> no
> Deletes the routing path entry from the configuration.
> path path_id
> Identifies a specific path configuration that will be associated with a DLCI. The path_id must be an integer from 1 to 3.
> ds1 connects | e1 connects
> Selects the channelization for the connection.
> DS1: (AKA: T1) Is associated with North American networks and would be the best choice to work with the SONET (can also work with SDH) framing selected with the card configuration command. DS1 splits the path into 28 logical connections.
> connects: Defines the number of logical connections supported via the DS1. The selection must be an integer from 1 to 28.
> E1: is associated with European networks and would be associated with the SDH (can also work with SONET) framing selected with the card configuration command. E1 splits the path into 21 logical connections.
> connects: Defines the number of logical connections supported via the E1. The selection must be an integer from 1 to 21.
> frame-mapping
> Frame mapping sets the channelization according to the national standards that correlate with the framing/speed standards. This option selects the mapping of containers (C), virtual containers (VC), tributary units (TU), and tributary unit groups (TUG), that is appropriate for the channel characteristics:

> • | tu11-au3: Appropriate for DS1 in SDH. Maps as follows AU-3—VC-3— m# —TUG-2— m# —TU-12—VC-12—C-12

> • | tu11-au4: Appropriate for DS1 in SDH. Maps as follows AU-4—VC-4—TUG-3— m# —TUG-2— m# —TU-11—VC-11—C-11

> • | tu12-au3: Appropriate for E1 in SDH. Maps as follows AU-3—VC-3— m# —TUG-2— m# —TU-12—VC-12—C-12

> • | tu12-au4: Appropriate for E1 in SDH. Maps as follows AU-4—VC-4—TUG-3— m# —TUG-2— m# —TU-12—VC-12—C-12

> • | vt1.5: Only appropriate for DS1 in SONET framing.

> • | vt2: Only appropriate for E1 in SONET framing.

> multiplexing index# index#
> index#: TUG-2 index - Must be an integer from 1 to 7 to identify a multiplex channel between TUG-2 and VC-3 (E1) or TUG-3 (DS1).
> index#: TU index - Must be an integer from 1 to 4 (DS1) or 1 to 3 (E1) to identify a multiplex channel between TU-11 (DS1) and TUG-2 or between TU-12 (E1) and TUG-2.
> framing mode
> Defines the framing modes to be used for the channelization to E1 or T1 of the (optical) port.

> • | options for E1:

> • | cas: standard mapping with CAS

> • | cas-crc4: CRC4 mapping with CAS

> • | crc4: CRC4 mapping

> • | standard: mapping

> • | options for DS1:

> • | esf: extended superframe mapping

> • | sf: superframe mapping

> • | option for either E1 or DS1:

> • | unframed

> mapping-mode

> • | bit-sync

> • | byte-sync

> timeslots timeslots
> Defines up to 8 timeslot groupings for multiple fractional DS1/E1 channels. Each slot is 2.048/32 Mbytes. Slots 0 and 16 are reserved for synchronization and alarms. Slots 1-15 and 17-31 are used for data. Timeslots must be unique -- a timeslot can not be used in more than one grouping.
> timeslots: Must be an integer from 1 to 31. Timeslot groups are separated by spaces and can consist of a single slot and/or a range indicated with a hyphen. Example: 3,7-10 is a single fractional group. NOTE there is no space after the comma. Timeslots must be unique -- a timeslot can not be used in more than one grouping.
> frame-relay
> Enables definition of a Frame Relay connection with the frame-relay command.
> Important: For release 8.1 and higher, this feature has been moved to the frame-relay command.
> intf-type intf_type
> Selecting the interface type specifies signaling parameters for the DLCI, options include:

> • | dce: Selects data circuit-terminating equipment -type signaling.

> • | dte: Selects data terminal equipment -type signaling.

> • | nni: Selects the network-to-network interface

> Default: DTE for Release 8.0
> Default: DCE for Release 8.1
> Important: For release 8.1 and higher, this feature has been moved to the frame-relay command.
> lmi_type lmi_type
> Default: none.
> Line management type options include:

> • | ansi - ANSI ANNEXED LMI, may include option:

> • | cisco - Cisco/Gang Of Four LMI

> • | none - LMI Disabled

> • | q933a - Q.933A LMI

> Any of the above LMI types can take one or more additional options

> • | n391 value - Number of keep exchanges before requesting a full status message. Default is 6. value must be an integer from 1 to 255.

> • | n392 value - Error Threshold value. Default is 2. value must be an integer from 1 to 10.

> • | n393 value - Monitored events count value. Default is 2. value must be an integer from 1 to 10.

> • | t391 value - Timer to send messages. Default is 10. value must be an integer from 5 to 30.

> • | t392 value - Polling verification timer value. Default is 15. value must be an integer from 5 to 30.

> Important: For release 8.1 and higher, this feature has been moved to the frame-relay command.
> Usage
> Defines the signaling characteristics of a frame relay connection or timeslots for a fractional connection.
> Use this command to create E1 ports or fractional E1 ports. Fractional E1 ports are created with the timeslot definitions. The fractional E1 port can consist of one or more or all of the timeslots.
> Example
> In the first example, define timers for the q933a LMI-type.
> path 1 e1 1 tu12-au4 1 1 framing crc4 mapping-mode bit-async frame-relay intf-type dce lmi_type q933a n391 6 n392 2 n393 2 t391 10 t392 15
> The next example defines 3 groups of fractional timeslots with group 1 having slots 1-5 and 8, group 2 having slot 22-25, and group 3 having slots 31.
> path 1 e1 1 tu12-au3 1 1 framing cas mapping-mode bit-async timeslots 1-5,8 22-25 31
> 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#
> no preferred slot
> slot#
> Identifies the physical slot in the chassis where the line card is installed.
> no
> Disables revertive, or auto-recovery, operation for the port.
> 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
> pwe3-cesopsn
> This command has been deprecated and replaced by the mtp2 command.
> 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
> [ 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
> Use the following command to disable a port:
> shutdown
> Use the following command to enable a port for service:
> 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
> All
> Privilege
> Security Administrator, Administrator
> Syntax
> [ 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
> 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
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> [ 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 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.
> Example
> Use the following command to terminate thresholding:
> no threshold monitoring
> threshold rx-utilization
> Configures thresholds for receive-port utilization.
> Product
> SGSN
> 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
> Default: 80
> Allows the configuration of the low threshold.
> 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
> SGSN
> 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
> Default: 80
> Allows the configuration of the low threshold.
> 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
> toh-sdsf
> Enable/disable line SDSF BER thresholds and configure the line transport overhead (TOH) signal degrade and signal failure (SDSF) bit error rate (BER) threshold.
> Product
> SGSN
> Privilege
> Security Administrator, Administrator
> Syntax
> toh-sdsf toh_value
> default toh-sdsf
> default
> Resets the default which disables this threshold.
> toh_value
> To facilitate configuration the SD and SF rates have been combined into a single setting. .

> • | 0: Disabled

> • | 1 -1.E-04

> • | 2 - 1.E-05

> • | 3 - 1.E-06

> • | 4 - 1.E-07

> • | 5 - 1.E-08

> • | 6 - 1.E-09

> • | 7 - 1.E-10

> • | 8 - 1.E-11

> Usage
> This command can be used to configure the line threshold whether the port is active or standby and sets a standard option for the paired values of the line’s signal degrade and signal failure (SDSF) BER.
> The SD is kept at a value of 100 erroredBits/sec less than the corresponding value of the SF. So if the SD threshold is configured at 1 error in every 100000 bits/sec, then the SF threshold automatically becomes 1 error in every 1000 bits/sec.
> The port will go operationally down as soon as the SD threshold is crossed.
> Example
> toh-sdsf 1
> vc-mapping
> This command has been deprecated. Go to the frame-mapping keyword in the path command to configure this functionality.

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