|
|
The commands shown in this chapter apply to the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. Where an entire command or certain attributes of a command have values specific to a particular switch or switch router, an exception is indicated by the following callouts:
Refer to Appendix D of this command reference for a detailed list of commands that have been removed, changed or replaced.
To select efci marking, relative-rate marking, or both, use the atm abr-mode global configuration command on ABR connections. To assign the default value to ABR mode, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
This configuration command changes the global type of notification used on ABR connections to send a congestion alert to the end stations. This change can be made if the switch connects to a network or end station that uses the new technique. The use of all causes both efci and relative-rate marking to be used.
Examples
In the following example, the ABR mode of the switch is set to efci.
Related Commands
To subscribe an interface or subinterface to an existing ATM address pattern-matching filter expression, use the atm access-group interface configuration command. To delete an address access filter subscription on a specified interface of subinterface, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command affects ATM signalling SETUP requests received or transmitted by the switch on an interface.
You should use the atm filter-set command prior to using this command. For descriptions of filter sets and expressions, see the atm filter-expr, and atm filter-set global configuration commands.
Each interface has only one access group. If you create a new access group, it overrides any existing group.
Examples
The following is sample output from the atm access-group command.
Related Commands
|
To enable ATM accounting on a specific interface, use the atm accounting interface configuration command. To disable ATM accounting on a specific interface, use the no form of the command.
Syntax Description
This command has no keywords or arguments.
Defaults
Command Modes
Command History
Usage Guidelines
When accounting is disabled for an interface, accounting stops keeping track of the VCs on that interface and treats the interface as if it were shut down. For the VCs that satisfy the selection criteria, accounting writes records to the active file; however, the VCs are not affected.
Use the show atm accounting EXEC command to determine which interfaces are using ATM accounting.
Examples
The following example shows how to enable ATM accounting on interface ATM 1/0/0.
Related Commands
To control collection of ATM accounting data into a specific file, use the atm accounting collection EXEC command.
Syntax Description
|
Command Modes
Command History
Usage Guidelines
Use the collect-now option to return a message with the number of records that were written.
Use the swap option to return a message with the number of records that were written.
Use the show atm accounting EXEC command to show the active and ready file sizes and the number of records.
Examples
The following example shows how to perform an on-demand collection to the file acctng_file1.
The following example shows how to perform a swap operation on the file acctng_file1.
 |
