|
|
To enable alarms in profile command mode, use the alarms command. To disable alarms, use the no form of the command.
alarmsThis command has no keywords or arguments.
Disabled
Profile configuration
| Release | Modification |
|---|---|
12.0(5)DA | This command was introduced in a previous release. |
The command affects minor alarms for DSL subscriber ports only. The alarms this command controls apply to these event classes:
Enabling or disabling alarms affects the specified profile only. For example, if you disable alarms on the default profile, other profiles are unaffected.
Use alarms and no alarms to enable and disable minor alarms related to DSL subscriber ports. When these alarms are disabled, you receive no notification when alarm conditions exist. (Notification methods include console messages, LEDs, the output of the show facility-alarm command, and relay alarm signals to external systems for audible or visible alarms.) However, you can track the condition of DSL ports on which alarms are disabled, including conditions that ordinarily trigger alarms, using the command show dsl interface atm slot#/port#.
You can suppress minimum bitrate alarms without disabling other alarms for the profile. See cap bitrate, and dmt bitrate.
 |
Note The alarms command has no effect on critical alarms, major alarms, or minor alarms related to subsystems other than the DSL subscriber ports. |
In this example, the command enables alarms for the default profile:
DSLAM# configure terminal
DSLAM(config)# dsl-profile default
DSLAM(config-dsl-prof)# alarms
To enable the clp-drop flag for all ports, and for selected traffic types, use the atm clp-drop command.
atm clp-drop [force] {vbr-nrt | ubr} {off | on}
[force] | Change the clp-drop setting on an active interface even if the change results in loss of data. |
{vbr-nrt | ubr} | Select the appropriate traffic parameters. |
{off | on} | Select off to disable the clp-drop flag or on to enable it. |
Off
Global configuration
| Release | Modification |
|---|---|
12.0(5)DA | This command was introduced in a previous release. |
If the clp-drop flag is enabled, the software drops cells when the specified service-category queues reach 50 percent of the discard threshold limit. This reduces congestion in busy flows.
In this example, the command enables the clp-drop flag for UBR traffic:
DSLAM# configure terminal
DSLAM(config)# atm clp-drop ubr on
None
To create an entry in the traffic characteristics table, use the atm connection-traffic-table-row global configuration command. To delete an entry, use the no form of this command.
atm connection-traffic-table-row [index row-index] cbr pcr rate [cdvt cdvt-value]
Rows 1 through 6 in the table are predefined.
Global configuration
This command sets up the traffic characteristics used in PVC definition. The characteristics are stored as rows of a table. The row index is referenced when a PVC is created using the atm pvc interface command.
When you use the atm connection-traffic-table-row command without the index clause, the software uses a free row-index, which is displayed if the command is successful.
When the CDVT or MBS parameter is not specified in the creation of a row, a configurable interface default value is chosen to use in UPC.
Six connection traffic table rows are defined by default and are numbered 1 through 6. Row 1 is the default row used by the atm pvc command if no rows are explicitly specified. Rows 2 through 6 might be used for well-known VCs on a VP tunnel subinterface, depending on the service category of the underlying VP.
Default rows cannot be deleted.
Row 1 PCR represents the maximum-signalable cell-rate (the maximum cell-rate that fits in 24 bits).
When an ABR row is configured, if MCR is not specified, MCR is configured as 0 in the CTT row.
In the following example, a CBR CTT row is defined with an index of 200 and a peak cell rate of 7743 kbps.
Switch(config)# atm connection-traffic-table-row index 200 cbr pcr 7743
To change the maximum size of the input queue for each subscriber port, use the atm input-queue interface configuration command. To reset the maximum queue size to the default value, use the no form of the command.
atm input-queue [force] {cbr | vbr-rt | vbr-nrt | ubr} max-size size-num
[force] | Change the input queue size on an active interface even if the change results in the loss of data from the queue. |
{cbr | vbr-rt | vbr-nrt | ubr} | Select the appropriate traffic parameter. |
max-size size-num | Maximum input queue size per service category. Enter queue size in cells, from 8 to 262144. If you enter a value that is not a power of 2, the system rounds up or down to the nearest power of 2 and uses that value. For example, if you enter 14, the system rounds up to 16. |
The defaults vary by queue (traffic type) as shown here:
| cbr | vbr-rt | vbr-nrt | ubr |
|---|---|---|---|
1024 cells | 1024 cells | 8192 cells | 8192 cells |
Interface configuration
| Release | Modification |
|---|---|
12.0(5)DA | This command was introduced in a previous release. The range of queue sizes and the type of port affected by the command were changed for Release 12.0(5)DA. |
This command is supported only on subscriber ports.
The force argument indicates that the change should be made even if it results in the loss of data on the interface queue. (The queue must be momentarily disabled for the threshold to be changed.) This command without the force argument changes only the threshold if the interface is down. An error message appears and the command does not take effect if the interface is up and the force argument is not present.
To display both the configured and installed values of size-num, use the show atm interface resource command.
In the following example, the maximum size of the vbr-nrt input queue is set to 512 cells (the minimum number allowed). This can be set even if the interface is up.
DSLAM(config-if)# atm input-queue force vbr-nrt max-size 512
To set input queue discard threshold values for this node and for any subtended nodes subordinate to this node, use the atm input-threshold global configuration command. To reset a threshold to its default value, use the no form of the command.
atm input-threshold {cbr | vbr-rt | vbr-nrt | ubr} {epd threshold-value | drop threshold-value}
{cbr | vbr-nrt |vbr-rt | ubr} | Select the traffic priority. Threshold settings apply to all queues of a given priority. |
epd | Early packet discard threshold. The epd value plus the drop value equals the total size of the input queue. For details, see the "Usage Guidelines" section. |
drop | Drop threshold. The drop value plus the epd value equals the total size of the input queue. For details, see the "Usage Guidelines" section. |
threshold-value | Enter the allowed maximum input discard threshold, in cells, for subscriber and subtending ports for the selected traffic parameter. The range is 8 to 262144. If you enter a value that is not a power of 2, the system rounds up or down to the nearest power of 2 and uses that value. For example, if you enter 18, the system rounds down to 16. If you enter a value that falls halfway between two powers of 2, the system rounds up. For example, if you enter 12, the system rounds up to 16. |
The defaults vary by interface type and by traffic priority, as shown here:
| Interface | Queue Segment | cbr | vbr-rt | vbr-nrt | ubr |
|---|---|---|---|---|---|
DS3 | epd | 512 cells | 512 cells | 4096 cells | 4096 cells |
drop | 512 cells | 512 cells | 4096 cells | 4096 cells | |
Total queue | 1024 cells | 1024 cells | 8192 cells | 8192 cells | |
OC-3c | epd | 2048 cells | 2048 cells | 8192 cells | 8192 cells |
drop | 2048 cells | 2048 cells | 8192 cells | 8192 cells | |
Total queue | 4096 cells | 4096 cells | 16384 cells | 16384 cells |
Global configuration
| Release | Modification |
|---|---|
12.0(5)DA | This command was introduced in a previous release. |
Cisco recommends that you leave the input queue discard thresholds set to their default values, which are adequate for most configurations.
This command controls the discard threshold settings for up to 52 input queues: one queue for each of four traffic types on each of up to 13 nodes in a subtending group. The behavior of the input queues is affected not only by the input queue discard threshold settings, but also by the setting of the intelligent packet discard (PD) feature, which is controlled with the atm pvc command. The PD setting determines whether the system performs packet-based discards or cell-based discards:
The PD setting applies to all discards, whether for reasons of queue exhaustion or policing. PD is disabled by default; use the command atm pvc vpi vci pd {on | off} to enable or disable it.
The input queue discard thresholds work as follows:
If packet-based discard is in force, you can implicitly configure the input queue discard thresholds for either EPD or PPD. For EPD, configure a drop threshold value that is large enough to allow most packets to enter the queue. Appropriate values for this purpose vary by traffic type, but see the thresholds in the "Defaults" section for examples of EPD settings. For PPD, configure a small drop threshold value. This forces the system to discard the remainder of the packet that fills up the queue.
To set input queue sizes, use the atm input-queue command.
In this example, the command sets the epd threshold for CBR traffic on subscriber and subtending ports at 32,000 cells:
DSLAM# configure terminal
DSLAM(config)# atm input-threshold cbr epd 32000
To change the output queue discard thresholds for the subscriber ports, use the atm output-threshold interface configuration command. To reset a threshold to its default value, use the no form of the command.
atm output-threshold {cbr | vbr-rt | vbr-nrt | ubr} {epd threshold-value | drop threshold-value}
{cbr | vbr-rt | vbr-nrt | ubr} | Select the traffic priority. Threshold settings apply to all queues of a given priority. |
epd | Early packet discard threshold. The epd value plus the drop value equals the total size of the output queue. For details, see the "Usage Guidelines" section. |
drop | Drop threshold. The drop value plus the epd value equals the total size of the output queue. For details, see the "Usage Guidelines" section. |
threshold-value | Enter the allowed maximum output discard threshold, in cells, for subscriber ports for the selected traffic parameter. The range is 8 to 262144. If you enter a value that is not a power of 2, the system rounds up or down to the nearest power of 2 and uses that value. For example, if you enter 18, the system rounds down to 16. If you enter a value that falls half way between two powers of 2, the system rounds up. For example, if you enter 12, the system rounds up to 16. |
The defaults vary by traffic priority, as shown here:
| Queue Segment | cbr | vbr-rt | vbr-nrt | ubr |
|---|---|---|---|---|
epd | 128 cells | 128 cells | 1024 cells | 1024 cells |
drop | 128 cells | 128 cells | 1024 cells | 1024 cells |
Total queue | 256 cells | 256 cells | 2048 cells | 2048 cells |
Interface configuration
| Release | Modification |
|---|---|
12.0(5)DA | This command was introduced in a previous release. |
Cisco recommends that you leave the output queue discard thresholds set to their default values, which are adequate for most configurations.
The atm output-threshold command controls the discard threshold settings for up to 1040 output queues. The behavior of the output queue is controlled not only by the output queue discard threshold settings, but also by the setting of the intelligent packet discard (PD) feature, which is controlled with the atm pvc command.
The PD setting determines whether the system performs packet-based discards or cell-based discards:
The PD setting applies to all discards, whether the discards occur for reasons of queue exhaustion or policing. PD is disabled by default; use the command atm pvc vpi vci pd {on | off} to enable or disable it.
The output queue discard thresholds work as follows:
If packet-based discard is in force, you can implicitly configure the output queue discard thresholds for either EPD or PPD. For EPD, configure a drop threshold value that is large enough to allow most packets to enter the queue. Appropriate values for this purpose vary by traffic type, but see the thresholds in the "Defaults" section for examples of EPD settings. For PPD, configure a very small drop threshold value. This forces the system to discard the remainder of the packet that fills up the queue.
In this example, the command sets the drop threshold for VBR-NRT traffic on subscriber ports at 16,000 cells:
DSLAM# configure terminal
DSLAM(config)# interface atm0/1
DSLAM(config-if)# atm output-threshold vbr-nrt drop 16000
To create a PVC on a subscriber port, use the atm pvc interface configuration command. To create a PVCC, use the long form of the atm pvc command. To create a PVCL, use the short form of the atm pvc command. To remove the specified PVC, use the no form of this command.
atm pvc vpi-A [vci-A | any-vci] [upc upc-A] [pd pd] [rx-cttr index] [tx-cttr index] interface atm slot-B/port-B [.vpt#] vpi-B [vci-B | any-vci] [upc upc-B] [encap aal-encap] [inarp minutes] |
Note The A and B suffixes of the command arguments refer to the ends of the connection; A is the local end, B is the remote end. |
vpi | VPI of this PVC. On the ASP interface, ATM0/0, the VPI is always 0. On DSL interfaces, the VPI range is 0 to 255. The VPI is an 8-bit field in the header of the ATM cell. The VPI value is unique only on an interface, not throughout the ATM network (the VPI has local significance only). | |
vci | VCI of this PVC. The range of values varies by interface type, mode, and VPI, as shown below. The VCI is a 16-bit field in the header of the ATM cell. The VCI value is unique only on a single interface, not throughout the ATM network (it has local significance only). | |
| ASP Interface (ATM0/0) | VCI Range | |
| 0 to 4095 | |
| DSL Interfaces | VCI Range | |
In manual-well-known-vc mode Not in manual-well-known-vc mode | 32 to 255 | |
| Other Interfaces | VCI Range | |
In manual-well-known-vc mode | 5 to 16383 | |
any-vci | Selects any available VCI. This feature only applies to the ASP interface (ATM0/0). | |
upc | Usage parameter control, specified as pass, tag, or drop; the default is pass. The upc parameter can be set to tag or drop only on an ATM interface that is not the ASP port (ATM0/0) or a logical port (VP tunnel). | |
pd | Turns the intelligent packet discard option on or off. The default is off. | |
rx-cttr index | Connection traffic table row index in the received direction. Configure the connection traffic table row before using the atm pvc command. Refer to the atm connection-traffic-table-row command for information on configuring the rx-cttr parameter. The default is 1. | |
tx-cttr index | Connection traffic table row index in the transmitted direction. Configure the connection traffic table row before using the atm pvc command. Refer to the atm connection-traffic-table-row command for information on configuring the tx-cttr parameter. The default is 1. | |
slot/port | Slot and port number for the ATM interface. | |
vpt# | Specifies the virtual path tunnel number. | |
encap | AAL and encapsulation type and applies only to terminating connections. When aal5mux is specified, a protocol is required. Possible values are as follows:
| |
inarp minutes | Specifies how often Inverse ARP datagrams are sent on this virtual connection and applies only to terminating connections. The default value is 15 minutes. | |
See the Syntax Description.
Interface configuration
| Release | Modification |
|---|---|
12.0(5)DA | This command was introduced in a previous release. |
Use the atm pvc commands to create or delete the following types of ATM connections:
When you set UBR connections, the tx-cttr and rx-cttr fields are not needed. However, these fields are required when you set up a CBR, VBR, or ABR connection. Refer to the atm connection-traffic-table-row command for information on configuring in the connection traffic table specified by index.
You can create PVCs only on subscriber ports; the atm pvc command does not work on trunk or subtending ports.
The following example shows how to configure a terminating PVC between interface ATM 3/1 and the ASP port (ATM0/0).
DSLAM(config)# interface atm 0/0
DSLAM(config-if)# atm pvc 0 any-vci interface atm 3/1 0 100
The following example shows how to set up a UBR PVC connection between interface ATM 4/1 and 4/2 with a VPI of 0 and a VCI of 40.
DSLAM(config)# interface atm 4/1
DSLAM(config-if)# atm pvc 0 40 interface atm 4/2 0 40
The following example shows a display using the encap variable.
DSLAM(config-if)# atm pvc 100 200 interface atm 0/0 0 344 encap ?
aal5mux AAL5+MUX Encapsulation
aal5snap AAL5+LLC/SNAP Encapsulation
The following example shows the commands used to establish a PVC between a logical interface (VP tunnel) on ATM 4/1.99 and ATM 3/1.
DSLAM(config)# interface atm 4/1.99
DSLAM(config-subif)# atm pvc 99 100 interface atm 3/1 0 89
DSLAM(config-subif)# end
The following example shows how to use the show atm vc command to display all VCs on an interface.
DSLAM# show atm vc interface atm 0/1.51
Interface VPI VCI Type X-Interface X-VPI X-VCI Status
ATM0/1.51 51 3 PVC ATM0/0 0 75 DOWN
ATM0/1.51 51 4 PVC ATM0/0 0 76 DOWN
ATM0/1.51 51 5 PVC ATM0/0 0 74 DOWN
ATM0/1.51 51 16 PVC ATM0/0 0 73 DOWN
The following example deletes the ATM transit point-to-point PVC previously configured.
DSLAM(config-if)# interface atm 1/1
DSLAM(config-if)# no atm pvc 50 100
Posted: Wed Jul 24 12:12:33 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.