Note The only filename currently allowed is acctng_file1. |
Related Commands
|
To enable the ATM VC accounting feature globally, use the atm accounting enable global configuration command. To disable this feature, use the no form of this command.
Syntax Description
This command has no keywords or arguments.
Defaults
Command Modes
Command History
Usage Guidelines
Accounting is enabled globally for the switch on interfaces where accounting is configured. An error message is given if memory is fragmented and ATM accounting cannot get two memory chunks of
5 MB each. The switch needs 32 MB of memory or it returns an error message.
The switch must have this command saved in the NVRAM configuration file. Use the following steps to enable ATM accounting:
Step 2 Exit global configuration mode.
Step 3 Use the copy running-config startup-config command to save the command in NVRAM.
Step 4 Reboot the switch.
Examples
The following example shows how to enable ATM accounting.
Related Commands
To enable an ATM accounting file and enter the accounting file configuration mode, use the atm accounting file global configuration command. To disable an ATM accounting file, use the no form of this command.
|
Note The atm accounting file global configuration command changes the configuration mode to ATM accounting, and the new prompt appears: Switch(config-acct-file)# |
To modify the fields in the ATM accounting file, use the following ATM accounting mode configuration subcommands. To set the fields to their default values, use the no form of these subcommands.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
The ATM accounting configuration mode subcommands are described in Table 2-1.
Table 2-1 ATM Accounting Configuration Mode Subcommands
|
To change the fields, you can either provide new values, or use the no form of the command.
Changes made to the list affect the file format. The change takes effect only for the next collection, for example, after using the atm accounting collection swap global configuration command. Changes to the connection types take effect immediately.
The ATM selection table is created using the default value of one. You can only modify the following fields in the file:
Examples
The following example shows how to enter the ATM accounting file configuration mode.
The following example shows how to enter the ATM accounting file configuration mode and configure a description that is displayed in the header of the file when using the show atm accounting command.
The following example shows how to enter the ATM accounting file configuration mode and configure failed-attempts to record failed attempts for SVC/SVP connections in the accounting file.
The following example shows how to enter the ATM accounting file configuration mode and configure remote-log.
Related Commands
|
To enable ATM accounting selection and enter the ATM accounting selection configuration mode, use the atm accounting selection global configuration command. To disable ATM accounting selection, use the no form of this command.
|
Note The atm accounting selection global configuration command changes the configuration mode to ATM accounting selection mode, and the following new prompt appears: Switch(config-acct-sel)# |
To configure the ATM accounting selection, use the following ATM accounting configuration mode subcommands. To set the selection parameters to their defaults, use the no form of these commands.
Syntax Description
Defaults
No default selection index. See the individual subcommand defaults.
Command Modes
Command History
Usage Guidelines
This release supports only one ATM selection table entry which cannot be deleted.
Examples
The following example specifies the ATM accounting selection index as 1 and restores the
default connection types.
Related Commands
|
To configure the threshold value which controls the generation of an ATM accounting SNMP trap, use the atm accounting trap threshold global configuration command. To restore the default value of the trap threshold, use the no form of the command.
Syntax Description
Defaults
The default value for the trap threshold is 90.
Command Modes
Command History
Usage Guidelines
To see the file size, threshold value, and trap statistics, use the show atm accounting EXEC command.
Examples
The following example changes the ATM accounting trap threshold to 80.
Related Commands
To assign a 20-byte ATM address to the switch, use the atm address global configuration command. To delete a specific ATM address, use the no form of this command.
Syntax Description
|
Defaults
When no atm address has been configured, an autoconfigured ATM address is assigned. Refer to the ATM Switch Router Software Configuration Guide for more information.
Command Modes
Command History
Usage Guidelines
You can have multiple ATM addresses. The first address in the list is the active ATM address for this switch router. When you delete the current active ATM address, the next address in the list becomes the active ATM address.
In autoconfiguration mode, the switch router establishes an address according to the format specified in the ATM Switch Router Software Configuration Guide.
The first 13-byte prefixes of all of the addresses are used by ILMI to assign addresses to end stations connected to the UNI ports (unless there is a prefix assigned per port). PNNI also summarizes all of the address prefixes automatically in reachable address advertisements. Refer to the auto-summary command for more information.
The active ATM address determines which address is advertised by PNNI as the ATM address of the PNNI local-nodes. Each local-node uses the active ATM address with the selector byte modified to match the local-node index.
In addition, the active ATM address is used as the source prefix for generating the PNNI peer group IDs and node IDs. However, the peer group IDs and node IDs are only updated after the local-node is disabled and reenabled. Therefore, it is recommended that a change to the active ATM address should be followed by a disable and enable of PNNI local-node 1, which will also update the identifiers for all higher local-nodes.
For two switches to belong to the same PNNI peer group, they need to have the same peer group identifier. Peer group identifiers must be prefixes of private ATM addresses, which means the organization that administers the peer group has assignment authority over that prefix. For more information, refer to the ATM Switch Router Software Configuration Guide.
In autoconfiguration mode, all switche routers have the same peer group identifier based on the first seven bytes of the autoconfigured ATM address.
The first 13-byte prefix of the active address is also used to automatically generate ATM addresses for each ATM interface that can be used for soft PVCs and PVPs to identify the destination ATM interface.
Examples
The following example shows how to assign a 20-byte ATM address to the switch.
The following example shows how to change the active ATM address for the switch and to update the PNNI local-node identifiers based on the new active ATM address prefix.
Step 2 Determine the current active ATM address by using the show atm addresses command. Then remove the current active ATM address, so that the desired new address will be the first in the list. If desired, the removed ATM address(es) can then be readded to appear later in the list.
Step 3 (Optional) Update all PNNI local-node identifiers by disabling and reenabling local-node 1.
Step 4 (Optional) Save the running configuration to be used as the startup configuration in the event of a reboot.
Related Commands
|
To enable the switch to engage in address registration on an interface using the ILMI protocol,
and to enable the optional per-interface access filters on ILMI address registration, use the
atm address-registration interface configuration command. To disable ILMI address registration functions on an interface, use the no form of this command.
Syntax Description
|
Defaults
ILMI address registration is enabled by default. If no optional keywords are configured, the global default access filter for ILMI address registration is used, as specified through the atm ilmi default-access permit global configuration command.
Command Modes
Command History
Usage Guidelines
The atm address-registration command does not apply to the ATM 0 interface.
The atm address-registration command enables a switch to participate in ILMI address registration. When the switch is on the network side of a UNI, the switch sets one or more network prefixes on the peer IME and accepts addresses registered by the peer IME. If the interface does not come up as a UNI, then ILMI address registration is not active, even if it was previously configured to be enabled.
The optional keywords allow configuration of per-interface access filters, in order to allow or deny certain ILMI registered addresses. If specified, the per-interface access filter overrides the global default access filter for ILMI address registration.
|
Note If the Cisco SSRP for LAN Emulation is used in this network, ILMI registration of well-known group addresses should be permitted. The SSRP allows the active LECS to register the well-known LECS address with the switch router. Either the permit all, permit matching-prefix wellknown-groups, or permit matching-prefix all-groups option should be configured. |
In order to allow certain addresses to be registered via ILMI, while also restricting them from being advertised through PNNI, the PNNI suppressed summary address feature should be used instead of the access filters for ILMI address registration (see the summary-address command for additional information).
The access filters option of this command allows configuration of per-interface access filters for ILMI registration to override the global defaults of the access filters.
Examples
The following example shows how to disable ILMI address registration on ATM interface 1/0/0.
The following example enables ILMI address registration on ATM interface 1/0/0 and configures the per-interface access filter for ILMI address registration to allow well-known group addresses and addresses with matching prefixes.
Related Commands
|
To configure an AESA gateway address on an ATM switch interface that connects to a service provider maintaining a separate ATM addressing plan, use the atm aesa gateway interface configuration command. To restore the default (disabled), use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
When outgoing calls are configured to use the forwarding AESA address as the called party address
(see the atm route command), this AESA is used as the forwarding calling party address.
When incoming calls are received on the interface that specifies the forwarding AESA as the called party address, the called and calling party addresses are removed from the signalling message and replaced by the new called and calling party subaddresses.
This new address is not registered with routing because it is used only as this switch's address for this interface. It is not used as the address of destination from this interface.
The combination of the atm aesa gateway command and the atm-aesa option of the atm route command provides a general mechanism for interconnection of private ATM networks across an ATM service provider. This combination allows one AESA for the interface to the ATM service provider network, with many AESA addresses present in the private network behind the interface.
Examples
The following example shows how to configure the AESA gateway address:
Related Commands
|
To identify an ARP server for the IP network, or set TTL values for entries in the ATM ARP table, use the atm arp-server interface configuration command. To disable an ARP server process, use the no form of this command.
Syntax Description
|
Defaults
The ARP server process is disabled. The default timeout value is 20 minutes.
Command Modes
Command History
Usage Guidelines
This command applies only to route processor and IP interfaces.
If an NSAP address is specified, the ARP client on this interface uses the specified host as an
ARP server.
Multiple ATM ARP servers can be specified by repeating the command. The no option is used to remove the definition of an ATM ARP server. If self is specified, this interface acts as the ARP server for the logical IP network.
The ATM ARP server takes one of the following actions if a destination listed in the server's ARP table expires:
This implementation follows RFC 1577, "Classical IP over ATM."
Related Commands
To enable or disable ILMI autoconfiguration, use the atm auto-configuration interface configuration command. To disable this feature, use the no form of this command.
Syntax Description
This command has no arguments or keywords.
Defaults
Command Modes
Command History
Usage Guidelines
This command enables or disables ILMI autoconfiguration procedures, as specified in Section 8.3.3 of the ATM Forum ILMI 4.0 Specification.
Among the variables covered by ILMI autoconfiguration are the interface protocol and version, interface side (user or network), UNI type (public or private), and the maximum number of VPI bits and VCI bits. Configuration of the atm auto-configuration command on an interface overwrites any previous configuration of the atm iisp, atm nni, atm maxvci-bits, and atm maxvpi-bits commands.
When autoconfiguration is enabled, ATM signalling and ILMI are restarted automatically on the interface. When ATM signalling is restarted, all switched virtual connections across the interface are cleared; permanent virtual connections are not affected.
When the peer switch has a device type of node but responds to GetRequest messages for atmfAtmLayerNniSigVersion with noSuchName, the default NNI protocol depends on the ATM routing mode (see the atm routing-mode command). When the ATM routing mode is set to static, the default NNI protocol is IISP. Otherwise, the default NNI protocol is PNNI 1.0. These defaults are relevant when the peer switch is a LightStream 1010 ATM with software version 11.1.
Examples
The following example shows how to enable ILMI autoconfiguration on interface ATM 0/1/2.
Related Commands
|
To change the maximum number of high-priority cells coming from the destination to the source
at the burst level on the SVC, use the atm backward-max-burst-size-clp0 map-class configuration command. To restore the default, use the no form of this command.
Syntax Description
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp0 indicates this command affects only cells with a CLP of 0 (high-priority cells).
Examples
The following example sets the maximum number of high-priority cells coming from the destination switch at the burst level to 800 cells.
To change the maximum number of the aggregate of low- and high-priority cells coming from the destination to the source at the burst level on the SVC, use the atm backward-max-burst-size-clp1 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp1 applies to the cumulative flow of CLP 0 and CLP 1 cells (high-priority and low-priority cells).
Examples
The following example sets the maximum number of the aggregate of low- and high-priority cells coming from the destination switch at the burst level to 100000.
To change the peak rate of high-priority cells coming from the destination to the source on the SVC, use the atm backward-peak-cell-rate-clp0 map-class configuration command. To restore the default, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp0 indicates this command affects only high-priority cells with a CLP of 0.
Examples
The following example sets the peak rate for high-priority cells from the destination switch router to 8000 kbps.
To change the peak rate of the aggregate of low- and high-priority cells coming from the destination to the source on the SVC, use the atm backward-peak-cell-rate-clp1 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp1 applies to the cumulative flow of CLP 0 and CLP 1 cells (high-priority and low-priority cells).
Examples
The following example sets the peak rate of the aggregate of low- and high-priority cells from the destination switch router to 7000 kbps.
To change the sustainable rate of high-priority cells coming from the destination to the source on the SVC, use the atm backward-sustainable-cell-rate-clp0 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp0 indicates this command affects only high-priority cells with a CLP of 0.
Examples
The following example sets the sustainable rate for high-priority cells from the destination switch
to 800 kbps.
To change the sustainable rate of the aggregate of low- and high-priority cells coming from the destination to the source on the SVC, use the atm backward-sustainable-cell-rate-clp1 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp1 applies to the cumulative flow of CLP 0 and CLP 1 cells (high-priority and low-priority cells).
Examples
The following example sets the sustainable rate of the aggregate of low- and high-priority cells
from the destination switch to 700 kbps.
To change or set the interface limit on the number of best-effort connections, use the
atm cac best-effort-limit interface configuration command. To restore the default, use the
no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
This command places a limit on the total number of ABR and UBR connections on the interface.
This command also supports subinterface configuration.
Examples
In the following example, the number of best effort connections allowed on the interface is limited
to 200.
Related Commands
|
To instruct CAC to consider framing overhead, use the atm cac framing overhead interface configuration command. To restore the default (disabled), use the no form of this command.
Syntax Description
|
Defaults
Framing overhead is not considered in calculating the MaxCR of an ATM interface.
Command Modes
Command History
Usage Guidelines
This command directs CAC to consider framing overhead in calculating the MaxCR of an ATM interface. For example, without this configuration, an OC-3 interface has a cell rate of 155,519 kbps. With the atm cac framing overhead command in effect, the actual cell rate (subtracting SONET framing overhead) is 149,759 kbps.
|
Note Once this configuration command is in effect, subsequent SVC establishment and PVC creation can be altered as compared to the default state (less bandwidth is available, and lower traffic parameter values are allowed). |
|
Note Commands that change the framing in effect on an interface (such as those available on a DS-3 interface) can cause corresponding changes in the maximum cell rate of the interface. |
Examples
The following example forces CAC to account for framing overhead on this interface.
Related Commands
|
To change the resource management interface controlled link-sharing parameters, use the
atm cac link-sharing interface configuration command. To reset the parameter values to the default, use the no form of this command.
Syntax Description
|
Defaults
No limits configured. All minimums are defined as 0 percent, maximums as 95 percent.
Command Modes
Command History
Usage Guidelines
On a 25-Mbps port adapter you can configure the atm cac link-sharing parameter only on
physical ports 0 or 6. The following rules apply:
This command does not support subinterface configuration.
The atm cac link sharing command specifies the minimum and maximum bandwidth that can be allocated to guaranteed service (CBR, VBR, ABR, or UBR+) connections. (UBR+ is UBR with MCR specified.)
Maximums can be individually specified for CBR, VBR, ABR, or UBR+, and also the AGG of this bandwidth. Minimums can be individually specified for CBR, VBR, ABR, and UBR+. These parameters, for a direction, are interrelated as follows (assuming these parameters are defined):
Examples
In the following example, the maximum bandwidth that can be allocated to VBR connections in the transmit direction on the interface is limited to 61 percent of the total bandwidth.
Related Commands
|
To configure the maximum CDVT (per service category and direction) allowed for a connection
on an interface by CAC, use the atm cac max-cdvt interface configuration command. To remove the configuration setting for atm cac max-cdvt, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command configures a maximum for the CDVT that is allowed at connection setup. These can be specified independently by service category and traffic direction.
This command also supports subinterface configuration.
Examples
The following example configures the maximum CDVT allowed by CAC in traffic parameters for the incoming direction of an ABR connection on the interface to 21354.
Related Commands
|
To change the interface maximum for incoming and outgoing MBS at connection startup, use the
atm cac max-mbs interface configuration command. To reset the maximum value to the default, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command configures a maximum for the MBS that is allowed at connection setup. These can be specified independently by traffic direction.
This command also supports subinterface configuration.
Examples
The following example configures the MBS allowed by CAC in traffic parameters for the outgoing direction of an VBR connection on the interface to 2345 cells.
Related Commands
|
To configure the maximum MCR for ABR and UBR service category traffic flowing into and out of the switch router, use the atm cac max-min-cell-rate interface configuration command. To remove these values, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command configures a maximum for the MCR that is allowed at connection setup. These can be specified independently by service category and traffic direction.
This command also supports subinterface configuration.
Examples
The following example configures the maximum MCR allowed by CAC in traffic parameters for the outgoing direction of an ABR connection on the interface to 1340 kbps.
Related Commands
|
To configure the maximum PCR for specific service categories and traffic directions, use the
atm cac max-peak-cell-rate interface configuration command. To restore the default value, use
the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command configures the maximum PCR that is allowed at connection setup. These can be specified independently by service category and traffic direction.
For UBR connections, cell rate is not checked in CAC. By specifying a peak-cell-rate limit, CAC rejects connections that exceed the limit.
This command also supports subinterface configuration.
Examples
The following example configures the maximum PCR allowed by CAC in traffic parameters for the incoming direction of an ABR connection on the interface to 3001 kbps.
Related Commands
|
To configure the maximum SCR for traffic flow in either direction, use the
atm cac max-sustained-cell-rate interface configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command specifies a maximum for the SCR that is allowed at connection setup. These can be specified independently by traffic direction.
This command also supports subinterface configuration.
Examples
The following example configures the maximum SCR allowed by CAC in traffic parameters for the outgoing direction of a VBR connection on the interface to 2201 kbps.
Related Commands
|
To configure overbooking on an ATM or IMA interface, use the atm cac overbooking interface configuration command. To restore the default, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command determines whether overbooking is enabled on an ATM or IMA interface, and specifies the extent of overbooking if enabled. Overbooking causes CAC to expand its concept of the amount of bandwidth available on an interface (receive and transmit) by the percentage specified. This applies to the aggregate bandwidth available on the interface; individual traffic parameters are still limited by the maximum cell rate of the interface in a given direction. Also, the normal limit of 95 percent of MaxCR for guaranteed cell rates (or the appropriate controlled link sharing percentages) applies to the overbooked MaxCR of the interface. The overbooking is expressed as a percentage of the MaxCR of the interface being configured.
An interface must be shut down before any change in the overbooking configuration can be made. (See "Example.") If the overbooking change results in a maximum guaranteed services bandwidth that is below the currently allocated bandwidth guarantees on this interface, then the configuration will be rejected.
Overbooking cannot be configured on regular VP tunnel interfaces and is configurable only on shaped and hierarchical VP tunnel interfaces.
Enabling overbooking is recommended only for advanced users. Enabling overbooking forfeits the protection for guaranteed cell rates provided by the CAC algorithm and hardware.
Examples
In the following example, ATM overbooking is configured for 159 percent of the MaxCR of the interface.
Related Commands
|
To permit or deny a service category on an ATM physical interface, shaped VP tunnel subinterface, or hierarchical VP tunnel subinterface, use the atm cac service-category command. To restore the default configuration of the interface with respect to the service category, use the no form of this command.
Syntax Description
Defaults
For physical interfaces and hierarchical VP tunnel subinterfaces, all service categories are enabled by default. For shaped VP tunnel subinterfaces, only CBR service category is enabled by default.
Command Modes
Command History
Usage Guidelines
This command specifies which service categories to permit or deny on the interface. Changes from the defaults must be done on a separate line for each service category. On a shaped VP tunnel interface, only one service category is permitted at one time.
To deny a service category in a shaped VP tunnel subinterface, you must delete all user VCs of the service category on the interface.
VBR-RT is used for connections where there is a fixed timing relationship between samples. VBR-NRT is used for connections where there is no fixed timing relationship between samples, but where there is still a need for guaranteed QoS.
This command also supports subinterface configuration.
Examples
In the following example, the CBR service category is prohibited on ATM subinterface 0/0/1.51 before service category UBR is allowed.
Related Commands
|
To change the default CDVT to request for UPC of cells received on the interface for connections that do not individually request a CDVT value, use the atm cdvt-default interface configuration command. To reset the default CDVT for a particular service category to the default value, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
CDVT is a limit parameter used in the GCRA policing algorithm to monitor PCR. CDVT can be specified for PVCs through a connection traffic table row. If no CDVT is specified in the row, then a per-interface, per-service category default CDVT is applied for purposes of UPC on the connection.
For signalled connections, CDVT cannot be signalled. Use defaults specified on the interface.
Examples
The following example shows changing the default CDVT for received cells on VBR-RT connections.
Related Commands
|
To create a table entry, use the atm connection-traffic-table-row global configuration command.
To delete an entry, use the no form of this command.
Syntax Description
|
Defaults
Rows 1 through 6 in the table are predefined.
Command Modes
Command History
Usage Guidelines
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 the atm connection-traffic-table-row command is issued without the index clause, the software uses a free row-index, which is displayed to the user 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. For systems that are capable of dual leaky bucket UPC (Catalyst 8540 MSR with feature card, and Catalyst 8510 MSR and LightStream 1010 with FC-PFQ), PCR/CDVT is monitored for service categories other than VBR, and for VBR PCR/CDVT and SCR/MBS. For LightStream 1010 with FC-PCQ, a single leaky bucket provides monitoring for PCR/CDVT for service categories other than VBR, and for VBR SCR/MBS.
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 cell-rate (the maximum cell-rate that fits in 24 bits) that you can signal.
When an ABR row is configured, if MCR is not specified, MCR is configured as 0 in the CTT row.
When a VBR CTT row is configured using the scr0 keyword, the switch processor feature card equipped with a dual leaky bucket polices only the CLP-0 flow of cells to the scrval. When the scr10 keyword is used, the CLP-0+1 flow is policed.
Examples
In the following example, a CBR CTT row is defined with an index of 200 and a peak cell rate of 7743 kbps.
Related Commands
|
To configure the native E.164 address of an ATM interface, use the atm e164 address interface configuration command. To disable the ATM E.164 address, use the no form of this command.
Syntax Description
|
Command Modes
Command History
Usage Guidelines
Use this command to configure a native E.164 address that is used to connect to public networks.
When outgoing calls are configured to use forwarding E.164 addresses as the called party address
(see the atm route command), this E.164 address is used as the forwarding calling party address.
When incoming calls are received on the interface that specifies the E.164 address as the called party address, the received called and calling party addresses are removed from the signalling message and replaced by the new received called and calling party subaddresses.
This new address is not registered with routing since it is only used as this switch's address for this interface. It is not used as the address of destinations from this interface.
Note that this address is not used in conjunction with the E.164 translation table feature. The E.164 translation table should only be used when you want a one-to-one correspondence between the NSAP-format ATM end-system address and the native E.164 address, for example, when the public network does not support transport of subaddresses. The combination of the atm e164 address command and the e164 address option of the atm route command provides a general mechanism for interconnection of private networks across a public network. This combination allows one native
E.164 address for the interface to the public network, with many NSAP-format ATM end-system addresses present in the private network behind the interface.
Examples
The following example shows setting the native E.164 address of ATM 0/0/1 to 1341457.
Related Commands
To enable autoconversion of E.164 addresses, use the atm e164 auto-conversion interface configuration command. To disable E.164 autoconversion, use the no form of this command.
Syntax Description
This command has no keywords or arguments.
Command Modes
Command History
Usage Guidelines
When an interface is configured for E.164 autoconversion, ATM E.164-format addresses are converted to the corresponding native E.164 address for outgoing calls. For incoming calls, native E.164 addresses are converted to the corresponding ATM E.164 format.
Examples
The following example shows how to enable E.164 autoconversion on ATM interface 0/0/1.
Related Commands
To configure an interface to use the ATM E.164 translation table, use the atm e164 translation interface configuration command. To disable the ATM E.164 translation, use the no form of this command.
Syntax Description
This command has no keywords or arguments.
Command Modes
Command History
Usage Guidelines
The ATM E.164 translation table is used when a one-to-one translation between NSAP-format ATM end-system addresses and native E.164 addresses is desired. This method for support of native E.164 addresses might be useful when the ATM interface connects to a public network that does not support transport of subaddresses.
Note that the more general mechanism for interconnection to E.164 public networks involves use of the atm e164 address command and the e164-address option of the atm route command. This other mechanism allows one native E.164 address for the interface to the public network, with many NSAP-format ATM end-system addresses present in the private network behind the interface.
When a signalling message attempts to establish a call from an interface configured for ATM E.164 translation, the called and calling party addresses are initially in NSAP format. Using the ATM E.164 translation table, an attempt is made to find the E.164 addresses corresponding to the NSAP addresses. These E.164 addresses are placed into the called and calling party addresses, and the original NSAP addresses are placed into the called and calling party subaddresses.
When a signalling message is received on an interface configured for ATM E.164 translation, the called and calling party addresses are in E.164 format. If the original NSAP-formatted called and calling addresses have been carried in subaddresses, then those addresses are used to forward the call. If subaddresses are not present, due to the network blocking the subaddresses, or the switch at the entry to the E.164 network does not provide subaddresses, an attempt is made to find a match for the E.164 addresses in the ATM E.164 translation table. If there is a match, the NSAP addresses corresponding to the E.164 addresses are placed into the called and calling party addresses. The call is then forwarded using the NSAP addresses.
Examples
The following example shows setting interface ATM 0/0/1 to use the E.164 translation table.
Related Commands
To start ATM E.164 translation configuration mode, use the atm e164 translation-table global configuration command. To disable the ATM E.164 translation table, use the no form of this command.
|
Note The atm e164 translation-table global configuration command changes the configuration mode to ATM E.164 translation table configuration, and the following new prompt appears: Switch(config-atm-e164)# |
Syntax Description
This command has no keywords or arguments.
Command Modes
Command History
Usage Guidelines
Use this command to start ATM E.164 translation configuration mode.
The ATM E.164 translation table is used by all interfaces configured with the ATM E.164 translation functionality. Each entry in the table specifies a one-to-one correspondence between a native E.164 address and an NSAP-format ATM end-system address.
Refer to the atm e164 translation command for more information and usage guidelines about the ATM E.164 translation feature.
Examples
The following example shows how to start the ATM E.164 translation configuration mode.
Related Commands
To enter the end station ID (ESI) and selector byte fields of the ATM NSAP address, use the atm esi-address interface configuration command. The NSAP address prefix is filled in by way of
the ILMI address registration from the ATM switch router. To remove the end station address, use the
no form of this command.
Syntax Description
|
|
Defaults
No end station ID is defined for this interface.
Command Modes
Command History
Usage Guidelines
This command only applies to the route processor interface and subinterfaces.
The NSAP-format ATM end-system address of an interface is used by static maps (refer to the section "Configuring an SVC-Based Map List" in the ATM Switch Router Software Configuration Guide) and by Classical IP over ATM, as defined in RFC 1577 (refer to the section "Configure Classical IP over ATM in an SVC Environment" in the ATM Switch Router Software Configuration Guide).
The NSAP-format ATM end-system address of an interface can be configured using either the
atm esi-address or the atm nsap-address command. Configuring a new address on the interface overwrites the previous address. The atm esi-address and atm nsap-address commands are mutually exclusive. Configuring the switch with the atm esi-address command negates the atm nsap-address setting, and vice versa.
The atm esi-address command allows you to configure the ATM address by entering the ESI (12 hexadecimal characters) and the selector byte (2 hexadecimal characters). The ATM address prefix (26 hexadecimal characters) is provided by the ATM switch router (refer to the atm address and
atm prefix commands for more information). The resulting ATM address is registered on the ATM switch router using ILMI address registration.
Examples
The following example sets the ESI to 303132333435 and the selector byte to 36 on ATM subinterface 0.1.
Related Commands
To configure an ATM address filter that matches patterns, use one of the forms of the atm filter-expr global configuration command. To delete the specified filter, use the no form of this command.
Syntax Description
|
|
Defaults
Command Modes
Command History
Usage Guidelines
The first form (atm filter-expr name term) defines a simple filter expression that is pattern-matched only if the pattern given by term is matched.
The second form (atm filter-expr name not term) defines a filter expression that is pattern-matched only if the pattern given by term is not matched.
The third form (atm filter-expr name term and term) defines a filter expression that is pattern-matched if either of the patterns given by the two terms are matched.
The fourth form (atm filter-expr name term or term) defines a filter expression that is pattern-matched only if both of the patterns given by the two terms are matched.
The fifth form (atm filter-expr name term xor term) defines a filter expression that is pattern-matched only if one of the patterns, but not both, given by the two terms is matched.
For commands with two terms—that is, commands using logical operators or, and, and xor—the evaluation sequence is from left to right of the expression. Further, for commands using logical operators or and and, the evaluation for the second term is conducted only when necessary, that is, the evaluation for the second term is omitted if the truth or falsehood can already be concluded from the evaluation for the first term.
Examples
The following is sample output from the atm filter-expr command.
Related Commands
To create an ATM address filter set, use the atm filter-set global configuration command. To delete the specified filter, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
If neither permit nor deny is specified, permit is assumed. If an address does not match any
of the filter set entries, an implicit "deny" is returned as the permit/deny action of the filter set.
Filters are set in the same order they were configured. You can change the order (except in a complete NSAP address that has no wildcards) by specifying the optional parameter index.
After you create a filter for a specific interface, associate the filter to that interface by using the
atm access-group command.
Examples
The following is an example of the atm filter-set command.
Related Commands
|
To change the maximum number of high-priority cells going from the source to the destination
at the burst level on the SVC, use the atm forward-max-burst-size-clp0 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp0 indicates this command affects only high-priority cells with a CLP of 0.
Examples
The following example sets the maximum number of high-priority cells going from the source switch at the burst level to 100000.
To change the maximum number of the aggregate of low- and high-priority cells going from the source to the destination at the burst level on the SVC, use the atm forward-max-burst-size-clp1 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp1 applies to the cumulative flow of CLP 0 and CLP 1 cells (high-priority and low-priority cells).
Examples
The following example sets the maximum number of the aggregate of low- and high-priority cells
going from the source switch at the burst level to 100000.
To change the peak rate of high-priority cells going from the source to the destination on the SVC,
use the atm forward-peak-cell-rate-clp0 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp0 indicates this command affects only high-priority cells with a CLP of 0.
Examples
The following example sets the peak of the high-priority cell rate from the source switch to
1000 kbps.
To change the peak rate of the aggregate of low- and high-priority cells coming from the source
to the destination on the SVC, use the atm forward-peak-cell-rate-clp1 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp1 applies to the cumulative flow of CLP 0 and CLP 1 cells (high-priority and low-priority cells).
Examples
The following example sets the peak of the aggregate of low- and high-priority cell rate from the source switch to 100000 kbps.
To change the sustainable rate of high-priority cells coming from the source to the destination on the SVC, use the atm forward-sustainable-cell-rate-clp0 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp0 indicates this command affects only high-priority cells with a CLP of 0.
Examples
The following example sets the sustainable rate of high-priority cells from the source switch to
100000 kbps.
To change the sustainable rate of the aggregate of low- and high-priority cells coming from the
source to the destination on the SVC, use the atm forward-sustainable-cell-rate-clp1 map-class configuration command. To restore the default value, use the no form of this command.
Syntax Description
|
Defaults
The parameter is not specified in the SVC setup request.
Command Modes
Command History
Usage Guidelines
This command defines a traffic parameter for the SVC connection.
The keyword clp1 applies to the cumulative flow of CLP 0 and CLP 1 cells (high-priority and low-priority cells).
Examples
The following example sets the sustainable rate of high-priority cells from the source switch to
100000 kbps.
To change the idle timer for SVCs on an interface that causes the SVCs to disconnect when inactive for a specified interval, use the atm idle-timeout interface configuration command. To restore the default setting, use the no form of this command.
Syntax Description
Defaults
Command Modes
|
Note This command applies only to the route processor interface (ATM 0). |
Command History
Usage Guidelines
To disable idle timeouts, set the value of seconds to 0.
Examples
The following example shows setting the timeout to 250.
Related Commands
To configure ATM IISP on the specified physical or logical (VP tunnel) port, use the atm iisp interface configuration command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
|
Note Before using this command, ILMI autoconfiguration must be disabled. (Refer to the atm auto-configuration command). |
When this command is configured and it causes a change in the interface protocol, version, or side, ATM signalling and ILMI are restarted automatically on the interface. When ATM signalling is restarted, all switch virtual connections across the interface are cleared; permanent virtual connections are not affected. Refer to the ATM Switch Router Software Configuration Guide for more information about this command.
The atm auto-configuration, atm iisp, and atm nni commands are mutually exclusive. Configuring the atm iisp command overwrites any previous configuration of the atm nni or atm uni commands for this interface. Future configuration of the atm auto-configuration, atm nni, or atm uni command on this interface overwrites the atm iisp command.
For calls to be routed from this interface, one or more static routes must be configured. Refer to the
atm route command.
Examples
The following example configures ATM interface 3/1/2 as an IISP interface, running version 3.0 as the user side.
The following example configures subinterface ATM 3/1/3.100 as an IISP interface, and uses the defaults for this command.
Related Commands
|
To set the global default access filter for ILMI-registered addresses on all interfaces, use the
atm ilmi default-access permit global configuration command. To disable the global default access filter, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command allows specification of a global default access filter for ILMI address registration. The access filter feature allows you to permit or deny certain ILMI registered addresses. The global default access filter takes effect when address registration is enabled on an interface, but no per-interface access filter is specified. For additional information, refer to the atm address-registration command.
|
Note If the Cisco SSRP for LAN Emulation is used in this network, ILMI registration of well-known group addresses should be permitted. This allows the active LECS to register the well-known LECS address with the switch. Either the permit all, permit matching-prefix wellknown groups, or permit matching-prefix all-groups option should be configured. |
The global default-access filter for ILMI registration can be overridden by a per-interface access filter. (See the atm address-registration command.)
You should allow certain addresses to be registered through ILMI; however, to restrict them from being advertised through PNNI, the PNNI suppressed summary address feature should be used instead of the access filters for ILMI address registration. (See the summary-address command.)
Examples
The following example shows how to permit all ILMI-registered addresses.
Related Commands
|
To enable the ILMI on a port, use the atm ilmi-enable interface configuration command.
To disable the ILMI on a port, use the no form of this command.
Syntax Description
This command has no arguments or keywords.
Defaults
Command Modes
Command History
Usage Guidelines
This command does not apply to the ATM 0 interface.
ILMI is enabled by default; however, if the peer does not support ILMI, you should turn off ILMI using this command.
Several components of ILMI can be disabled independently without completely disabling ILMI. Refer to the atm address-registration, atm auto-configuration, and atm ilmi-keepalive commands for more information.
Examples
The following example shows how to disable ILMI on interface ATM 1/0/0.
Related Commands
|
To enable or disable ILMI connectivity procedures and to change the ILMI keepalive poll interval, use the atm ilmi-keepalive interface configuration command. To disable ILMI connectivity procedures, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
This command does not apply to the ATM 0 interface.
This command enables ILMI connectivity procedures, as described in Section 8.3.1 of the ATM Forum ILMI 4.0 Specification.
Examples
The following example enables ILMI keepalives on ATM interface 1/0/0, with a poll interval set to 4 seconds and the number of retries to 3.
Related Commands
To allow more than one interface to have the same ATM address, use the atm interface-group command. To remove the interface from an interface group, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
ATM address groups allow more than one interface to have the same ATM address. These multiple connections provide load balancing for traffic from an end station.
Examples
The following example shows how to configure ATM interface 1/1/0 and ATM interface 3/0/1 in ATM address group 5:
Switch(config)# interface atm 1/1/0
Switch(config-if)# atm interface-group 5
Switch(config)# interface atm 3/0/1
Switch(config-if)# atm interface-group 5
Related Commands S
To configure the LECS address advertised by the switch to the end system, use the atm lecs-address interface configuration command.
Syntax Description
|
|
Defaults
If the LECS address is not configured on an interface, the LECS address that was configured using the atm lecs-address-default global configuration command is used by default.
Command Modes
Command History
Usage Guidelines
The LECS address is provided by the switch to directly connect LANE clients over the ILMI. LECS addresses can be configured on both interface and global levels. The globally configured address is sent to a port only if there is no LECS address configured on that port. The sequence number provides the position of this address in the ordered LECS address table.
Related Commands
To configure the LECS address advertised by the switch to the end system, use the
atm lecs-address-default global configuration command.
Syntax Description
Command Modes
Command History
Usage Guidelines
The LECS address is provided by the switch to directly connected LANE clients over the ILMI. LECS addresses can be configured on both interface and global levels. The globally configured address is sent to a port only if there is no LECS address configured on that port. The sequence number provides the position of this address in the ordered LECS address table.
Related Commands
To alter the propagation delay component of the cell-transfer delay offered by an interface, use the
atm link-distance command. To reset the propagation delay to the default value, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
The cell-transfer delay is used for the resource connection admission control of a CBR or VBR-RT connection.
This resource management command is supported for interface and subinterface configurations, and when interface metrics are provided to PNNI routing.
Related Commands
To create and delete well-known (reserved) PVCs with non-default connection identifiers, or other nondefault parameters, use the atm manual-well-known-vc interface configuration command.
To reenable the automatic default well-known VC mode, use the no form of this command.
Syntax Description
|
Defaults
The keep option becomes the default on existing automatically created VCs when manual mode
is entered.
Command Modes
Command History
Usage Guidelines
This command does not apply to the route processor interface (ATM 0).
All interfaces default to the no form of this command during initial startup. When this command is in effect, well-known VCs are not automatically created at startup. When this mode is enabled on an interface, the allowed range for VCI values is 5 through 16383, instead of 32 through 16383.
The three additional reserved channel encapsulation types added for the CPU PVCs are QSAAL, PNNI, and ILMI. These specify that the interface is a signalling, PNNI, or ILMI reserved channel.
You must enter the copy running-config command using the startup-config option to disable the automatic creation of default well-known VCs at system startup.
Although the OAM channels for tunnels are well-known channels (VCI 3 and VCI 4), they are not affected by the atm manual-well-known-vc status.
|
Note You should not change the well-known channels to use a VC where the remote end is sending AAL5 messages not intended for this well-known VC. This means you should not swap VC values between two types of well-known VCs. |
When using the no form of this command, if there are existing non-default reserved channel VCs for this interface, you are prompted to confirm that the VC can be automatically deleted. (If you enter no, the command stops abruptly.) Well-known VCs with default configurations are then automatically created for the interface. The default well-known PVCs are no longer shown as part of the running configuration.
Examples
The following example puts an interface into the manual-well-known-vc mode, deletes the existing default signalling PVC, and then creates a signalling PVC using a VCI value of 7.
Related Commands
|
To configure the maximum number of ATM VCs supported on the ATM interface, use the atm maxvc-number interface configuration command. To restore the default value, use the
no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
Before using this command, the interface must be administratively shut down.
Examples
The following example sets the maximum number of ATM virtual channels supported on interface
ATM 0/0/0 to 8000.
Related Commands
|
To configure the maximum number of active bits of VCI supported on an ATM interface, use the
atm maxvci-bits interface configuration command. To restore the default value, use the no form of
this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
Before using the atm maxvci-bits command, disable the atm auto-configuration command. Refer to "Examples" below.
When the atm auto-configuration command is configured, it causes a change in the maximum number of active VCI bits, and ATM signalling and ILMI are restarted automatically on the interface. When ATM signalling is restarted, all switched virtual connections across the interface are cleared; permanent virtual connections are not affected.
Examples
The following example sets the maximum number of active VCI bits to 10 for interface ATM 0/0/0.
Related Commands
To configure the maximum number of ATM VPs supported on an ATM interface, use the
atm maxvp-number interface configuration command. To restore the default value, use the
no form of this command.
Syntax Description
|
|
Defaults
For the Catalyst 8540 MSR: 4095 virtual paths
For the Catalyst 8510 MSR and LightStream 1010: 255 virtual paths
Command Modes
Command History
Examples
The following example sets the maximum number of ATM virtual paths supported on interface ATM 0/0/1 to 128.
Related Commands
To configure the maximum number of active VPI bits supported on an ATM interface, use the
atm maxvpi-bits interface configuration command. To restore the default value, use the no form
of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
|
Note Before using this command, ILMI autoconfiguration must be disabled. See the atm auto-configuration command. |
When this command is configured and it causes a change in the maximum number of active VPI bits, ATM signalling and ILMI automatically restart on the interface. When ATM signalling is restarted, all switched virtual connections across the interface are cleared; permanent virtual connections are not affected.
|
Note Only 6 interfaces per switch module can have the VPI bits set to more than 8 bits. If an interface with more than 8 bits of VPI is removed (for example, a port adapter is hot-swapped), you can set the VPI bits to more than 8 bits on another interface on the same switch module. If, however, you reinstall the original interface (which had more than 8 bits of VPI), it reconfigures back to 8 bits. If this occurs, the VCs with the VPI set to 255 or higher are sent into a NO HW RESOURCES state. To configure this interface back to a VPI of greater than 8, another interface on the same MSC module must be configured to less than 8 bits. To restore the VC from the NO HW RESOURCES state, toggle the interface using the shut or no shut command. (Catalyst 8540 MSR) |
Examples
The following example sets the maximum number of active VPI bits to 6 for interface ATM 0/0/0.
Related Commands
|
To change the default MBS to request for UPC of cells received on the interface for connections
that do not individually request an MBS value, use the atm mbs-default interface configuration command. To reset the default MBS for a particular service category to the default value, use the
no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
MBS is used to determine the burst tolerance limit parameter used in the GCRA policing algorithm to police SCR.
MBS can be specified for PVCs through a connection traffic table row. If no MBS is specified in the row, then a per-interface, per-service category default MBS is applied for purposes of UPC on the connection. This command allows for changes to the MBS default.
Examples
The following example shows changing the default MBS for received cells on VBR-RT connections.
Related Commands
|
To configure an ATM NNI on the specified physical or logical (VP tunnel) port, use the atm nni interface configuration command.
Syntax Description
This command has no keywords or arguments.
Command Modes
Command History
Usage Guidelines
|
Note Before using this command, ILMI autoconfiguration must be disabled. See the atm auto-configuration command. |
When this command is configured and it causes a change in the interface protocol, ATM signalling and ILMI are restarted automatically on the interface. When ATM signalling is restarted, all switched virtual connections across the interface are cleared; permanent virtual connections are not affected.
The PNNI routing and signalling protocol is run over all NNI interfaces, except those interfaces on which signalling was previously disabled (see the atm signalling enable command). To configure an IISP interface, use the atm iisp command.
The atm auto-configuration, atm iisp, and atm nni commands are mutually exclusive. Configuring the atm nni command overwrites any previous configuration of the atm iisp command for this interface. Future configuration of the atm auto-configuration, and atm iisp command on this interface overwrites the atm nni command.
Examples
The following example shows configuring an ATM NNI on logical port card 3, subcard 1, and
port 3, VPI 99.
Related Commands
To configure the NSAP-format ATM end-system address of an ATM interface, use the
atm nsap-address interface configuration command. To remove any configured NSAP-format
address for the interface, use the no form of this command.
Syntax Description
|
Command Modes
Command History
Usage Guidelines
This command only applies to the route processor interface and subinterfaces.
The NSAP-format ATM end-system address of an interface is used by static maps (refer to the section "Configuring an SVC-Based Map List" in the ATM Switch Router Software Configuration Guide) and by Classical IP over ATM, as defined in RFC 1577 (see the section "Configure Classical IP over ATM in an SVC Environment" in the ATM Switch Router Software Configuration Guide).
The NSAP-format ATM end-system address of an interface can be configured using either the
atm esi-address or the atm nsap-address command. Configuring a new address on the interface overwrites the previous address. The atm esi-address and atm nsap-address commands are mutually exclusive. Configuring the switch with the atm esi-address command negates the atm nsap-address setting, and vice versa.
NSAP-format ATM end-system addresses have a fixed length of 40 hexadecimal digits. Configure the address using the following dotted format:
|
Note ATM addresses configured using the atm nsap-address command are not automatically registered with ATM routing on the switch. In addition to configuring these addresses using the atm nsap-address command, the addresses must be configured as static routes on the route processor interface of the ATM switch router. |
Examples
The following example shows how to configure the NSAP-format ATM end-system address for interface ATM 0.1.
Related Commands
|
To define an ATM map statement for an SVC, use the atm-nsap map-list configuration subcommand in conjunction with the map-list global configuration subcommand. To remove the address, use the
no form of this command.
Syntax Description
|
Defaults
No map statements are defined.
Command Modes
Command History
Usage Guidelines
This command is required with the map-list command when you are configuring an SVC.
Examples
In the following example, a map list named atmsvc includes one map statement for a destination address being mapped.
Related Commands
To configure the OAM, AIS, RDI, and loopback operations and to set the maximum number of OAM connections, use the atm oam global configuration command. To disable these operations, use the
no form of this command.
Catalyst 8510 MSR and LightStream 1010
Syntax Description
|
Command Modes
Command History
Usage Guidelines
To set the maximum number of OAM connections that can be configured per switch, use the
atm oam max-limit global configuration command.
Examples
The following example globally enables AIS, RDI, and segment loopback operators for all interfaces.
Related Commands
To configure the OAM, AIS, RDI, and loopback modules at the interface level, use the atm oam interface configuration command. To disable these modules, use the no form of this command.
Syntax Description
|
Defaults
Default for the loopback-timer interval is 5 seconds.
Command Modes
Command History
Usage Guidelines
To enable or disable OAM operations on a VP connection, only specify the vpi value. To enable or disable VC connections, you must specify both vpi and vci values.
In interface and subinterface command modes, vpt configuration is supported.
|
Note For the Catalyst 8510 MSR and the LightStream 1010, use the atm oam loopback-timer command only with the seg-loopback and end-loopback keywords. |
Examples
The following example enables end-to-end OAM loopback on VPI 50 VCI 100 on ATM 3/0/0.
The following example enables or disables the OAM, AIS, RDI, and loopback operation to a specified connection.
The following example shows changing the loopback timer interval to 10 seconds.
Related Commands
|
To change the maximum queue size of the output queue, use the atm output-queue interface configuration command. To reset the maximum queue size to the default value, use the no form
of this command.
Syntax Description
|
Defaults
Varies by physical interface type, queue, and either abr-ubr or vbr-nrt queues, and by the OSF value.
Command Modes
Command History
Usage Guidelines
The force argument indicates that the change should be made even if it results in losing data on the interface queue (the queue must be momentarily disabled to change the threshold). This command without the force argument only changes the threshold if the interface is down. An error message is displayed and the command does not take effect if the interface is up and the force argument has not been specified.
|
Note This command is not supported on systems equipped with the FC-PCQ. |
This command does not support subinterface configuration and does not apply to the route processor interface (ATM 0).
On a 25-Mbps port adapter, you can configure the parameters only on physical ports 0 or 6. The following rules apply:
Examples
In the following example, the maximum size of the vbr-nrt output queue is set to a minimum of 512 cells. This can be set even if the interface is up.
Related Commands
|
To change the output queue thresholds, use the atm output-threshold interface configuration command. To reset the threshold to the default value, use the no form of this command.
Syntax Description
|
Defaults
For all service categories, discard is 87 percent and efci is 25 percent.
The abr relative-rate is 25 percent.
Command Modes
Command History
Usage Guidelines
This command does not support subinterface configuration. This command does not apply to the route processor interface (ATM 0).
|
Note This command is not supported on systems equipped with FC-PCQ. |
You can configure the abr relative-rate parameter only on physical ports 0 or 6 on a 25-Mbps port adapter. The following rules apply:
Examples
In the following example, the discard threshold of the VBR-NRT queue is set to 87 percent of the maximum queue size.
Related Commands
To set the over-subscription factor, use the atm over-subscription-factor global configuration command. To restore the default value to the over-subscription factor, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
The over-subscription factor number is a positive integer from 1 through 32. Use this command to determine the initial port queue size. The over-subscription factor is used to size the VBR-NRT and ABR/UBR queues.
The resizing of queues can be overridden using the atm output-queue (Catalyst 8510 MSR and LightStream 1010) command. Changes to the atm over-subscription-factor command only take place during startup.
The sizing of VBR-NRT and ABR UBR queues is determined by the following equations.
The default size of the CBR and VBR queues varies by interface type, as defined in Table 2-2.
Table 2-2 Default Maximum Queue Size by Interface Type
|
|
Note This command is not supported on systems equipped with FC-PFQ. |
Examples
In the following example, the over-subscription factor of the switch is set to 15. To effect this change and resize the UBR and VBR-RT queues, the configuration must be written to NVRAM and the switch must be restarted.
Related Commands
To enable or change the artificial limitation on interface output rate, use the atm pacing interface configuration command. To disable output pacing, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
This command is only available on systems equipped with the switch processor feature card or on LightStream 1010 not equipped with FC-FCQ.
|
Note For the Catalyst 8540, this command applies only to port adapters in the carrier module. |
This command is not supported for subinterface configuration and does not apply to the route processor interface (ATM 0). You cannot configure this parameter on OC-12 and 25-Mbps ports.
On systems equipped with the switch processor feature card, the pacing value installed cannot be less than the guaranteed bandwidth allocated on the interface, regardless of the value of the force argument. The force argument indicates that the change should be made even if it results in an output cell-rate that does not provide sufficient bandwidth for guaranteed service on the transmit flow of the interface. An error message is displayed and the command does not take effect if the change impacts guaranteed bandwidth, and the force argument is not present.
|
Note The granularity of the pacing rate provided by the hardware varies with the size of the bit rate requested. The value entered by the user is rounded up to the closest value available for installation in the hardware. Both the configured and installed values are displayed with the show ima interface command. |
Examples
In the following example, the transmit cell rate of the interface is limited to the closest value possible in hardware, greater than 30,000 kbps. If the amount of bandwidth allocated to CBR and VBR connections in the transmit direction on the interface is greater than 30,000 kbps, the command fails.
Related Commands
To specify the administrative weight of the ATM PNNI interface, use the atm pnni admin-weight interface configuration command. To return to the default values, use the no form of this command.
Syntax Description
|
Defaults
Determined by the mode set by the administrative-weight command.
Command Modes
Command History
Usage Guidelines
This command does not apply to the ATM 0 interface and applies only to the NNI interface.
Use this command to manually set the administrative weight of an interface. Changing the administrative weight of an interface to a larger value might cause calls to be routed away from
the interface.
Related Commands
|
To specify the aggregation token for a PNNI interface, use the atm pnni aggregation-token
PNNI interface configuration command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Aggregation tokens are used to determine the grouping of links that are summarized to higher levels of the PNNI hierarchy. All lower-level links with the same aggregation token between a pair of peer groups will be treated as a single aggregated link at the parent node level.
In the default case, all parallel links between two peer groups are aggregated with aggregation token 0.
Examples
The following example shows how to set the aggregation token on ATM interface 1/0/0.
Related Commands
|
To enter PNNI explicit path configuration mode to create or modify PNNI explicit paths, use
the atm pnni explicit-path command from global configuration mode. Use the no form of this command to delete the explicit path and all associated explicit path segments.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
Use this command to manually configure either a fully-specified or a partially-constrained path for routing a standard soft VC or soft VP connection or a Frame Relay soft VC.
Once you are in PNNI explicit path configuration mode, there are several commands that you can use to create and edit an ordered list of path entries. Refer to the following commands for more information on creating the individual path entries:
Each explicit path has entries with indexes that give it a relative position within the list. Use these indexes to edit an explicit path. After each entry is added, the entire current list is displayed.
Use the following keywords to edit, add an entry to, or delete an entry from an explicit path:
Use the following syntax to edit, add an entry to, or delete an entry from any explicit path:
Examples
The following example shows how to enter PNNI explicit path configuration mode from global configuration mode, for a path named boston_2.path1.
Once in PNNI explicit path configuration mode, the following example shows how to configure the explicit path boston_2.path1 with four entries and then exit explicit path configuration mode:
The following example shows how to reenter PNNI explicit path configuration mode for a path named new_york.path1 and list the current path.
Examples
The following example shows how to modify the first entry to add an exit port, using the index keyword to specify the index of the entry to be modified.
The following example shows how to use the append-after keyword to add a new entry into an explicit path list.
If the explicit path has four next-node entries labelled as index 1 through 4, use the append-after keyword to add a new entry after index 2, which results in index 3. The remaining two entries are automatically renumbered to index 4 and 5 to accommodate the newly added index 3.
Related Commands
|
To configure a method for selecting a link out of multiple links to the same neighbor, use the
atm pnni link-selection interface configuration command. To return to the default value, use
the no form of this command.
Syntax Description
|
Defaults
blocking-minimize is the default link selection for cbr, vbr-rt, and vbr-nrt service categories.
load-balance is the default link selection for abr and ubr service categories.
Command Modes
Command History
Usage Guidelines
This command does not apply to the ATM 0 interface.
Link selection applies whenever the port specified in the DTL is zero and there are multiple interfaces to the next node.
When multiple parallel "alternate" links are considered during call setup, the load-balance link selection is applied to these parallel links. The alternate configuration on some links does not modify the link selection for non-alternate parallel links.
When multiple parallel links are configured inconsistently, the order of precedence of configured values is admin-weight-minimize, blocking-minimize, transmit-speed-maximize, and load-balance. For example, if any link is configured as admin-weight-minimize, that becomes the link selection criteria for the entire group.
Examples
The following example shows how to configure link selection on ATM interface 0/0/0 with a VPR-NRT service category and in transmit speed maximize mode:
The following example shows how to configure link selection on ATM interface 0/0/0 with a
CBR service category, and then designate the link as an alternate:
Related Commands
Use the atm pnni mobile command to specify a PNNI interface node as mobile in a mobile network.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Applies to interfaces on mobile switches (border nodes in a mobile network). A mobile interface (or link) is a wireless (physical or virtual path) connection between two switches, at least one of which is mobile.
Use the atm pnni mobile command to enable a mobile border switch to advertise an outside nodal hierarchy list to its peer group. Without advertising, a mobile network cannot join a host peer group.
Examples
The following example shows how to specify an interface as mobile.
Related Commands
|
To specify which PNNI node in the switch router runs on an interface when the interface runs PNNI, use the atm pnni node interface configuration command. To return to the default value, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command does not apply to the ATM 0 interface.
Currently node index 1 is the only valid value. Refer to the node command for more information.
By default, PNNI node 1 automatically runs on all PNNI interfaces.
This command does not turn PNNI on or off for this interface. See the atm auto-configuration command and the atm nni commands for more information on the interface type.
Examples
The following example shows how to configure a PNNI node index on ATM interface 1/0/0.
Related Commands
|
Specifies the highest level of PNNI hierarchy to be advertised in the outside nodal hierarchy list.
Syntax Description
Defaults
Default is zero, the highest PNNIlevel possible. Using the default, the outside nodal hierarchy list will not be truncated, allowing attached mobile networks to see all network levels of a fixed network.
Command Modes
Command History
Usage Guidelines
An access point switch is a border switch in a fixed network that has the capacity to establish a wireless connection with a mobile network.
Use the atm pnni nodal-hierarchy-list highest-level command in conjunction with an access point switch interface connected to a mobile network. This command sets the highest level advertised in the outside nodal hierarchy list by the access point switch. A mobile network cannot access any hierarchy level higher than the advertised level because it cannot see it. Using this command prevents mobile networks from connecting at higher than wanted levels to a fixed network and/or offers protection against badly configured networks.
Examples
The following example shows how to specify the highest outside nodal hierarchy level for an interface.
Related Commands i
|
To configure an ILMI address prefix for an ATM interface, use the atm prefix interface configuration command. To delete a configured ILMI address prefix, use the no form of this command.
Syntax Description
Command Modes
Command History
Usage Guidelines
This command is used to assign one or more address prefixes to a specific interface that is different from any prefixes based on the switch addresses (see the atm address command). ILMI assigns the prefix to end systems attached to this interface. These prefixes are used as network prefixes during ILMI address registration.
Whenever one or more ILMI address prefix is assigned on an interface, no network prefixes derived from the switch address are used for address registration on that interface.
Examples
The following example shows how to configure an ILMI address prefix on interface ATM 3/1/0.
Related Commands
To create a PVC, 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.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
The commands are used to create or delete the following types of ATM connections on a switch.
When setting UBR connections the tx-cttr and rx-cttr fields are not needed, but these fields are required when setting 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.
Examples
The following example shows how to configure a terminating PVC between interface ATM 3/1/1 and the route processor port.
The following example shows how to set up a UBR PVC connection between interface ATM 3/0/0 and 3/0/1 with a VPI of 0 and a VCI of 40.
The following example shows a display using the encap variable.
The following example shows how to establish a PVC between a logical interface (VP tunnel) on ATM 3/1/1.99 and ATM 3/0/0.
The following example shows how to use the show atm vc command to display all VCs on an interface. The Encap column is displayed only on systems equipped with the switch processor feature card.
The following example shows how to use the show atm vc command to display detailed information about a specific connection on a system equipped with the switch processor feature card.
The following example shows how to delete the previously configured ATM transit point-to-point PVC.
Examples
The following example shows how to use the show atm vc command to display detailed information about a specific connection on a system equipped with the FC-PCQ.
Related Commands
To create a PVP, use the atm pvp interface configuration command. To create a PVPC, use the
long form of the atm pvp command. To create a PVPL, use the short form of the atm pvp command. To remove the specified PVP, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
When the PVP is specified as shaped or hierarchical, it must subsequently be used as a VP tunnel
(via the interface command). Only CBR VPs can be used for shaped or hierarchical tunnels. A shaped or hierarchical PVP cannot be cross-connected.
|
Note Shaped and hierarchical tunnels are only supported on systems with FC-PFQ installed. The atm pvp command does not apply to the route processor port or logical port (VP tunnel). |
The commands are used to create or delete the following types of ATM connections on a switch:
Hierarchical VP tunnels can only be defined on slots 0, 2, 8, and 11.
The maximum number of hierarchical VP tunnels that can be supported on the ATM switch router varies from 120 to 240, depending on the port adapter type installed.
If the ATM switch router is entirely populated with LightStream 1010 port adapters installed in carrier modules, hierarchical VP-tunnels can be defined on the following ports, for a total of 120 defined hierarchical VP-tunnels.
If the ATM switch router is entirely populated with OC-12 SuperPAMs, hierarchical VP tunnels can be defined on the following ports, for a total of 240 defined hierarchical VP-tunnels.
For a total of 240 defined hierarchical VP-tunnels.
Any physical port with one or more hierarchical VP tunnels defined cannot have any other VCs or VPs (signalled or permanent) defined on that port (except well-known VCs).
Conversely, to define a hierarchical VP tunnel on a port, all existing VCs or VPs on that port must be removed.
Tag switching must not be configured on a port that has hierarchical VP tunnels defined.
|
Note You must enable the hierarchical VP tunnel feature on the ATM switch router before configuring hierarchical VP tunnels on an interface. See the atm idle-timeout command for configuration information. |
Before physically removing a port adapter from the chassis with hierarchical VP tunnels defined, all defined hierarchical VP tunnels must be deleted, unless an identical port adapter is plugged back in.
If you do not do this, the hardware schedulers allocated for these hierarchical tunnels remain allocated and cannot be used by any other port.
Usage Guidelines
When the PVP is specified as shaped or hierarchical, it must subsequently be used as a VP tunnel
(via the interface command). Only CBR VPs can be used for shaped or hierarchical tunnels. A shaped or hierarchical PVP cannot be cross-connected.
|
Note Shaped and hierarchical tunnels are only supported on systems with FC-PFQ installed. The atm pvp command does not apply to the route processor port or logical port (VP tunnel). |
The commands are used to create or delete the following types of ATM connections on a switch:
ATM switch routers equipped with ASP-B and feature card version FC-PFQ can have hierarchical VP tunnels defined on the following ports:
0/0/port and 3/0/port (30 maximum)
0/1/port and 3/1/port (32 maximum)
ATM switch routers equipped with ASP-C and feature card version FC-PFQ can have hierarchical VP-tunnels defined on the following ports:
Any physical port with one or more hierarchical VP tunnels defined cannot have any other VCs or VPs (signalled or permanent) defined on that port (except well-known VCs).
Conversely, to define a hierarchical VP tunnel on a port, all existing VCs or VPs on that port must be removed.
Tag switching must not be configured on a port that has hierarchical VP tunnels defined.
|
Note You must enable the hierarchical VP tunnel feature on the ATM switch router before configuring hierarchical VP tunnels on an interface. See the atm idle-timeout command for configuration information. |
Before you physically remove a port adapter from the chassis with hierarchical VP tunnels defined, we strongly recommended that all defined hierarchical VP tunnels be deleted, unless an identical port adapter is plugged back in. If you do not do this, the hardware schedulers allocated for these hierarchical tunnels remain allocated and cannot be used by any other port.
Examples
The following example shows how to configure an ATM PVP from ATM 3/1/1 to ATM 3/1/2.
The following example shows how to use the show atm vp command to display details about the ATM interface 3/1/1 for VPI 99 using the switch processor feature card.
To create a VP tunnel on a physical interface, enter the interface configuration mode for the switch, then specify the PVP and create the tunnel. The following example shows the commands used to create a tunnel on ATM 0/0/1.
The following example shows how to use the show atm interface command to display the interface information about ATM 0/0/1.51 using the switch processor feature card.
To create a hierarchical VP tunnel on a physical interface, enter the interface configuration mode for the switch, then specify the PVP and create the tunnel. The following example shows the commands used to create a hierarchical VP tunnel on ATM 0/0/0.10.
Related Commands
To change individual QoS objectives assigned to SVC setup messages entering the switch through UNI interfaces, use the atm qos default global configuration command. To return all objective values for a service category to the default, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
This command changes the individual QoS objectives used in establishing CBR or VBR SVCs.
The QoS objectives are as follows:
These objectives can be set differently for each of the three service categories: CBR, VBR-RT,
and VBR-NRT (VBR-NRT only uses CLR0 and CLR01). All UNI SVC requests received for a particular service category use the configured values. These objectives are signalled across a continuous sequence of PNNI hops, starting at the source switch.
When max-cell-loss-ratio is specified, and the clp0 or clp1plus0 value is not configured, the default
is CLP=0.
Examples
In the following example, the cbr MaxCTD objective is set to 1000 microseconds.
Related Commands
To add a port to an ATM-RMON MIB port select group, use the atm rmon collect interface configuration command. To disable ATM-RMON collection, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
This command allows references to a nonexistent port select group. You cannot reference an active port select group. However, you can access the group if RMON collection is disabled using the no form of the atm rmon collect command.
|
Note Collection must be disabled with the no atm rmon enable command before using the no form of this command. |
Currently, this command is not allowed on logical ports (VP tunnel).
Examples
The following example shows setting the port select group number to 1000.
Related Commands
To enable ATM-RMON MIB data collection, use the atm rmon enable global configuration command. To stop data collection for all fully configured port select groups, use the no form of this command.
Syntax Description
This command has no keywords or arguments.
Defaults
Command Modes
Command History
Usage Guidelines
Using this command causes dynamic data pools to be allocated and data collection to begin in the background. This command also propagates signalling information to the RMON agent.
When using the no form of this command, all control tables are preserved; however, the drop, insert, and delete counters are cleared, and all data tables are removed.
Related Commands
To configure statics, host, and matrix collection parameters for ATM-RMON MIB, use the atm rmon portselgrp global configuration command. To remove data to a configured port select group, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
To use this command, configure the ports into port select groups using the atm rmon collect interface configuration command.
Examples
The following example shows configuring the port select group, and sets the maxhost to 1000 and the matrix-scope to 3.
Related Commands
To specify a static route to a reachable address prefix, use the atm route global configuration command. To delete a static route, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
The internal keyword should be used when a static route is configured to an address prefix representing an attached end system (for example, in place of an ILMI address registration).
The type of static route should be exterior, and the internal keyword should not be present when a static route is configured to an address prefix representing end systems attached to a different switch or network.
The scope keyword value translates to a PNNI level according to the PNNI scope map. Refer to the scope map and scope mode commands for more information.
When the e164-address option is included, the specified address-string is passed on as the called party address. The received called party address is passed on as the called party subaddress, the E.164 address of this interface (configured using the atm e164 address command) is passed on as the calling party address, and the received calling party address (if any) is passed on as the calling party subaddress.
If no e164-address is specified, the received called party address and calling party address are passed on unchanged.
When the aesa-gateway option is included, the specified AESA address is passed on as the called party address. The received called party address is passed on as the called party subaddress. The AESA gateway address of this interface (configured using the atm aesa gateway command) is passed on as the calling party address. The received calling party address (if any) is passed on as the calling party subaddress.
Examples
The following example shows how to configure a static route on interface ATM 1/2/1 to the address prefix 47.8 of 12 bits in length.
The following example shows how to configure a static route on interface ATM 1/2/1 to the address prefix 47.88 of 14 bits in length.
The following example shows how to configure a static route on ATM 0/0/0 with a forwarding E.164 address.
The following example shows how to configure a static route with a forwarding AESA gateway address.
Related Commands
|
To initiate route optimization immediately for a specific interface or specific soft VC, use the
atm route-optimization EXEC command.
Syntax Description
|
Command Modes
Command History
Usage Guidelines
If you do not specify the VPI and VCI, this command sets optimization for a specific interface.
If you specify the VPI and VCI, this command sets optimization for a specific soft VC.
|
Note The atm route-optimization (EXEC) command must be entered on the same interface where the soft PVCs or PVPs are configured. Route optimization only works for the source end of a soft PVC or PVP, and is ignored if entered on the destination interface. |
Examples
The following example shows how to initiate ATM route optimization on a soft VC at ATM
interface 1/0/0 100 250.
The following example shows how to initiate ATM route optimization on a soft VC at serial
interface 1/0/3:3 DLCI 248.
Related Commands
|
To enable and configure soft PVC route optimization on an ATM interface, use the
atm route-optimization interface configuration command. To disable this feature, use the no form of this command.
Syntax Description
|
Defaults
For interval: 60 minutes
For time-of-day: anytime
Command Modes
Command History
Usage Guidelines
Use this command to enable and configure soft PVC route optimization to determine when a better route is found. You can also reconfigure the old route after you perform this configuration.
|
Note The atm route-optimization (interface) command must be entered on the same interface where the soft PVCs or PVPs are configured. Route optimization only works for the source end of a soft PVC or PVP and is ignored if entered on the destination interface. |
The time-of-day parameter is used as a filter to determine if route optimization is acceptable when the interval timer activates.
To ensure that route optimization takes place at least once a day, set the interval to a smaller value than the time range. After route-optimization starts, it runs until it is finished regardless of the time range. All connections on this interface subject to route optimization are checked to see if better paths exist. When better paths are found, the connections are rerouted.
|
Note The atm route-optimization (interface) command can also be used to configure route optimization for Frame Relay interfaces. |
Examples
The following example enables soft PVC route optimization on interface ATM 0/1/2, with the time period of 120 minutes.
The following example configures a soft PVC with route optimization interval configured as every 30 minutes between the hours of 6:00 p.m. and 5:00 a.m.
Related Commands
|
To specify the percentage reduction in the administrative weight of the existing path required to trigger route optimization, use the atm route-optimization percentage-threshold global configuration command. To set the threshold to the default value, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
When route optimization is enabled and the threshold is exceeded, the existing path is partially torn down and a new path is established. Currently route optimization is only supported for soft PVCs and soft PVPs.
Smaller values lead to greater network efficiency, at the expense of an increased amount of calls subject to rerouting.
Examples
The following example shows setting the route optimization threshold to 20 percent.
Related Commands
|
To enter the PNNI configuration mode, use the atm router pnni global configuration command.
To exit from the PNNI configuration mode, use the no form of this command.
Syntax Description
This command has no arguments or keywords.
Command Modes
Command History
Usage Guidelines
Use this command to start global PNNI configuration mode.
Examples
The following example shows using the atm router pnni global configuration command to change to ATM router PNNI configuration mode.
Related Commands
To restrict the mode of ATM routing on an ATM switch router, use the atm routing-mode global configuration command. To remove all restrictions on ATM routing, use the no form of this command.
Syntax Description
|
Defaults
Disabled (no restrictions on ATM routing)
Command Modes
Command History
Usage Guidelines
This command takes effect on the next reboot.
Switch behavior in static routing mode is analogous to that of the LightStream 1010 default IISP software images of Cisco IOS Release 11.1. Without any restrictions on the routing mode, PNNI functionality is available on all interfaces.
This command differs from deletion of all PNNI nodes (using the node command) because it affects ILMI autoconfiguration. When the switch is in static routing mode, for each interface, the ILMI variable atmfAtmLayerNniSigVersion for the switch is set to iisp. This causes ILMI autoconfiguration on interfaces between two switches to determine an interface type of IISP, unless the switch on the other side indicates that the NNI signalling protocol is not supported.
Examples
The following example shows configuration of a switch to allow only static routing.
Related Commands
|
To set the limits on the number of cells simultaneously allowed in the switch memory by type of output queue, use the atm service-category-limit global configuration command. To restore the default value of 64544, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
The no form of this command applies to all service categories.
|
Note This command is not supported on systems equipped with the FC-PFQ. |
 |
Caution Setting a service-category-limit to 0 causes the connection requests for the associated service categories to be rejected. |
Examples
In the following example, the maximum number of abr and ubr cells allowed into the switch fabric at one time is limited to 45000.
Related Commands
To specify the weighting for each service class for physical interfaces or for a hierarchical VP tunnel, use the atm service-class interface configuration command. To return the weight of the specified class to its default (See tables below), use the no form of this command.
To specify the weighting for each service class for physical interfaces or for a hierarchical VP tunnel, use the atm service-class interface configuration command. To return the weight of the specified class to its default, use the no form of the atm service-class command. This command supports both the ATM Forum service categories and the TBR service classes on physical interfaces, as shown in Table 2-3.
Table 2-3 ATM Forum Service Classes and Tag Bit Rate Service Classes for Physical Interfaces
|
To specify the weighting of each service class for a physical interface, use the following syntax:
To cancel WRR scheduling or to set weights to their defaults, use the no form of the command.
For hierarchical VP tunnels, this command supports either the ATM Forum service categories or the TBR service classes, as shown in Table 2-4.
Table 2-4 ATM Forum Service Classes and Tag Bit Rate Service Classes for Hierarchical VP Tunnels
|
To specify the weighting for each service class for a hierarchical VP tunnel, use the following syntax:
To cancel WRR scheduling or to set weights to their defaults, use the no form of the command.
Syntax Description
|
Defaults
Table 2-5 lists the service classes and the default class weights for physical interfaces and hierarchical VP tunnels.
Table 2-5 Service Classes and Default Class Weights for Physical Interfaces and Hierarchical VP Tunnels
|
||||||||||||||||||||||||||||||||||||||||||||||||||
Command Modes
Command History
Usage Guidelines
If wrr-weight is not specified, the default weight applies. The no form of the command returns the weight of the specified class to its default.
|
Note This command is available only on systems equipped with the FC-PFQ. |
Examples
In the following example, ATM interface 2/0/1 is configured for service class 3 with a
WRR weight of 8.
Related Commands
To restrict access to and from a closed user group, use the atm signalling cug access interface configuration command. To disable this feature, use the no form of this command.
Syntax Description
|
Defaults
No incoming or outgoing access allowed. An interface is not considered to be a CUG access interface unless this command is configured. If the keywords permit-unknown-cugs are not specified, calls to or from unknown CUGs are denied. When a CUG call goes out, and the destination is not in the same CUG, the call is rejected at the destination switch.
Command Modes
Command History
Usage Guidelines
CUG procedures are invoked on the interface only if the interface is configured as an access interface. No CUG configuration applies until this command is configured.
Transmission and reception of CUG interlock codes is not allowed over access interfaces.
All interfaces leading outside of the network should be configured as access interfaces, ensuring
that all CUG interlock codes are generated and used only within this network.
|
Note Interfaces to other networks should be configured as CUG access interfaces, even if no CUGs are configured on the interface. In this case, if you want to exchange SVCs with the neighbor network, permit-unknown-cugs both-directions permanent should be configured. |
Table 2-6 describes the relationship between the Cisco CUG access terminology and ITU-T CUG access terminology.
Examples
The following example shows configuration as a CUG access interface that allows calls from unknown CUGs.
Related Commands
To create a CUG alias, use the atm signalling cug alias global configuration command.
To delete the alias, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
Use this command to configure an alias for the interlock codes. The alias can be used while configuring CUGs on the interface.
An alias can be defined for each CUG interlock code used on the switch. Using an alias simplifies configuration of a CUG on multiple interfaces. When the alias is used, it removes the need to specify the 48-hexadecimal digit CUG interlock code on each interface attached to a CUG member.
Examples
The following example shows how to create the switch_cug CUG alias with the 24-bite interlock code.
Related Commands
To assign a CUG to an interface, use the atm signalling cug assign interface configuration command. To disable this feature, use the no form of this command.
Syntax Description
|
Defaults
If deny-same-cugs is not specified, calls to or from other members of the same CUG are permitted.
If preferential is not specified, the CUG is assigned as a non-preferential CUG.
Command Modes
Command History
Usage Guidelines
Each access interface can be configured to have one or more CUGs associated with it. Only one CUG can be selected as the preferential CUG. Calls received from users attached to this interface can only be associated with the preferential CUG. Calls directed to users attached to this interface can be accepted, based on membership in any of the CUGs configured on this interface.
CUG service can be configured without any preferential CUG. If no preferential CUG is configured on the interface, and calls are permitted from users attached to this interface to unknown users, the calls proceed as non-CUG calls, without generating any CUG IE.
|
Note The CUGs assigned to this interface take effect only when the interface is configured as an access interface (see the atm signalling cug access command for additional information). |
Table 2-7 describes the relationship between the Cisco CUG terminology and the ITU-T CUG terminology.
Examples
The following example shows assignment of the redefined CUG switch router as the preferential CUG on the interface to ATM 2/0/1.
Related Commands
To create a filter table for signalling diagnostics, use the atm signalling diagnostics global configuration command. To disable signalling diagnostics, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
ATM signalling diagnostics is a tool for troubleshooting call failures in the ATM network, and should not be enabled while the switch is operating.
|
Note The atm signalling diagnostics global configuration command changes the configuration mode to ATM signalling diagnostics, and the new prompt appears: Switch(cfg-atmsig-diag)# |
Examples
The following example shows creating filter table 1.
Related Commands
|
To enable the signalling and SSCOP on a port, use the atm signalling enable interface configuration command. To disable signalling and SSCOP on a port, use the no form of this command.
Syntax Description
This command has no arguments or keywords.
Defaults
Command Modes
Command History
Usage Guidelines
ILMI is automatically restarted whenever signalling is enabled or disabled. This command, when used to disable signalling on a PNNI interface, disables both PNNI routing and PNNI signalling.
|
Note This command does not apply to the route processor interface. |
Examples
The following example shows how to disable signalling on ATM 0/1/2.
Related Commands
To allow the mode field in AAL5 IEs to be added when using UNI 3.0, use the atm signalling ie aal5 mode interface configuration command. To disable this feature, use
the no form of this command.
Syntax Description
Defaults
Message mode is passed in UNI 3.0 AAL5 information elements.
Command Modes
Command History
Usage Guidelines
The atm signalling ie aal5 mode interface configuration command allows you to fill in the mode field in AAL5 IEs when using UNI 3.0.
The AAL5 IE has a mode field in UNI version 3.0. This mode field was removed in UNI version 3.1. When a setup request arrives from a UNI 3.1 side connection, the AAL5 IE does not have the mode information. Some vendor switches and end systems reject the connection because the mode information is missing. To allow interoperability, this atm signalling ie aal5 mode interface configuration command allows, by default, a message mode field to be added statically on UNI 3.0 side connections even if one was not received from the other side, for example, from a UNI 3.1 connection.
Examples
The following example configures, in interface configuration mode, ATM interface 1/0/0 signalling IEs in AAL5 to include a mode field configured as message.
Related Commands
To specify which signalling IEs are forwarded from the calling party to the called party, use the
atm signalling ie forward interface configuration command. To stop the transfer of information, use the no form of this command.
Syntax Description
|
Defaults
Forward all IEs in the signalling message from the calling party to the called party.
Command Modes
Command History
Usage Guidelines
When the action indicator in the IE is not set to indicate what action should be taken when an unknown-ie is received, the appropriate action is taken, depending upon whether the unknown-ie is enabled or disabled. If the action indicator is set, then the unknown-ie configuration is ignored.
Examples
The following example shows how to forward the calling party's number to the called party.
To specify the value of VPCI to be carried in the signalling messages within a VP tunnel, use the
atm signalling vpci subinterface configuration command. To use the default configuration, use the
no form of this command.
Syntax Description
Defaults
Use the value of VPI on which the subinterface is established. By default, the VPCI is the same as the VPI on the ATM switch router.
Command Modes
Command History
Usage Guidelines
The atm signalling vpci subinterface command allows you to configure the VPCI to be different from VPI when configuring PVP tunnels.
The connection identifier IE is used in signalling messages to identify the corresponding user information flow. The connection identifier IE contains the VPCI and VCI.
For example, if you want to configure a PVP tunnel connection from a LightStream 1010 ATM switch on VPI 2, VCI X, to a router with a virtual path switch in between, the signalling message would contain connection ID VPI 2, VCI X. Since the PVP tunnel at the router end is on VPI 3, VCI X, the connection will be refused. By configuring VPCI to 3, you can configure the signalling message explicitly to contain connection ID VPI 3, VCI X, instead of containing VPI 2, VCI X.
This command could also be used to support virtual UNI connections.
Examples
The following example configures a PVP tunnel on ATM interface 0/0/0, PVP 99, and then configures the connection ID VCPI as 0 in subinterface configuration mode.
Related Commands
To set the current port snooping configuration and actual register values for the highest ATM interface, use the atm snoop interface atm interface configuration command.
Syntax Description
|
Defaults
Command Modes
Interface configuration on the snoop test port.
Command History
Usage Guidelines
The atm snoop interface atm subcommand applies only if the previously specified port is the highest system port residing on card 4 and subcard 1 (which has been shut down). If so, this enables it as the snoop test port. Cells transmitted from the snoop test port are copies of cells from a single direction of a monitored port.
While in snoop mode, any prior permanent virtual connections to the snoop test port remain in the down state.
The port number of the test port depends on the card type. Table 2-8 defines the snoop test port number for various interfaces.
Examples
The following example configures the highest port in the snoop mode to monitor port card 1, subcard 0, and port 2 in the transmit direction, starting from the configuration mode.
Related Commands
|
To set the current port snooping configuration and actual register values per-VC, use the
atm snoop-vc interface configuration command. To remove a previous configuration, use
the no form of this command.
Syntax Description
|
Defaults
Command Modes
Interface configuration. Applies to the snoop test port.
Command History
Usage Guidelines
There is no restriction on the snoop test port on a switch processor feature card-based system for ATM snoop, snoop-vc, and snoop-vp configurations. The snoop port can be any port and is not limited to the highest port.
The atm snoop-vc interface atm option applies only if the previously specified port is the highest system port residing on card 4 and subcard 1 (which has been shut down) on the snoop test port.
Cells transmitted from the snoop test port are copies of cells from a single direction of a monitored
port. For Catalyst 8510 MSR and LightStream 1010, this restriction is only for FC-PCQ-based systems.
When in snoop mode, any prior permanent virtual connections to the snoop test port remain in the down state.
The port number of the test port depends on the card type. Table 2-9 defines the ATM snoop test port number for various interfaces.
Examples
The following example configures the port in the snoop mode to monitor port card 1, subcard 0, and port 2 in the transmit direction, starting from the configuration mode.
Related Commands
|
To set the current port snooping configuration and actual register values per-VP, use the atm snoop-vp interface configuration command. To remove a previous configuration, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Interface configuration. Applies to the snoop test port.
Command History
Usage Guidelines
There is no restriction on the snoop test port on a switch processor feature card-based system for ATM snoop, snoop-vc, and snoop-vp configurations. The snoop port can be any port and is not limited to the highest port.
The atm snoop-vp interface atm command applies only if the previously specified port is the highest system port residing on card 4 and subcard 1 (which has been shut down) on the snoop test port. Cells transmitted from the snoop test port are copies of cells from a single direction of a monitored port. For Catalyst 8510 MSR and LightStream 1010, this restriction is only for FC-PCQ-based systems.
When in snoop mode, any prior permanent virtual connections to the snoop test port remain in the down state.
The port number of the test port depends on the card type. Table 2-10 defines the ATM snoop test port number for various interfaces.
Examples
The following example configures the port in the snoop mode to monitor port card 1, subcard 0, and port 2 in the transmit direction, starting from the configuration mode.
Related Commands
|
To create a soft PVC on the switch router, use the atm soft-vc interface configuration command.
For existing soft PVCs, use the no form of the command to delete the soft PVC.
To respecify the explicit paths, use the redo-explicit form.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
Obtain the destination port address before configuring a soft PVC by using the show atm interface or show atm addresses command on the destination switch.
The following list identifies why the creation of a soft PVC might be unsuccessful:
Up to three explicit paths can be assigned to a soft VC, using precedence numbers 1 through 3. The precedence 1 explicit path is considered the primary path and is tried first. If it fails, then the next precedence path is tried. Explicit paths can be specified either by name or by identifier.
The explicit path options can be changed without tearing down an existing soft PVC. Use the redo-explicit form of the command to respecify all of the explicit path options.
After configuring a soft PVC, use the show atm vc interface command on the source node (specifying the source VPI and source VCI) to verify that the soft PVC has succeeded and to see the explicit path taken.
|
Note The show configuration displayed for soft connections with explicit paths is always shown as two separate lines, with the redo-explicit keyword on the second line, even if it was originally configured using a single command line. |
Examples
The following example shows how a user at the destination switch displays the address of the destination port.
The following example shows how to configure a soft PVC on interface ATM 0/1/0. At the source switch, create a soft PVC with the following configuration.
The following example shows how to manually configure an explicit path for a soft PVC. For this example, if the explicit path fails, standard routing will be used.
The following example shows how to use the redo-explicit keyword to modify an existing explicit-path configuration to add a second alternate explicit path, and to prevent standard routing from being used should both paths fail. Note that the system prompts you to confirm the changes.
The following example shows how to remove all explicit paths from an existing soft PVC, using the redo-explicit keyword with no other options specified. The path is not changed until a soft PVC reroute occurs.
Related Commands
|
To create a soft PVP on the switch, use the atm soft-vp interface configuration command.
For existing soft PVPs, use the no form of the command to delete the soft PVP.
Use the redo-explicit form of the command to respecify explicit paths.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
Obtain the destination port address before configuring a soft PVP by using the show atm interface or show atm addresses command on the destination switch.
The following list identifies reasons why the creation of a soft PVP is unsuccessful:
Up to three explicit paths can be assigned to a soft VP, using precedence numbers 1 through 3. The precedence 1 explicit path is considered the primary path and is tried first. If it fails, then the next precedence path is tried. Explicit paths can be specified either by name or by identifier.
The explicit path options can be changed without tearing down an existing soft PVP. Use the redo-explicit form of the command to respecify all of the explicit path options.
After configuring a soft PVP, use the show atm vp interface command on the source node (specifying the source VPI) to verify that the soft PVP has succeeded and to see the explicit path taken.
|
Note The show configuration displayed for soft connections with explicit paths is always shown as two separate lines, with the redo-explicit keyword on the second line, even if it was originally configured using a single command line. |
Examples
The following example shows how a user at the destination switch displays the address of the destination port.
At the source switch, create a soft PVP with the VP of 150, the destination port address of 47.0091.8100.0000.0003.be59.ed00.4000.0c82.0010.00, and the destination VPI of 160.
The following example shows how to manually configure an explicit path for a soft PVP. In this example, if the explicit path fails, standard routing is used.
The following example shows how to use the redo-explicit keyword to modify an existing explicit-path configuration to add a second alternate explicit path and to prevent standard routing from being used should both explicit paths fail. Note that the system prompts you to confirm the changes.
The following example shows how to remove all explicit paths from an existing soft PVP by using the redo-explicit keyword, with no other options specified. The path is not changed until a soft PVP reroute occurs.
Related Commands
|
To change the SCRMF, use the atm sustained-cell-rate-margin-factor global configuration command. SCRMF dictates the weight given to PCR in computing the bandwidth used by VBR connections. To assign the default value to SCRMF, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
The following equation is used in the CAC of VBR connections to define the bandwidth requested.
Examples
In the following example, the SCRMF of the switch is set to 35 percent.
Related Commands
To specify the minimum VCI value for the ILMI signalling stack to support for allocation to SVCCs, use the atm svcc vci min interface configuration command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
This command specifies the minimum VCI value used in range negotiation by the ILMI signalling stack for SVCCs. This feature is supported in autoconfiguration and nonautoconfiguration mode.
Examples
The following example illustrates how to set the minimum SVCC VCI value on ATM interface
0/0/1 to 100.
Related Commands
|
To specify the maximum VPI value for the ILMI signalling stack to support for allocation to SVCCs, use the atm svcc vpi max interface configuration command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
This command specifies the maximum VPI value used in range negotiation by the ILMI signalling stack for SVCCs. This feature is supported in autoconfiguration and nonautoconfiguration mode.
|
Note On a bidirectional VCC, the VPI/VCI values used for both directions of the connection are the same at each interface. The same VCI is used for both directions of a connection at an interface. |
Examples
The following example illustrates how to set the maximum SVCC VPI value on ATM interface
0/0/1 to 3.
Related Commands
|
To specify the maximum VPI value for the ILMI signalling stack to support for allocation to SVPCs, use the atm svpc vpi max interface configuration command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
This command specifies the maximum VPI value used in range negotiation by the ILMI signalling stack for SVPCs. This feature is supported in autoconfiguration and non-autoconfiguration mode.
|
Note On a bidirectional VCC, the VPI/VCI values used for both directions of the connection are the same at each interface. The same VCI is used for both directions of a connection at an interface. |
Examples
The following example shows how to set the maximum SVPC VPI value to 3 on ATM interface 0/0/1.
Related Commands
|
To specify the threshold at which the per-connection queue is considered full for CLP discards and EPD, use the atm threshold-group discard-threshold global configuration command. To reset the discard threshold percentage for a particular threshold group to the default value, use the no form of this command.
Catalyst 8510 MSR and LightStream 1010
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
As the threshold group becomes congested (the cumulative number of cells on the queues of VCs in the threshold group approaches the configured max-cells value), the maximum number of cells per queue shrinks from the threshold group max-queue-limit to the min-queue-limit. As the queue size changes, the discard threshold changes, and the installed threshold is made as close as possible to the percent of queue-full specified.
|
Note This command is not available on systems equipped with the FC-PCQ. (Catalyst 8510 MSR and LightStream 1010) |
Examples
The following example shows how to configure threshold group 3 to a discard-threshold of
50 percent.
Related Commands
|
To specify the threshold at which the per-connection queue is considered full for EFCI marking and ABR relative-rate marking, use the atm threshold-group marking-threshold global configuration command. To reset the marking threshold percentage for a particular threshold group to the default value, use the no form of this command.
Syntax Description
|
Defaults
Command Modes
Command History
Usage Guidelines
As the threshold group becomes congested (the cumulative number of cells on the queues of VCs in the threshold group approaches the configured max-cells value), the maximum number of cells per queue shrinks from the threshold group max-queue-limit to the min-queue-limit. As the queue size changes, the marking threshold changes, and the installed threshold is made as close as possible to the percent of queue-full specified.
|
Note This command is not available on systems equipped with the FC-PCQ. (Catalyst 8510 MSR and LightStream 1010) |
Examples
The following example shows how to configure threshold group 3 to to a marking-threshold of
50 percent.
Related Commands
|
To specify the maximum number of cells queued for all connections that are members of a specified threshold group, use the atm threshold-group max-cells global configuration command. To reset the maximum cell count for a particular threshold group to the default value, use the no form of this command.
Catalyst 8510 MSR and LightStream 1010
Syntax Description
|
|
Defaults
Command Modes
Command History
Usage Guidelines
As the threshold group becomes congested (the cumulative number of cells on the queues of VCs in the threshold group approaches the configured max-cells value), the maximum number of cells per queue shrinks from the threshold group max-queue-limit to the min-queue-limit.
The hardware does not provide all possible max-cell values in the range. Rather, the value used is the closest number of cells greater than that specified. The possible values are {(64*i)-1, 1<=i<=1024}. The installed value can be displayed using the show atm resource command.
|
Note This command is not available on systems equipped with the FC-PCQ. (Catalyst 8510 MSR and LightStream 1010) |
Examples
The following example shows how to set threshold-group 3 to a maximum cell count of 32000.
Related Commands
|
To set the largest per-VC queue limit for a specified threshold group, use the atm threshold-group max-queue-limit global configuration command. To reset the maximum queue limit for a particular threshold group to the default value, use the no form of this command.
Catalyst 8510 MSR and LightStream 1010
Syntax Description
|
Defaults
Depends on the threshold group.
Command Modes
Command History
Usage Guidelines
As the threshold group becomes congested (the cumulative number of cells on the queues of the VCs in the threshold group approaches the configured max-cells value), the maximum number of cells per queue shrinks from the threshold group max-queue-limit to the min-queue-limit.
The hardware does not provide all possible max-queue-limit values in the range. Rather, the value used is the closest number of cells greater than that specified. The possible values are
{(16 * i) -1, 2 <= i <= 1024}. The installed value can be displayed using the show atm resource command.
|
Note This command is not available on systems equipped with the FC-PCQ. (Catalyst 8510 MSR and LightStream 1010) |
Examples
The following example shows how to set threshold-group 3 to a maximum queue limit of 16383.
Related Commands
|
To set the smallest per-VC queue limit for a specified threshold group, use the
atm threshold-group min-queue-limit global configuration command. To reset the minimum queue limit for a particular threshold group to the default value, use the no form of this command.
Catalyst 8510 MSR and LightStream 1010
Syntax Description
|
Defaults
Depends on the threshold group.
Command Modes
Command History
Usage Guidelines
As the threshold group becomes congested (the cumulative number of cells on the queues of VCs in the threshold group approaches the configured max-cells value), the maximum number of cells per-queue shrinks from the threshold group max-queue-limit to the min-queue-limit.
|
Note This command is not available on systems equipped with the FC-PCQ. (Catalyst 8510 MSR and LightStream 1010) |
Examples
The following example shows how to set threshold-group 3 to a minimum queue limit of 31.
Related Commands
|
To specify the name associated with a threshold group number, use the atm threshold-group name global configuration command. To reset the name of a particular threshold group to the default value, use the no form of this command.
Syntax Description
|
|
Defaults
1 - cbr-default
2 - vbrrt-default
3 - vbrnrt-default
4 - abr-default
5 - ubr-default
Command Modes
Command History
Usage Guidelines
You cannot rename the well-known VC threshold group.
|
Note This command is not available on systems equipped with the FC-PCQ. |
Examples
The following example shows how to change the name of threshold group 3 to bigq.
Related Commands
To assign a service category to a threshold group, use the atm threshold-group service global configuration command. To reset the association of a particular service category to a threshold group, use the no form of this command.
Syntax Description
|
|
Defaults
atm threshold-group service cbr 1
atm threshold-group service vbr-rt 2
atm threshold-group service vbr-nrt 3
atm threshold-group service abr 4
atm threshold-group service ubr 5
Command Modes
Command History
Usage Guidelines
This command is not available on systems equipped with the FC-PCQ. (Catalyst 8510 MSR and LightStream 1010)
Examples
The following example shows how to set the threshold group to use subsequently in connection setup for CBR connections to group 3.
Related Commands
To define an ATM map statement for a PVC, use the atm-vc map-list configuration command in conjunction with the map-list global configuration command. To remove the address, use the
no form of this command.
Syntax Description
|
Defaults
No map statements are defined.
Command Modes
Command History
Usage Guidelines
This command is required with the map-list command when you are configuring an SVC.
Examples
The following example shows how to create a map-list named atm, followed by a map statement for the protocol address being mapped.
Related Commands
Posted: Tue Aug 12 17:49:55 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.