|
|
The commands shown in this chapter apply to the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010. Where an entire command or certain attributes of a command have values specific to a particular switch, an exception is indicated by the following callouts:
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.
atm abr-mode {efci | relative-rate | all}
efci | When cells arrive on ABR connections to a congested (as indicated by the efci threshold) output queue on the interface, the efci bit in the cell header is set. |
relative-rate | When a backward RM cell is received on an ABR connection on an interface (from outside the switch), its congestion bit is set if the forward-direction interface is congested (as indicated by the abr relative-rate threshold). |
all | Indicates both efci and relative-rate modes of congestion notification. |
relative-rate
Global configuration
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.
In the following example, the ABR mode of the switch is set to efci.
Switch(config)# atm abr-mode efci
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.
atm access-group name [in | out]
name | The filter expression or filter set. |
in | Indicates you should apply the filter to an incoming SETUP message. |
out | Indicates you should apply the filter to an outgoing SETUP message. |
out
Interface configuration
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, atm filter-set, and atm template-alias global configuration commands.
Each interface has only one access group. If you create a new access group, it overrides any existing group.
The following is sample output from the atm access-group command.
Switch(config-if)# atm access-group atm_filter_expr1 in Switch(config-if)# atm access-group atm_filter_expr2 out
atm filter-expr
atm filter-set
atm template-alias
show atm filter-expr
show atm filter-set
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.
atm accountingThis command has no keywords or arguments.
Disabled
Interface configuration
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.
The following example shows how to enable ATM accounting on interface ATM 1/0/0.
Switch(config)# interface atm 1/0/0 Switch(config-if)# atm accounting
To control collection of ATM accounting data into a specific file, use the atm accounting collection EXEC command.
atm accounting collection {collect-now | swap} filename
collect-now | Immediately captures ATM accounting information for all connections that meet the min-age criteria. |
filename | Specifies the name for the ATM accounting file. |
swap | Stops the data collection in the active file and activates the passive file so it collects data. The new passive file is now available for downloading. |
Privileged EXEC
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.
The following example shows how to perform an on-demand collection to the file acctng_file1.
Switch# atm accounting collection collect-now acctng_file1 Switch# Collect-now found 12 SVCs with life longer than min-age
The following example shows how to perform a swap operation on the file acctng_file1.
Switch# atm accounting collection swap acctng_file1 Switch# File Swap Done. New Ready File 4999702 bytes (#records 28796); Active File 65 bytes (#records 0)
To globally enable the ATM VC accounting feature, use the atm accounting enable global configuration command. To disable this feature, use the no form of this command.
atm accounting enableThis command has no keywords or arguments.
Disabled
Global configuration
Accounting is enabled globally for the switch on interfaces for which 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 must have this command saved in the NVRAM configuration file. Use the following steps to enable ATM accounting:
Step 1 Enable ATM accounting in global configuration mode.
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.
The following example shows enabling ATM accounting.
Switch(config)# atm accounting enable
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.
atm accounting file filenameSwitch(config-acct-file)# appears.
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.
collection-modes [periodic] [on-release]
filename | Specifies the filename of the accounting file. |
See "Syntax Description."
Global configuration
The ATM accounting configuration mode subcommands are described in Table 2-1.
| Subcommand | Description |
|---|---|
collection-modes | Initializes the collection mode and allows you to specify at what time accounting data is recorded in the file: on the release of a connection (on-release) or periodically (periodic). |
default | Sets a parameter to its defaults. |
description | Configures a description of the ATM accounting file with a limit of 64 characters. |
enable | Activates ATM accounting data collection to a specified file. |
failed-attempts | Configures the writing of records for initial connection attempts, as follows:
Default is regular and soft. |
interval | Sets the period for periodic collection of accounting records. The default is 3600 seconds. |
min-age | Configures the value of the minimum age of the VC for on-release or periodic collection of accounting records. The default is 3600 seconds. |
remote-log | Establishes a TCP connection from the switch to a PC or workstation, as follows:
|
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:
The following example shows how to enter the ATM accounting file configuration mode.
Switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# atm accounting file acctng_file1 Switch(config-acct-file)#
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.
Switch(config)# atm accounting file acctng_file1 Switch(config-acct-file)# description Main accounting file for engineering
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.
Switch(config)# atm accounting file acctng_file1 Switch(config-acct-file)# failed-attempts regular
The following example shows how to enter the ATM accounting file configuration mode and configure remote-log.
Switch(config)# atm accounting file acctng_file1 Switch(config-acct-file)# remote-log 172.20.52.3 6001 alternate-host cisco-lab 7001
atm accounting collection
atm accounting selection
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.
atm accounting selection indexSwitch(config-acct-sel)# appears.
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.
connection-types [type]
index | Configures the ATM accounting selection index number. |
No default selection index. See the individual subcommand defaults.
Global configuration
This release supports only one ATM selection table entry which cannot be deleted.
The following example shows specifying the ATM accounting selection index as 1 and returning to the default connection types.
Switch# configure terminal Switch(config)# atm accounting selection 1 Switch(config-acct-sel)# default connection-types
atm accounting collection
atm accounting file
connection-types
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.
atm accounting trap threshold percent-value
percent-value | Specifies the value as a percent of the maximum file size. |
The default value for the trap threshold is 90.
Global configuration
To see the file size, threshold value, and trap statistics, use the show atm accounting EXEC command.
The following example shows changing the ATM accounting trap threshold to 80.
Switch(config)# atm accounting trap threshold 80
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.
atm address address-template
address-template | The address template can be a full 20-byte address or a partial 13-byte. When a partial address is assigned, this command automatically sets one of the switch's 6-byte MAC addresses in the ESI part, and puts a 0 in the selector part. |
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.
Global configuration
You can have multiple ATM addresses. The first address in the list is the active ATM address for this switch. When you delete the current active ATM address, the next address in the list becomes the active ATM address.
In autoconfiguration mode, the switch 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 (refer to the ATM Switch Router Software Configuration Guide for more information).
In autoconfiguration mode, all switches have the same peer group identifier based on the first 7 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.
The following example shows how to assign a 20-byte ATM address to the switch.
Switch# configure terminal Switch(config)# atm address 47.009181000000000000000001
The following example shows the steps 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 1 Configure the desired new address or prefix to be added to the list of ATM addresses for the switch.
Switch# configure terminal Switch(config)# atm address 47.00918100002
Step 2 Determine the current active ATM address by using the show atm address 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.
Switch(config)# no atm address 47.00918100000000400B003081.00400B003081.00
Step 3 (Optional) Update all PNNI local-node identifiers by disabling and reenabling local-node 1.
Switch(config)# atm router pnni Switch(config-atm-router)# node 1 disable Switch(config-pnni-node)# node 1 enable
Step 4 (Optional) Save the running configuration to be used as the startup configuration in the event of a reboot.
Switch# copy running-config startup-config
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.
atm address-registration [permit {all | matching-prefix [wellknown-groups | all-groups]}]
all | Permit all AESAs registered by attached end systems. |
matching-prefix | Permit AESAs where the first 13 bytes of the address match an ILMI prefix used on the interface. These ILMI prefixes can be configured using the global atm address command or the per-interface atm prefix command. The ILMI prefixes used on the interface can be shown using the show atm ilmi-status command. |
wellknown-groups | Permit well-known group addresses assigned by the ATM Forum and AESAs that match an ILMI prefix used on the interface. The well-known group addresses include the old LECS address (47.0079.0000.0000.0000.0000.0000.00A0.3E00.0001.00) and any address matching the ATM Forum address prefix for well-known addresses. (C5.0079.0000.0000.0000.0000.0000.00A0.3E) |
all-groups | Permit all group addresses, including the well-known group addresses, and the AESAs that match an ILMI prefix used on the interface. |
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 global configuration command atm ilmi default-access permit.
Interface configuration
This command does not apply to the ATM 0 interface.
This 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, so you can allow or deny certain ILMI registered addresses. If specified, the per-interface access filter overrides the global default access filter for ILMI address registration.
If you want to allow certain addresses to be registered via ILMI, but want 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 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.
The following example disables ILMI address registration on ATM interface 1/0/0.
Switch(config)# interface atm 1/0/0 Switch(config-if)# no atm address-registration
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.
Switch(config)#interface atm 1/0/0Switch(config-if)#atm address-registration permit matching-prefix wellknown-groups%ATM-5-ILMIACCFILTER: New access filter setting will be applied to registration of new addresses on ATM1/0/0.
atm address
atm ilmi default-access permit
atm ilmi-enable
atm prefix
show atm ilmi-status
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.
atm arp-server [self [time-out minutes] | nsap nsap-address]
self | Specifies the current switch as the ATM ARP server. |
minutes | Number of minutes a destination entry listed in the ATM ARP server's ARP table is kept before the server takes any action to verify or time out the entry. |
nsap-address | NSAP address of an ATM ARP server. |
The ARP server process is disabled. The default timeout value is 20 minutes.
Interface configuration
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."
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.
atm auto-configurationThis command has no arguments or keywords.
Enabled
Interface configuration
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 uni, 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.
The following example shows how to enable ILMI autoconfiguration on interface ATM 0/1/2.
Switch(config)# interface atm 0/1/2 Switch(config-if)# atm auto-configuration Switch(config-if)# %ATM-5-ATMSOFTSTART:Restarting ATM signalling and ILMI on ATM0/1/2
atm iisp
atm ilmi-enable
atm maxvci-bits
atm maxvpi-bits
atm nni
atm routing-mode
atm uni
show atm ilmi-status
show atm interface
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.
atm backward-max-burst-size-clp0 cell-count
cell-count | Maximum number of high-priority cells coming from the destination switch at the burst level. |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
The following example sets the maximum number of high-priority cells coming from the destination switch at the burst level to 800 cells.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm backward-max-burst-size-clp0 800
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.
atm backward-max-burst-size-clp1 cell-count
cell-count | Maximum number of the aggregate of low- and high-priority cells coming from the destination at the burst level. |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
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.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm backward-max-burst-size-clp1 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 value, use the no form of this command.
atm backward-peak-cell-rate-clp0 rate
rate | Maximum rate in kbps that this SVC can receive high-priority cells from the destination switch. Maximum upper range is 7113539 (limited by 0xffffff cells per second). |
The parameter is not specified in the SVC setup request.
Map-class configuration
This command defines a traffic parameter for the SVC connection.
The keyword clp0 indicates that this command affects only cells with a CLP of 0 (high-priority cells).
The following example sets the peak rate for high-priority cells from the destination switch to 8000 kbps.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm backward-peak-cell-rate-clp0 8000
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.
atm backward-peak-cell-rate-clp1 rate
rate | Maximum rate in kbps that this SVC can receive of the aggregate of low- and high-priority cells from the destination switch. Maximum upper range is 7113539 (limited by 0xffffff cells-per-second). |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
The following example sets the peak rate of the aggregate of low- and high-priority cells from the destination switch to 7000 kbps.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm backward-peak-cell-rate-clp1 7000
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.
atm backward-sustainable-cell-rate-clp0 rate
rate | Sustainable rate in kbps that this SVC can receive high-priority cells from the destination switch. Maximum upper range is 7113539 (limited by 0xffffff cells per second). |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
The following example sets the sustainable rate for high-priority cells from the destination switch to 800 kbps.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm backward-sustainable-cell-rate-clp0 800
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.
atm backward-sustainable-cell-rate-clp1 rate
rate | Sustainable rate in kbps that this SVC can receive of the aggregate of low- and high-priority cells from the destination. Maximum upper range is 7113539 (limited by 0xffffff cells per second). |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
The following example sets the sustainable rate of the aggregate of low- and high-priority cells from the destination switch to 700 kbps.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm backward-sustainable-cell-rate-clp1 700
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.
atm cac link-sharing max-guaranteed-service-bandwidth {receive | transmit} percentTo change the best-effort interface connection limit, use the atm cac best-effort-limit command. To disable the best-effort limit, use the no form of this command.
atm cac best-effort-limit conn-valueTo permit or deny a service category on an ATM physical interface or shaped 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.
atm cac service-category {cbr | vbr-rt | vbr-nrt | abr | ubr} {permit | deny}To change the interface maximum for individual traffic parameters allowed on connection setup, use the following commands. To reset the maximum value to the default, use the no form of these commands.
atm cac max-cdvt {cbr | vbr | abr | ubr} {receive | transmit} cdvtval
receive | The configured parameter applies to the flow of traffic into the switch on the interface (or from the route processor 0 interface). |
transmit | The configured parameter applies to the flow of traffic out of the switch on the interface (or to the route processor 0 interface). |
percent | The percent of interface bandwidth, from 0 to 95 percent. |
cbr | The constant bit rate connection. |
vbr | The variable bit rate connection. |
abr | The available bit rate connection. |
ubr | The unspecified bit rate connection. |
conn-value | The number of best-effort connections allowed on the interface, in the range of 0 to 32768. |
permit | Permit the specified service category on the interface. |
deny | Deny the specified service category on the interface. |
cdvtval | The value of the cell delay variation tolerance, in the range of 0 to 2147483647, expressed in cell times (2.72 microseconds at 155.2 Mbps). |
mbsval | The value of the maximum burst size, in the range of 0 to 2147483647, expressed as the number of cells. |
rate | A positive integer, measured in kbps, in the range of 0 to 910533065. |
No link-sharing, best-effort limits, or traffic parameter limits. On a physical interface, all service categories are permitted; on a shaped VP tunnel, only CBR is supported.
Interface configuration
You can configure the link-sharing parameter only on physical ports 0 or 6 on a 25-Mbps port adapter.
Use the atm cac commands to tune parameters used in the connection admission control functions performed by resource management. The four types of parameters, which are configured per interface, are described in Table 2-2. Any changes to these parameters only affect subsequent connection setups.
| Parameter | Description |
|---|---|
link sharing | 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 aggregate (AGG) of CBR and VBR. Minimums can be specified for CBR, VBR, ABR, or UBR+. These parameters, for a direction, are interrelated as follows (assuming these parameters are defined):
|
best-effort-limit | A limit on the total number of ABR and UBR connections on the interface. |
service-category | 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. |
max-cdvt | Specifies the maximum traffic parameters that are allowed at VC setup. These can be specified independently by service category and traffic direction. |
To deny a service category in a shaped VP tunnel subinterface, you must delete all user VCs of the service category on the interface.
UBR connections are normally not rejected by CAC due to the value specified for peak cell rate. By specifying a peak-cell-rate limit, CAC rejects connections that exceed the limit.
The following commands are a subset of the interface configuration and are supported for the subinterface configuration:
atm cac best-effort-limitThe following command is not supported for the subinterface configuration:
atm cac link-sharingIn the following example, a peak-cell-rate traffic parameter limit of 3001 kbps is defined for ABR connections in the receive direction on the interface.
Switch(config-if)# atm cac max-peak-cell-rate abr receive 3001
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.
Switch(config-if)# atm cac link-sharing max-bandwidth vbr transmit 61
In the following example, the number of best-effort connections allowed on the interface is limited to 200.
Switch(config-if)# atm cac best-effort-limit 200
In the following example, the CBR service category is denied on ATM subinterface 0/0/1.51 before service category UBR is permitted.
Switch(config)# interface atm 0/0/1.51 Switch(config-subif)# atm cac service-category cbr deny Switch(config-subif)# atm cac service-category ubr permit
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.
atm cdvt-default {cbr | vbr-rt | vbr-nrt | abr | ubr} num
num | This parameter is an integer, with a range of 0 to 2147483647. The CDVT is expressed in cell-times (2.72 microseconds at 155.2 Mbps). |
1024
Interface configuration
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 and the defaults specified on the interface should be used.
The following example shows changing the default CDVT for received cells on VBR-RT connections.
Switch(config-if)# atm cdvt-default vbr-rt 4000
atm connection-traffic-table-row
show atm vc
show atm vp
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.
atm connection-traffic-table-row [index row-index] cbr pcr rate [cdvt cdvt]
cdvt cdvtval | The value of the cell delay variation tolerance, in the range of 0 to 2147483647, expressed in cell-times (2.72 microseconds at 155.2 Mbps). |
mbs mbsval | The value of the maximum burst size, in the range of 0 to 2147483647, expressed in the number of cells. |
mcr mcrval | The minimum cell rate is a positive integer, measured in kbps, in the range of 0 to 910533065. |
pcr rate | The peak cell rate is a positive integer, measured in kbps, in the range of 0 to 910533065. |
row-index | An integer in the range of 1 to 1073741823. |
scr0 | Sustained cell rate for the CLP 0 flow. |
scr10 | Sustained cell rate for the CLP 0+1 flow. |
scrval | The sustained cell rate is a positive integer, measured in kbps per second, in the range of 0 to 910533065. |
Rows 1 through 6 in the table are predefined.
Global configuration
This command sets up the traffic characteristics used in PVC definition. The characteristics are stored as rows of a table. The row index is referenced when a PVC is created using the atm pvc interface command.
When 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-signalable cell-rate (the maximum cell-rate that fits in 24 bits).
When an ABR row is configured, if MCR is not specified, MCR is configured as 0 in the CTT row.
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.
In the following example, a CBR CTT row is defined with an index of 200 and a peak cell rate of 7743 kbps.
Switch(config)# atm connection-traffic-table-row index 200 cbr pcr 7743
atm pvc
atm pvp
show atm connection-traffic-table
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.
atm e164 address e164-address
e164-address | Specifies a native E.164 address, consisting of 7 to 15 decimal digits. Refer to the ITU-T Recommendation E.164 for more information on the syntax and semantics of native E.164 addresses. |
Interface configuration
Use this command to configure a native E.164 address 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 this interface that specify this 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 received called and calling party subaddresses as the new called and calling party addresses.
This 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.
The following example shows setting the native E.164 address of ATM 0/0/1 to 1341457.
Switch(config)# interface atm 0/0/1 Switch(config-if)# atm e164 address 1341457
atm route
show atm addresses
show atm interface
show atm vc
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.
atm e164 auto-conversionThis command has no keywords or arguments.
Interface configuration
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.
The following example shows how to enable E.164 autoconversion on ATM interface 0/0/1.
Switch(config)# interface atm 0/0/1 Switch(config-if)# atm e164 auto-conversion
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.
atm e164 translationThis command has no keywords or arguments.
Interface configuration
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 not providing 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.
The following example shows setting interface ATM 0/0/1 to use the E.164 translation table.
Switch(config)# interface atm0/0/1 Switch(config-if)# atm e164 translation
atm e164 auto-conversion
atm e164 translation-table
atm route
e164 address
show atm interface
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.
atm e164 translation-tableSwitch(config-atm-e164)# appears.
This command has no keywords or arguments.
Global configuration
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.
The following example shows starting ATM E.164 translation configuration mode.
Switch(config)# atm e164 translation-table Switch(config-atm-e164)# e164 address 1112222 nsap-address 11.111122223333444455556666.112233445566.11
atm e164 translation
e164 address
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 via ILMI address registration from the ATM switch router. To delete the end station address, use the no form of this command.
atm esi-address esi.selector
esi | End station ID field value in hexadecimal; 6 bytes long. |
selector | Selector field value in hexadecimal; 1 byte long. |
No end station ID is defined for this interface.
Interface configuration
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.
The following example sets the ESI to 303132333435 and the selector byte to 36 on ATM subinterface 0.1.
Switch(config)# interface atm 0.1 Switch(config-subif)# atm esi-address 303132333435.36
atm address
atm nsap-address
atm prefix
To configure an ATM address filter that matches patterns, use the atm filter-expr global configuration command. To delete the specified filter, use the no form of this command.
atm filter-expr name term
name | The name of the pattern-matching filter expression. |
term | Can be any of the following: · A previously defined address pattern-matching expression · A filter set applied to a calling-party address---source filter-set name · A filter set applied to a called-party address---destination filter-set name |
Permit
Global configuration
The first form listed defines a simple filter expression that is pattern-matched only if the pattern given by term is matched.
The second form defines a filter expression that is pattern-matched only if the pattern given by term is not matched.
The third form defines a filter expression that is pattern-matched if either of the patterns given by the two terms are matched.
The fourth form defines a filter expression that is pattern-matched only if both of the patterns given by the two terms are matched.
The fifth form 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.
The following is sample output from the atm filter-expr command.
Switch(config)# atm filter-expr atm_filter_expr1 not source atm_filter_set1 Switch(config)# atm filter-expr atm_filter_expr2 source atm_filter_set1 and destination atm_filter_set2
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.
atm filter-set name [index [number]] [permit | deny] [template | time-of-day
name | The name of the filter set. |
index | Set order in which filters are set. The range is from 1 through 65535. The default is 1. |
permit | Permission to accept an incoming call or forward an outgoing call on an interface/subinterface if the address pattern-matching succeeds. |
deny | Denial to accept an incoming call or forward an outgoing call on an interface or subinterface if the address pattern-matching succeeds. |
template | An ATM address, address template, or ATM address template alias. |
time-of-day | Specify the time range in which the filter set takes place. This parameter can be specified as anytime or as a specific time. The default is anytime. |
start-time | Specify the time the filter set starts, in 24-hour format, hh:mm:ss. |
end-time | Specify the time the filter set ends, in 24-hour format, hh:mm:ss. |
Permit
Global configuration
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.
The following is an example of the atm filter-set command.
Switch(config)# atm filter-set filter_set1 permit 47.0091.8100.0000.0003.bbe4.aa01.4000.0c80.0000.64 Switch(config)# atm filter-set filter_set3 deny 47.840F... Switch(config)# no atm filter-set filter_set3
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.
atm forward-max-burst-size-clp0 cell-count
cell-count | The burst size in cells, from 1 to 16777215. This is the maximum number of high-priority cells going from the source switch at the burst level. |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
The following example sets the maximum number of high-priority cells going from the source switch at the burst level to 100000.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm forward-max-burst-size-clp0 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.
atm forward-max-burst-size-clp1 cell-count
cell-count | The burst size in cells, from 1 to 16777215. This is the maximum number of the aggregate of low- and high-priority cells going from the source switch at the burst level. |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
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.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm forward-max-burst-size-clp1 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.
atm forward-peak-cell-rate-clp0 rate
rate | Maximum rate in kbps that this SVC can send high-priority cells from the source switch. The maximum upper range is 7113539 (limited by 0xffffff cells per second). |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
The following example sets the peak of the high-priority cell rate from the source switch to
1000 kbps.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm forward-peak-cell-rate-clp0 1000
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.
atm forward-peak-cell-rate-clp1 rate
rate | Maximum rate in kbps that this SVC can send the aggregate of low- and high-priority cells from the source. The maximum upper range is 7113539 (limited by 0xffffff cells per second). |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
The following example sets the peak of the aggregate of low- and high-priority cell rate from the source switch to 100000 kbps.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm forward-peak-cell-rate-clp1 100000
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.
atm forward-sustainable-cell-rate-clp0 rate
rate | Sustainable rate in kbps that this SVC can send high-priority cells from the source. The maximum upper range is 7113539 (limited by 0xffffff cells per second). |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
The following example sets the sustainable rate of high-priority cells from the source switch to 100000 kbps.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm forward-sustainable-cell-rate-clp0 100000
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.
atm forward-sustainable-cell-rate-clp1 rate
rate | Sustainable rate in kbps that this SVC can send of the aggregate low- and high-priority cells from the source. The maximum upper range is 7113539 (limited by 0xffffff cells per second). |
The parameter is not specified in the SVC setup request.
Map-class configuration
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).
The following example sets the sustainable rate of high-priority cells from the source switch to 100000 kbps.
Switch(config)# map-class atm high-rate Switch(config-map-class)# atm forward-sustainable-cell-rate-clp1 100000
To enable hierarchical scheduling, use the atm hierarchical-tunnel global configuration command. To disable hierarchical scheduling, use the no form of this command.
atm hierarchical-tunnelThis command has no arguments or keywords.
Disabled
Global configuration
Hierarchical VP tunnels have dedicated schedulers, which make possible the simultaneous support of all service category circuits inside the tunnel. The overall output of the tunnel rate is limited to the total output of the dedicated scheduler.
Hierarchical VP tunnels are supported only if FC-PFQ is installed. (Catalyst 8510 MSR and LightStream 1010)
When you enable hierarchical scheduling, it impacts the behavior of the CAC software on the switch. For example, enabling hierarchical scheduling can cause CAC software to refuse admission to some connections, even though those same connections were admitted before hierarchical scheduling was enabled.
If hierarchical scheduling is enabled, and if there are any guaranteed service VCs defined (or signalled) with a guarantee less than 76.114 kbps, those guaranteed service VCs are allocated a full rate of 76.114 kbps. Guaranteed service connections include:
If hierarchical scheduling is disabled, the guaranteed service VC rate is 38.057 kbps.
Guaranteed service VCs are allocated more bandwidth after hierarchical scheduling is enabled, which affects the CAC of those VCs. You can compute the extra bandwidth that is being allocated and evaluate the effect this has on the interface CAC before enabling hierarchical scheduling.
Best-effort VCs, or VCs with guarantees larger than 76.114 kbps, do not affect the behavior of the switch.
The following example shows how to enable hierarchical scheduling on an ATM switch router.
Switch# configure terminal Switch(config)# atm hierarchical-tunnel Switch(config)# end Switch# reload
To change the idle timer for SVCs on an interface that will cause the SVCs to disconnect when inactive for a specified interval, use the atm idle-timeout interface configuration command. To return to the default setting, use the no form of this command.
atm idle-timeout seconds
seconds | Number of seconds the SVC can be inactive before disconnecting. |
300 seconds
Interface configuration. This command applies only to the route processor interface (ATM 0).
To disable idle timeouts, set the value of seconds to 0.
The following example shows setting the timeout to 250.
switch(config)# atm idle-timeout 250
To configure ATM IISP on the specified physical or logical (VP tunnel) port, use the atm iisp interface configuration command.
atm iisp [side side [version ver]] | [version ver [side side]]
side | Interface side, specified as user or network. The default is network. |
version | IISP version, specified as 3.0, 3.1, or 4.0. The default is 3.0. |
See "Syntax Description."
Interface configuration
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, 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, atm nni, and atm uni 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 (see the atm route command).
The following example configures ATM interface 3/1/2 as an IISP interface, running version 3.0 as the user side.
Switch(config)# interface atm 3/1/2 Switch(config-if)# no atm auto-configuration Switch(config-if)# %ATM-6-ILMINOAUTOCFG: ILMI(ATM3/1/2): Auto-configuration is disabled, current interface parameters will be used at next interface restart. Switch(config-if)# atm iisp side user version 3.0 Switch(config-if)# %ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM3/1/2. Switch(config-if)# atm maxvci-bits 12 Switch(config-if)# %ATM-5-ATMSOFTSTART:# Restarting ATM signalling and ILMI on ATM3/1/2. Switch(config-if)# end
The following example configures subinterface ATM 3/1/3.100 as an IISP interface, and uses the defaults for this command.
Switch(config)# interface atm 3/1/3.100 Switch(config-subif)# no atm auto-configuration Switch(config-subif)# %ATM-6-ILMINOAUTOCFG: ILMI(ATM3/1/3.100): Auto-configuration is disabled, current interface parameters will be used at next interface restart. Switch(config-subif)# atm iisp Switch(config-subif)# %ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM3/1/3.100.
atm auto-configuration
atm nni
atm route
show atm interface
show atm route
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.
atm ilmi default-access permit {all | matching-prefix [wellknown-groups | all-groups]}
all | Permit all AESAs registered by attached end systems. |
matching-prefix | Permit AESAs where the first 13 bytes of the address match an ILMI prefix used on the interface. These ILMI prefixes can be configured using the global atm address command or the per-interface atm prefix command. The ILMI prefixes used on the interfaces can be shown using the show atm ilmi-status command. |
wellknown-groups | Permit well-known group addresses assigned by the ATM Forum and AESAs that match an ILMI prefix used on the interface. The well-known group addresses include the old LECS address (47.0079.0000.0000.0000.0000.0000.00A0.3E00.0001.00) and any address matching the ATM Forum address prefix for well known addresses. (C5.0079.0000.0000.0000.0000.0000.00A0.3E) |
all-groups | Permit all group addresses, including the well-known group addresses, and AESAs that match an ILMI prefix used on the interface. |
permit all
Global configuration
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 (see the atm address-registration command for additional information).
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 via 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 for additional information).
The following example shows how to permit all ILMI-registered addresses.
Switch(config)# atm ilmi default-access permit all Switch(config)# %ATM-5-ILMIDEFACCFILTER: New global default access filter setting will be applied to registration of new addresses on interfaces using global default access filter.
atm address
atm address-registration
atm prefix
summary-address
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.
atm ilmi-enableThis command has no arguments or keywords.
Enabled
Interface configuration
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.
The following example shows how to disable ILMI on interface ATM 1/0/0.
Switch(config)# interface atm 1/0/0 Switch(config-if)# no atm ilmi-enable
atm address-registration
atm auto-configuration
atm ilmi-keepalive
show atm ilmi-status
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.
atm ilmi-keepalive [seconds [retry number]]
seconds | Period in seconds, from 1 to 65,535, when the IME is polled. The default is 5 seconds. |
number | Number of retries from 2 to 5. The default is 5 retries. |
Disabled
Interface configuration
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.
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.
Switch(config)# interface atm 1/0/0 Switch(config-if)# atm ilmi-keepalive 4 retry 3
atm ilmi-enable
show atm ilmi-status
To configure the LECS address advertised by the switch to the end system, use the atm lecs-address interface configuration command.
atm lecs-address lecsaddress [sequence#]
lecsaddress | Address of the LAN Emulation configuration server. |
sequence# | Sequence number of the LECS. |
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.
Interface configuration
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.
atm lecs-address-default
show atm ilmi-configuration
To configure the LECS address advertised by the switch to the end system, use the atm lecs-address-default global configuration command.
atm lecs-address-default lecsaddress [sequence #]
lecsaddress | Address of the LAN Emulation configuration server. |
sequence # | Sequence number of the LECS. |
Global configuration
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.
atm lecs-address
show atm ilmi-configuration
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.
atm link-distance p-value
p-value | Specified in units of kilometers, which is then divided by the speed of light in kbps to derive a propagation delay in microseconds (0 to 65535). |
0
Interface configuration
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.
To create and delete well-known (reserved) PVCs with non-default connection identifiers or other non-default 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.
atm manual-well-known-vc [delete | keep]
delete | When specified, the existing automatically created VCs are deleted. If well-known VCs exist, you are prompted to confirm that the VC can be automatically deleted. If you reply no, the command stops abruptly. |
keep | When specified, the existing automatically created well-known VCs remain in place and appear in the running configuration. |
The keep option becomes the default on existing automatically created VCs when manual mode is entered.
Interface configuration
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 startup-config command 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.
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.
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.
Switch(config-if)# atm manual-well-known-vc keep Switch(config-if)# no atm pvc 0 5 Switch(config-if)# atm pvc 0 7 interface atm 0 0 any-vci encap qsaal
atm pvc
copy running-config startup-config
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.
atm maxvc-number max-vc-num
max-vc-num | Maximum number of supported virtual channels. Configures the maximum number of virtual channels supports (0 to 32768). |
32768 virtual channels
Interface configuration
Before using this command, the interface must be administratively shut down.
The following example sets the maximum number of ATM virtual channels supported on interface ATM 0/0/0 to 8000.
Switch(config)# interface atm 0/0/0 Switch(config-if)# shutdown Switch(config-if)# atm maxvc-number 8000
atm maxvci-bits
atm pvc
show atm interface
shutdown (interface)
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.
atm maxvci-bits max-vci-bits
max-vci-bits | Maximum number of active bits supported on an ATM interface. Configures the maximum number of VCI bits (0 to 14). |
14 bits
Interface configuration
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 VCI bits, 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 following example sets the maximum number of active VCI bits to 10 for interface ATM 0/0/0.
Switch(config)# interface atm 0/0/0 Switch(config-if)# no atm auto-configuration Switch(config-if)# %ATM-6-ILMINOAUTOCFG: ILMI(ATM0/0/0): Auto-configuration is disabled, current interface parameters will be used at next interface restart. Switch(config-if)# atm maxvci-bits 10 Switch(config-if)# %ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM0/0/0.
atm auto-configuration
atm connection-traffic-table-row
atm maxvc-number
atm pvc
show atm interface
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.
atm maxvp-number max-vp-no
max-vp-no | Maximum number of supported virtual paths. Configures the maximum number of virtual paths supported, 0 to 4095 for the Catalyst 8540 MSR, and 0 to 255 for the Catalyst 8510 MSR and LightStream 1010. |
4095 virtual paths (Catalyst 8540 MSR)
255 virtual paths (Catalyst 8510 MSR and LightStream 1010)
Interface configuration
The following example sets the maximum number of ATM virtual paths supported on interface ATM 0/0/1 to 128.
Switch(config)# interface atm 0/0/1 Switch(config-if)# atm maxvp-number 128
atm maxvpi-bits
atm pvp
show atm interface
shutdown (interface)
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.
atm maxvpi-bits max-vpi-bits
max-vpi-bits | Maximum number of active VPI bits supported on an ATM interface (0 to 12 for the Catalyst 8540 MSR, and 0 to 8 for the Catalyst 8510 MSR and LightStream 1010). |
8 bits
Interface configuration
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 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 following example sets the maximum number of active VPI bits to 6 for interface ATM 0/0/0.
Switch(config)# interface atm 0/0/0 Switch(config-if)# no atm auto-configuration Switch(config-if)#%ATM-6-ILMINOAUTOCFG: ILMI(ATM0/0/0): Auto-configuration is disabled, current interface parameters will be used at next interface restart.Switch(config-if)# atm maxvpi-bits 6 Switch(config-if)#%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM0/0/0.
atm auto-configuration
atm connection-traffic-table-row
atm maxvp-number
atm pvp
show atm interface
show switch fabric
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.
atm mbs-default {vbr-rt | vbr-nrt} num
num | This parameter is an integer, with a range of 0 to 2147483647. The MBS is expressed in cells. |
1024
Interface configuration
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.
The following example shows changing the default MBS for received cells on VBR-RT connections.
Switch(config-if)# atm mbs-default vbr-rt 4000
atm connection-traffic-table-row
show atm vc
show atm vp
To configure an ATM NNI on the specified physical or logical (VP tunnel) port, use the atm nni interface configuration command.
atm nniThis command has no keywords or arguments.
Interface configuration
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 or atm uni commands for this interface. Future configuration of the atm auto-configuration, atm iisp, or atm uni command on this interface overwrites the atm nni command.
The following example shows configuring an ATM NNI on logical port card 3, subcard 1, and port 3, VPI 99.
Switch(config)# interface atm 3/1/3.99 Switch(config-subif)# atm nni
atm auto-configuration
atm iisp
atm signalling enable
atm uni
show atm interface
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.
atm nsap-address nsap-address
nsap-address | A 20-octet NSAP address. Specifies the 40-digit hexadecimal NSAP address of this interface (the source address). |
Interface configuration
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. It is recommended that the address be configured using the following dotted format.
xx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xxxx.xx
The dots can be omitted.
The following example shows configuration of the NSAP-format ATM end-system address for interface ATM 0.1.
Switch(config)# interface atm 0.1 Switch(config-subif)# atm nsap-address 47.0091.8100.0000.1111.1111.1111.1111.1111.1111.00 Switch(config-subif)# exit Switch(config)# atm route 47.0091.8100.0000.1111.1111.1111.1111.1111.1111.00 atm0 internal
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.
protocol protocol-address atm-nsap atm-nsap-address [class class-name] [broadcast]
protocol | Specified as the keyword ip. |
protocol-address | Destination address that is being mapped to this SVC. |
atm-nsap-address | Destination ATM NSAP address. Must be exactly 40 hexadecimal digits long and in the correct dotted format. |
class-name | Name of a table that contains encapsulation-specific parameters. Such a table can be shared between maps that have the same encapsulation. |
broadcast | Indicates this map entry is to be used when the corresponding protocol sends broadcast packets to the interface. |
aal5mux | Uses aal5mux encapsulation. The default is snap. |
No map statements are defined.
Map-list configuration
This command is required with the map-list command when you are configuring an SVC.
In the following example, a map list named atmsvc includes one map statement for a destination address being mapped.
Switch(config)# map-list atm 1/0/0 Switch(config-map-list)# map-list atmsvc ip 172.21.97.17 atm-nsap AB.CDEF.01.234567.890A.BCDE.F012.3456.7890.1234.12 class qos
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.
ais | AIS operation. |
end-loopback | End-to-end OAM loopback. |
intercept end-to-end | End-to-end OAM flow intercept. (Catalyst 8510 MSR and |
max-limit | Maximum number of OAMs supported. |
number | Number of maximum OAM-configured connections allowed per switch. The range is 1 to 3200. |
rdi | RDI operation. |
seg-loopback | Segment loopback. |
Global configuration
To set the maximum number of OAM connections that can be configured per switch, use the atm oam max-limit global configuration command.
The following example globally enables AIS, RDI, and segment loopback operators for all interfaces.
Switch(config)# atm oam seg-loopback ais rdi
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.
atm oam [interface atm card/subcard/port[.vpt#]] [vpi [vci]] [ais] [end-loopback]
ais | AIS operation. |
end-loopback | End-to-end OAM loopback. |
loopback-timer | OAM loopback transmit timer. |
max-limit | Maximum number of OAMs supported. |
rdi | RDI operation. |
seg-loopback | Segment loopback. |
intercept end-to-end | Intercept OAM cells and forward to the ATM switch processor. |
vpi | Virtual path identifier. |
vci | Virtual channel identifier. |
card/subcard/port[.vpt#] | Card, subcard, port, and tunnel number for the ATM interface. |
The default is 5 seconds for the loopback-timer interval.
Interface configuration
Use the atm oam loopback-timer command only with the seg-loopback and end-loopback keywords.
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.
The following example enables end-to-end OAM loopback on VPI 50 VCI 100 on ATM 3/0/0.
Switch(config)# interface atm 3/0/0 Switch(config-if)# atm oam 50 100 end-loopback
The following example enables or disables the OAM, AIS, RDI, and loopback operation to a specified connection.
Switch(config-if)# no atm oam 12 100 Switch(config-if)# atm oam 19 rdi Switch(config-if)# atm oam 100 200 ais rdi Switch(config-if)# atm oam 34 89 seg-loopback end-to
The following example shows changing the loopback timer interval to 10 seconds.
Switch(config-if)# atm oam 50 100 Switch(config-if)# atm loopback-timer 10
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.
atm output-queue [force] {cbr | vbr-rt | vbr-nrt | abr-ubr} max-size size-num
size-num | Queue size in cells, from 256 to 65250. For installation in hardware, the number provided is rounded up to the next value available in the hardware. The configured and installed values are both displayed using the show atm interface command. |
max-size | Maximum output queue size per service category. |
Varies by physical interface type, queue, and for abr-ubr or vbr-nrt queues, by the OSF value.
Interface configuration
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 is not present.
This command is not supported for the subinterface configuration and does not apply to the route processor interface (ATM 0).
You can configure the parameters only on physical ports 0 or 6 on a 25-Mbps port adapter.
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.
Switch(config)# interface atm 3/0/0 Switch(config-if)# atm output-queue force vbr-nrt max-size 512
atm over-subscription-factor
show atm interface
show atm interface resource
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.
atm output-threshold {cbr | vbr-rt | vbr-nrt | abr | ubr} discard disc-thresh-num
disc-thresh-num | Number 12, 25, 37, 50, 62, 75, 87, or 100 indicating the percentage of queue-full. Using 100 disables the threshold. |
efci-thresh-num | Number 12, 25, 50, or 100, indicating the percentage of queue-full using 100 disables the threshold. |
abr-thresh-num | Number 12, 25, 37, 50, 62, 75, 87, or 100 indicating the percentage of queue-full. Using 100 disables the threshold. |
efci | When cells arrive on connections to a congested (as indicated by efci threshold) output queue on the interface, the efci bit in the cell header is set. |
relative-rate | When a backward RM cell is received on an ABR connection on the interface (from outside the switch), its congestion bit is set if the ABR-UBR interface output queue is congested (as indicated by abr-thresh-num). |
discard | When a cell arrives at a congested output queue (as indicated by discard-threshold), it is eligible for CLP discard (or EPD if EPD is enabled on the connection). |
For all service categories, discard is 87 percent and efci is 25 percent. The abr relative-rate is
25 percent.
Interface configuration
This command is not supported for subinterface configuration. This command does not apply to the route processor interface (ATM 0).
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:
In the following example, the discard threshold of the VBR-NRT queue is set to 87 percent of the maximum queue size.
Switch(config)# interface atm 3/0/0 Switch(config-if)# atm output-threshold vbr-nrt discard 87
To set the oversubscription factor, use the atm over-subscription-factor global configuration command. To assign the default value to the oversubscription factor, use the no form of this command.
atm over-subscription-factor o-value
o-value | A positive integer from 1 to 32. |
8
Global configuration
The oversubscription factor number is a positive integer in the range from 1 through 32. Use this command to determine the initial port queue size. The oversubscription factor is used to size the VBR-NRT and ABR/UBR queues.
The resizing of queues can be overridden using the atm output-queue command. Changes to
atm over-subscription-factor only take place during startup.
The sizing of VBR-NRT and ABR-UBR queues is determined by the following equations.
size (vbr-nrt) = .25 * ((osf * 2048) - DefaultSize (cbr) - DefaultSize (vbr-rt)) size (abr-ubr) = .75 * ((osf * 2048) - DefaultSize (cbr) - DefaultSize (vbr-rt))
The default size of the CBR and VBR queues varies by interface type, as defined in Table 2-3.
| Interface Type | Default Max Size CBR Queue | Default Max Size VBR-RT Queue |
|---|---|---|
SONET | 256 | 256 |
DS3/E3 | 256 | 512 |
In the following example, the oversubscription 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.
Switch(config)# interface atm 3/0/0 Switch(config)# atm over-subscription-factor 15
atm output-queue
show atm resource
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.
atm pacing r-value [force]
r-value | Bit rate in thousand bits per second (kbps). |
No pacing
Interface configuration
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.
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.
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.
Switch(config)# interface atm 3/0/0 Switch(config-if)# atm pacing 30000
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.
atm pnni admin-weight number service-category
number | The administrative weight value assigned to the interface (1 to 1000000). Refer to the administrative-weight command for default values. |
service-category | The keywords are cbr, vbr-rt, vbr-nrt, abr, ubr, or all. |
Determined by the mode set by the administrative-weight command.
Interface configuration
This command does not apply to the ATM 0 interface and applies only 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.
administrative-weight
show atm pnni interface
To specify the aggregation token for a PNNI interface, use the atm pnni aggregation-token PNNI interface configuration command.
atm pnni aggregation-token value
value | The aggregation token on this interface, in the range of 0 to 4294967295. |
0
PNNI interface configuration
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 together with aggregation token 0.
The following example shows how to set the aggregation token on ATM interface 1/0/0.
Switch(config)# interface atm 1/0/0 Switch(config-if)# atm pnni aggregation-token 100
aggregation-mode
show atm pnni aggregation link
show atm pnni aggregation node
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.
atm pnni explicit-path {identifier path-id-number [name path-name] | name path-name}
identifier path-id-number | Path ID number of the explicit path. |
name path-name | Path name of the path for the explicit path. If you specify the identifier first, you can assign or modify its path name. |
enable | Enables the explicit path to be used for routing any soft connections that reference it. |
disable | Prevents the explicit path from being used for routing any soft connections that reference it. |
Enabled
Global configuration
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:
atm pnni explicit-path {identifier path-id-number [name path-name] | name path-name}The following example shows how to enter PNNI explicit path configuration mode from global configuration mode, for a path named boston_2.path1.
Switch(config)# atm pnni explicit-path name boston_2.path1 Switch(cfg-pnni-expl-path)#
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:
Switch(cfg-pnni-expl-path)# next-node dallas_2 Switch(cfg-pnni-expl-path)# next-node dallas_4 port 80003004 Switch(cfg-pnni-expl-path)# segment-target chicago_2 Switch(cfg-pnni-expl-path)# next-node 40:72:47.009181000000106000000000 Switch(cfg-pnni-expl-path)# end Switch#
The following example shows how to reenter PNNI explicit path configuration mode for a path named new_york.path1 and list the current path.
Switch(config)# atm pnni explicit-path name new_york.path1 Switch(cfg-pnni-expl-path)# list Explicit_path name new_york.path1 (id 5) from node dallas_1:1 next-node dallas_2 2 next-node dallas_4 port 80003004 3 segment chicago_2 4 next-node new_york
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.
Switch(cfg-pnni-expl-path)# index 1 next-node dallas_2 port 80000000 Explicit_path name new_york.path1 (id 5) from node dallas_1:1 next-node dallas_2 port 80000000 2 next-node dallas_4 port 80003004 3 segment chicago_2 4 next-node 40:72:47.009181000000106000000000.
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.
Switch(cfg-pnni-expl-path)# append 2 next-node st_louis Explicit_path name new_york.path1 (id 5) from node dallas_1:1 next-node dallas_2 port 80000000 2 next-node dallas_4 port 80003004 3 next-node st_louis 4 segment chicago_2 5 next-node 40:72:47.009181000000106000000000.
atm soft-vc
atm soft-vp
exclude-node
frame-relay soft-vc
next-node
segment-target
show atm pnni explicit-paths
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.
atm pnni link-selection {cbr | vbr-rt | vbr-nrt | abr | ubr | all}
cbr | Constant bit rate service category. |
vbr-rt | Variable bit rate real-time service category. |
vbr-nrt | Variable bit rate non-real-time service category. |
abr | Available bit rate service category. |
ubr | Unspecified bit rate service category. |
all | All service categories. |
admin-weight-minimize | Transmits a call on the interface with the lowest administrative weight. |
blocking-minimize | Minimizes subsequent call blocking. |
transmit-speed-maximize | Transmits calls on the highest-speed parallel link. |
load-balance | Balances calls across parallel links. |
alternate | Selects an alternate link that is used only when all other, nonalternate, links are either down or full. |
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.
Interface configuration
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.
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:
Switch(config)# interface atm 0/0/0 Switch(config-if)# atm pnni link-selection vbr-nrt transmit-speed-maximize
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:
Switch(config)# interface atm 0/0/0 Switch(config-if)# atm pnni link-selection cbr alternate
To specify which PNNI node in the switch 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.
atm pnni node node-index
node-index | An integer, from 1 through 255, identifying a PNNI node running on this switch. Currently only a single lowest-level node with node index 1 is supported. |
Node index 1
Interface configuration
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.
The following example shows how to configure a PNNI node index on ATM interface 1/0/0.
Switch# configure terminal Switch(config)# interface atm 1/0/0 Switch(config-if)# atm pnni node 1
atm auto-configuration
atm nni
node
show atm pnni interface
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.
atm prefix 13-byte-prefix
13-byte-prefix | A 13-byte ATM address prefix, specified as 26 hexadecimal digits. |
Interface configuration
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.
The following example shows how to configure an ILMI address prefix on interface ATM 3/1/0.
Switch(config)# interface atm 3/1/0 Switch(config-if)# atm prefix 47123456789012345678112233
atm address
show atm addresses
show atm ilmi-status
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.
atm pvc vpi-A [vci-A | any-vci] [cast-type type-A] [upc upc-A] [pd pd] [rx-cttr index]
any-vci | Selects any available VCI. This feature only applies to the route processor interface (ATM 0). |
vpi | VPI of this PVC, from 0 to 4095 for the Catalyst 8540 MSR, or 0 to 255 for the Catalyst 8510 MSR and LightStream 1010. The VPI is a 12-bit field in the |
vci | VCI of this PVC. The range is normally 32 to 16383, but can be expanded to 5 to 16383 in manual-well-known-vc mode. The VCI is a 16-bit field in the header of the ATM cell. The VCI value is unique only on a single interface, not throughout the ATM network (it has local significance only). |
type | The type of PVC, specified as p2p, p2mp-root, or p2mp-leaf. The default is p2p. |
pd | Specifies the intelligent packet discard option as on or off. The default is off. |
vpt # | Specifies the virtual path tunnel number. |
encap | AAL and encapsulation type and applies only to terminating connections. When aal5mux is specified, a protocol is required. Possible values are as follows: · aal5lane---A LANE-type virtual connection. · aal5mux decnet---A MUX-type virtual connection. · aal5snap---LLC/SNAP precedes the protocol datagram. This is the only encapsulation supported for Inverse ARP. · ilmi---Specifies the ILMI control VC when in manual-well-known-vc mode only. · pnni---Specifies the PNNI control VC when in manual-well-known-vc mode only. · qsaal---Specifies the signalling control VC when in manual-well-known-vc mode only. |
upc | Usage parameter control, specified as pass, tag, or drop; the default is pass. The upc parameter can be set to tag or drop only under the following conditions: · The ATM interface is not the route processor port (ATM 0) or a logical port (VP tunnel). · The connection is not the leaf of a point-to-multipoint connection. |
rx-cttr | Connection traffic table row index in the received direction. The connection traffic table row should be configured before using the atm pvc command. See the atm connection-traffic-table-row command for information on configuring the rx-cttr parameter. The default is 1. |
tx-cttr | Connection traffic table row index in the transmitted direction. The connection traffic table row should be configured before using the atm pvc command. See the atm connection-traffic-table-row command for information on configuring the tx-cttr parameter. The default is 1. |
card/subcard/port | Card, subcard, and port number for the ATM interface. |
inarp minutes | Specifies how often Inverse ARP datagrams are sent on this virtual connection and applies only to terminating connections. The default value is 15 minutes. |
weight | Specifies the weight assigned to the output VC for weighted round robin scheduling. This value is an integer in the range of 1 to 15. This parameter is valid only on systems equipped with the switch processor feature card. (Catalyst 8540 MSR and Catalyst 8510 MSR and LightStream 1010 with FC-PFQ) |
See "Syntax Description."
Interface configuration
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.
The following example configures a terminating PVC between interface ATM 3/1/1 and the route processor port.
Switch(config)# interface atm 0 Switch(config-if)# atm pvc 0 any-vci interface atm 3/1/1 0 100
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.
Switch(config)# interface atm 3/0/0 Switch(config-if)# atm pvc 0 40 interface atm 3/0/1 0 40
The following example shows a display using the encap variable.
Switch(config-if)# atm pvc 100 200 interface atm 0 0 344 encap ? aal5lane AAL5+LANE Encapsulation aal5mux AAL5+MUX Encapsulation aal5snap AAL5+LLC/SNAP Encapsulation
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.
Switch(config)# interface atm 3/1/1.99 Switch(config-subif)# atm pvc 99 100 interface atm 3/0/0 0 89
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.
Switch# show atm vc interface atm 0/0/1.51 Interface VPI VCI Type X-Interface X-VPI X-VCI Encap Status ATM0/0/1.51 51 3 PVC ATM2/0/0 0 75 SNAP DOWN ATM0/0/1.51 51 4 PVC ATM2/0/0 0 76 SNAP DOWN ATM0/0/1.51 51 5 PVC ATM2/0/0 0 74 QSAAL DOWN ATM0/0/1.51 51 16 PVC ATM2/0/0 0 73 ILMI DOWN
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.
Switch# show atm vc interface atm 0/0/1.51 51 16 Interface: ATM0/0/1.51, Type: oc3suni VPI = 51 VCI = 16 Status: DOWN Time-since-last-status-change: 2w0d Connection-type: PVC Cast-type: point-to-point Packet-discard-option: enabled Usage-Parameter-Control (UPC): pass Wrr weight: 32 Number of OAM-configured connections: 0 OAM-configuration: disabled OAM-states: Not-applicable Cross-connect-interface: ATM2/0/0, Type: ATM Swi/Proc Cross-connect-VPI = 0 Cross-connect-VCI = 73 Cross-connect-UPC: pass Cross-connect OAM-configuration: disabled Cross-connect OAM-state: Not-applicable Encapsulation: AAL5ILMI Threshold Group: 6, Cells queued: 0 Rx cells: 0, Tx cells: 0 Tx Clp0:0, Tx Clp1: 0 Rx Clp0:0, Rx Clp1: 0 Rx Upc Violations:0, Rx cell drops:0 Rx pkts:0, Rx pkt drops:0 Rx connection-traffic-table-index: 6 Rx service-category: UBR (Unspecified Bit Rate) Rx pcr-clp01: 424 Rx scr-clp01: none Rx mcr-clp01: none Rx cdvt: 1024 (from default for interface) Rx mbs: none Tx connection-traffic-table-index: 6 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 424 Tx scr-clp01: none Tx mcr-clp01: none Tx cdvt: none Tx mbs: none No AAL5 connection registered
The following example shows how to delete the previously configured ATM transit point-to-point PVC.
Switch(config-if)# interface atm 1/1/1 Switch(config-if)# no atm pvc 50 100
The following example shows using the show atm vc command to display detailed information about a specific connection on a system equipped with the FC-PCQ.
Switch# show atm vc interface atm 0/1/0 1 10 Interface: ATM0/1/0, Type: oc3suni VPI = 1 VCI = 100 Status: UP Time-since-last-status-change: 00:00:08 Connection-type: PVC Cast-type: point-to-point Packet-discard-option: disabled Usage-Parameter-Control (UPC): pass Number of OAM-configured connections: 0 OAM-configuration: disabled OAM-states: Not-applicable Cross-connect-interface: ATM0/1/3, Type: oc3suni Cross-connect-VPI = 1 Cross-connect-VCI = 100 Cross-connect-UPC: pass Cross-connect OAM-configuration: disabled Cross-connect OAM-state: Not-applicable Rx cells: 0, Tx cells: 0 Rx connection-traffic-table-index: 1 Rx service-category: UBR (Unspecified Bit Rate) Rx pcr-clp01: 7113539 Rx scr-clp01: none Rx tolerance: 0 (from default for interface) Tx connection-traffic-table-index: 1 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 7113539 Tx scr-clp01: none Tx tolerance: none
atm connection-traffic-table-row
atm pvp
show atm interface
show atm vc
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.
atm pvp vpi-A [cast-type type-A] [upc upc-A] [rx-cttr index] [tx-cttr index]
type | Specified as p2p, p2mp-root, or p2mp-leaf. The default is p2p. |
vpi | VPI of this PVP, from 1 to 4095 for the Catalyst 8540 MSR, or from 1 to 255 for the Catalyst 8510 MSR and LightStream 1010. The VPI is a 12-bit field in the Catalyst 8540 MSR, or an 8-bit field in the Catalyst 8510 MSR and LightStream 1010 in the header of the ATM cell. The VPI value is unique only on a single interface, not throughout the ATM network (it has local significance only). |
upc | Usage parameter control, specified as pass, tag, or drop. The default is pass. The upc variable can be set to tag or drop only under the following conditions: · The ATM interface is not the route processor port (ATM 0) or a logical port (VP tunnel). · The connection is not the leaf of a point-to-multipoint connection. |
hierarchical | Defines a hierarchical VP tunnel. See the "Usage Guidelines" for limitations. The PVP is a VP tunnel that should use hardware shaping of the aggregate transmit flow of cells. Only CBR PVPs can be hierarchical VP tunnels. Hierarchical VP tunnels can support transit VCs of all service categories at the same time. |
rx-cttr | Connection traffic table row index in the received direction. The connection traffic table row should be configured before using the atm pvc command. See the atm connection-traffic-table-row command for information on configuring the rx-cttr parameter. The default is 1. |
shaped | The PVP is a VP tunnel that should use hardware shaping of the aggregate transmit flow of cells. Only CBR PVPs can be shaped VP tunnels. |
tx-cttr | Connection traffic table row index in the transmitted direction. The connection traffic table row should be configured before using atm pvc command. See the atm connection-traffic-table-row command for information on configuring the tx-cttr parameter. The default is 1. |
card/subcard/port | Card, subcard, and port number for the ATM interface. |
weight | Specifies the weight assigned to the output VP for weighted round-robin scheduling. This value is an integer in the range of 1 to 15. This parameter is valid only on systems equipped with the switch processor feature card. |
See "Syntax Description."
Interface configuration
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.
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 OC12 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.
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.
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.
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:
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.
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.
The following example shows how to configure an ATM PVP from ATM 3/1/1 to ATM 3/1/2.
Switch(config)# interface atm 3/1/1 Switch(config-if)# atm pvp 99 upc drop rx-cttr 37 tx-cttr 37 interface atm 3/1/1 88 upc tag
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.
Switch# show atm vp interface atm 3/1/1 99 Interface: ATM3/1/1, Type: ds3suni_Quad VPI = 99 Status: TUNNEL Time-since-last-status-change: 03:22:05 Connection-type: PVP Cast-type: point-to-point Usage-Parameter-Control (UPC): pass Wrr weight: 32 Number of OAM-configured connections: 0 OAM-configuration: disabled OAM-states: Not-applicable Threshold Group: 5, Cells queued: 0 Rx cells: 0, Tx cells: 0 Tx Clp0:0, Tx Clp1: 0 Rx Clp0:0, Rx Clp1: 0 Rx Upc Violations:0, Rx cell drops:0 Rx Clp0 q full drops:0, Rx Clp1 qthresh drops:0 Rx connection-traffic-table-index: 1 Rx service-category: UBR (Unspecified Bit Rate) Rx pcr-clp01: 7113539 Rx scr-clp01: none Rx mcr-clp01: none Rx tolerance: 1024 (from default for interface) Tx connection-traffic-table-index: 1 Tx service-category: UBR (Unspecified Bit Rate) Tx pcr-clp01: 7113539 Tx scr-clp01: none Tx mcr-clp01: none Tx tolerance: none
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.
Switch(config)# interface atm 0/0/1 Switch(config-if)# atm pvp 51 Switch(config-if)# interface atm 0/0/1.51
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.
Switch# show atm interface atm 0/0/1.51
Interface: ATM0/0/1.51 Port-type: vp tunnel
IF Status: DOWN Admin Status: down
Auto-config: enabled AutoCfgState: waiting for response from peer
IF-Side: Network IF-type: UNI
Uni-type: Private Uni-version: V3.0
Max-VPI-bits: 0 Max-VCI-bits: 14
Max-VP: 0 Max-VC: 16383
ConfMaxSvpcVpi: 0 CurrMaxSvpcVpi: 0
ConfMaxSvccVpi: 0 CurrMaxSvccVpi: 0
ConfMinSvccVci: 33 CurrMinSvccVci: 33
Signalling: Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0040.0b0a.2a81.4000.0c80.0010.33
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs Total-Cfgd Inst-Conns
4 0 0 0 4 0
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.
Switch(config-if)# atm pvp 10 hierarchical rx-cttr 2 tx-cttr 2 Switch(config-if)# interface atm 0/0/0.10
atm connection-traffic-table-row
atm pvc
show atm interface
show atm vp
To change individual QoS objectives assigned to SVC setup messages entering the switch via 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.
atm qos default {cbr | vbr-rt} max-cell-transfer-delay {microseconds | any}
microseconds | Integer number, which represents time in microseconds, in the range 0 through 16777214. |
loss-ratio exponent | Positive integer in the range of 1 through 15. This represents 10 - (loss-ratio). |
any | Indicates that the QoS value is not considered in the setup of the connection. |
any
Global configuration
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 you specify max-cell-loss-ratio, and the clp0 or clp1plus0 value is not configured, the default is CLP=0.
In the following example, the cbr MaxCTD objective is set to 1000 microseconds.
Switch(config)# atm qos default cbr max-cell-transfer-delay 1000
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.
atm rmon collect number
number | Specifies the port select group number, from 1 to 2147483647. |
Disabled
Interface configuration
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 atm rmon collect command.
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).
The following example shows setting the port select group number to 1000.
Switch(config)# atm rmon enable Switch(config)# interface atm 1/0/0 Switch(config-if)# atm rmon collect 1000
atm rmon enable
interface
show atm rmon
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.
atm rmon enableThis command has no keywords or arguments.
Disabled
Global configuration
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.
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.
atm rmon portselgrp number [descr string | host-prio number | host-scope number |
number | Specifies the number of the port select group, from 1 to 2147483647. |
descr | Specifies the descriptive label for the ATM-RMON collection. |
host-prio | Specifies the host collection resource priority from 1 to 3. Use 1 for low, 2 for normal, and 3 for high. The default is 2. |
host-scope | Specifies the host collection address collection scope from 1 to 3. Use 1 for prefix, 2 for prefix and esi, and 3 for the entire address. The default is 2. |
matrix-prio | Specifies the matrix collection resource priority from 1 to 3. Use 1 for low, 2 for normal, and 3 for high. The default is 2. |
matrix-scope | Specifies the matrix collection address collection scope from 1 to 3. Use 1 for prefix, 2 for prefix and esi, and 3 for the entire address. The default is 2. |
maxhost | Specifies the maximum desired host entries, from 0 to 4294967295. Use 0 to disable, or omit the number to indicate no configuration limit. |
maxmatrix | Specifies the maximum desired matrix entries from 0 to 4294967295. Use 0 to disable, or omit the number to indicate no configuration limit. |
nostats | Suppresses the collection of the atmStatsTable for this group. |
owner | Specifies the owner for all the control tables used by the ATM-RMON collection (portSelGrpOwner, atmHostControlOwner, or atmMatrixControlOwner). The default is an empty string. |
See "Syntax Description."
Global configuration
To use this command, configure the ports into port select groups using the atm rmon collect interface configuration command.
The following example shows configuring the port select group, and sets the maxhost to 1000 and the matrix-scope to 3.
Switch(config-if)# atm rmon collect 3 Switch(config-if)# exit Switch(config)# atm rmon portselgrp 3 maxhost 1000 matrix-scope 3
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.
atm route addr-prefix interface-type card/subcard/port[.vpt#] [internal] [scope org-scope]
addr-prefix | Specifies the address prefix. The address prefix has a maximum length of 19 bytes. By default, each character in the prefix is 4 bits long. To specify a part of a prefix in bits, use parentheses () to enclose binary numbers. The asterisk (*) wildcard character means "neutral." Wildcard character ellipses (...) after a prefix match any destination address that starts with the prefix. |
interface-type | Specifies the interface type as atm, ethernet, loopback, or null. |
card/subcard/port | Identifies the card, subcard, and port number for the interface. |
.vpt# | Specifies an interface that represents a virtual path tunnel. |
internal | Specifies an internal static route to an internal reachable address prefix. By default, an exterior static route to an exterior reachable address prefix is created. |
org-scope | Specifies the organizational scope (for example, UNI scope) value for the route. The valid range of organizational scope values is from local (1) to global (15). The default organizational scope is global (15) for individual addresses and local (1) for group addresses. |
e164-address | Associates a forwarding E.164 address with the static route. |
address-string | Specifies a forwarding native E.164 address, used when a call matching the ATM address prefix is forwarded across the specified interface. The E.164 address consists of 7 to 15 decimal characters. |
numtype | Specifies a number from the following four options: international, national, subscriber, and local. |
See "Syntax Description."
Global configuration
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.
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.
Switch(config)# atm route 47.8... atm 1/2/1
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.
Switch(config)# atm route 47.8(10*)... atm 1/2/1
The following example shows how to configure a static route on ATM 0/0/0 with a forwarding E.164 address.
Switch(config)# atm route 1234 atm 0/0/0 e164-address 1234567
atm e164 address
redistribute
scope map
scope mode
show atm pnni scope
show atm route
To initiate route optimization immediately for a specific interface or specific soft VC, use the atm route-optimization EXEC command.
atm route-optimization soft-connection interface {atm card/subcard/port [vpi [vci]] |
card/subcard/port | Specifies the card, subcard, and port number of a specific ATM interface. |
vpi | Specifies the virtual path identifier. |
vci | Specifies the virtual channel identifier. |
card/subcard/port:cgn | Specifies the card, subcard, port and channel-group number for the Frame Relay interface. |
dlci | For a Frame Relay interface, if a DLCI is not specified, this command sets optimization for the specified Frame Relay interface. If a DLCI is specified, this command sets optimization for a specific Frame Relay interworking soft VC. |
EXEC
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.
The following example shows how to initiate ATM route optimization on a soft VC at ATM interface 1/0/0 100 250.
Switch# atm route-optimization soft-connection interface atm 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.
Switch# atm route-optimization soft-connection interface serial 1/0/3:1 248
atm route-optimization (interface)
atm route-optimization percentage-threshold
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.
atm route-optimization soft-connection [interval minutes] [time-of-day {anytime |
interval minutes | Specifies the frequency of route optimization in minutes. The range is 10 to 10000. The default is 60 minutes. |
time-of-day | Specifies the 24-hour time range when route optimization can occur. The default is anytime. |
anytime | Route optimization can occur at any time during the day. |
start-time | Specifies the start of the time range when route optimization is allowed, in 24-hour format (hh:mm). |
end-time | Specifies the end of the time range when route optimization is allowed, in 24-hour format (hh:mm). |
For interval: 60 minutes.
For time-of-day: anytime.
Interface configuration
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.
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.
The following example enables soft PVC route optimization on interface ATM 0/1/2, with the time period of 120 minutes.
Switch(config)# interface atm 0/1/2 Switch(config-if)# atm route-optimization soft-connection interval 120
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.
Switch(config)# interface serial 11/0/0:1 Switch(config-if)# atm route-optimization soft-connection interval 30 time-of-day 18:00 5:00
atm route-optimization (EXEC)
atm route-optimization percentage-threshold
show atm interface
show running-config
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.
atm route-optimization percentage-threshold percent
percent | Specify the route optimization threshold in percent, from 5 to 100. |
30
Global configuration
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.
The following example shows setting the route optimization threshold to 20 percent.
Switch(config)# atm route-optimization percentage-threshold 20
atm route-optimization (EXEC)
atm route-optimization percentage-threshold
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.
atm router pnniThis command has no arguments or keywords.
Global configuration
Use this command to start global PNNI configuration mode.
The following example shows using the atm router pnni global configuration command to change to ATM router PNNI configuration mode.
Switch(config)# atm router pnni Switch(config-atm-router)#
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.
atm routing-mode static
static | Restricts ATM routing to allow only static configuration of ATM routes. In this routing mode, the switch does not run any dynamic ATM routing protocols, such as PNNI routing. |
Disabled (no restrictions on ATM routing)
Global configuration
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.
The following example shows configuration of a switch to allow only static routing.
Switch(config)# atm routing-mode static
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 set to the default value of 64544, use the no form of this command.
atm service-category-limit {cbr | vbr-rt | vbr-nrt | abr-ubr} l-value
l-value | Integer in the range from 0 to 64544, specified in units of cells. |
64544
Global configuration
The no form of this command applies to all service categories.
 | Caution Setting service-category-limit to 0 causes the connection requests for the associated service categories to be rejected. |
In the following example, the maximum number of ABR and UBR cells allowed into the switch fabric at one time is limited to 45000.
Switch(config)# atm service-category-limit abr-ubr 45000
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.
This command supports both the ATM Forum service categories and the TBR service classes on physical interfaces, as shown in Table 2-4.
| ATM Forum Service Classes | ATM Forum Service Categories | Tag Bit Rate | Service Classes |
|---|---|---|---|
2 | VBR-RT | 1 | TBR class 1 |
3 | VBR-NRT | 6 | TBR class 2 |
4 | ABR | 7 | TBR class 3 |
5 | UBR | 8 | TBR class 4 |
To specify the weighting for each service class for a physical interface, use the following syntax:
atm service-class {1 | 2 | 3 | 4 | 5 | 6 | 7 | 8} wrr-weight weightTo cancel WRR scheduling or to set weights to their defaults, use the no form of the command.
no atm service-class [1 | 2 | 3 | 4 | 5 | 6 | 7 | 8] wrr-weight weightFor hierarchical VP tunnels, this command supports either the ATM Forum service categories or the TBR service classes, as shown in Table 2-5.
| ATM Forum Service Classes | ATM Forum Service Categories | Tag Bit Rate | Service Classes |
|---|---|---|---|
1 | VBR-RT | 1 | TBR class 1 |
2 | VBR-NRT | 2 | TBR class 2 |
3 | ABR | 3 | TBR class 3 |
4 | UBR | 4 | TBR class 4 |
To specify the weighting for each service class for a hierarchical VP tunnel, use the following syntax:
atm service-class {1 | 2 | 3 | 4} wrr-weight weight
To cancel WRR scheduling or to set weights to their defaults, use the no form of the command.
no atm service-class {1 | 2 | 3 | 4} wrr-weight weight
1-8 | ATM Forum service classes or tag bit rate service classes. Refer to Table 2-6 for service classes 1 to 8 for physical interfaces. Refer to Table 2-5 for service classes 1 to 4 for hierarchical VP tunnels. |
wrr-weight weight | Integer in the range of 1 to 15. |
Table 2-6 lists the service classes and the default class weights for physical interfaces and hierarchical VP tunnels.
| Physical Interfaces | Hierarchical VP Tunnels | |||
|---|---|---|---|---|
| Service Class | Default Class Weight | Service Class | Default Class Weight for ATM Forum Service Classes | Default Class Weight for Tag Bit Rate Service Classes |
1 | 1 | 1 | 8 | 1 |
2 | 8 | 2 | 1 | 2 |
3 | 1 | 3 | 1 | 3 |
4 | 1 | 4 | 1 | 4 |
5 | 1 | - | - | - |
6 | 2 | - | - | - |
7 | 3 | - | - | - |
8 | 4 | - | - | - |
Interface configuration
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.
In the following example, ATM interface 2/0/1 is configured for service class 3 with a WRR weight of 8.
Switch(config)# interface atm 2/0/1 Switch(config-if)# atm service-class 3 wrr-weight 8
show atm interface resource
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.
atm signalling cug access [permit-unknown-cugs {to-user | from-user permanent |
permit-unknown-cugs | Permits calls between users attached to this interface and unknown users that are not members of the CUGs on this interface. |
to-user | Applies to calls going from the network to the user. |
from-user | Applies to calls going from the user to the network. |
per-call | Uses CUG index in CUG IE (received from the end system) to map to a CUG IC IE. |
both-directions | Applies to calls going from the network to the user, and to calls going from the user to the network. |
permanent | Indicates that permit-unknown-cugs applies to all calls from users to the network, regardless of whether the call setup asked for the permission or not. |
No incoming or outgoing access allowed. An interface is not considered to be a CUG access interface unless this command is configured. If permit-unknown-cugs is 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.
Interface configuration
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.
Table 2-7 describes the relationship between the Cisco CUG access terminology and ITU-T CUG access terminology.
| ITU-T CUG | Cisco CUG |
|---|---|
incoming access allowed to-user | permit-unknown-cugs |
outgoing access allowed from-user | permit-unknown-cugs |
The following example shows configuration as a CUG access interface that allows calls from unknown CUGs.
Switch(config)# interface atm 2/0/1 Switch(config-if)# atm signalling cug access permit-unknown-cugs to-user
atm signalling cug assign
show atm signalling cug access
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.
atm signalling cug alias alias-name interlock-code interlock-code
alias-name | The name of the alias. |
interlock-code | The 24-byte interlock code, specified as a string of 48 hexadecimal digits. |
No alias name is defined.
Global configuration
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.
The following example shows how to create the switch_cug CUG alias with the 24-bite interlock code.
Switch(config)# atm signalling cug alias switch_cug interlock-code 47.0091810000000061705BDA01.0061705BDA01.00.12345678
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.
atm signalling cug assign {alias alias-name | interlock-code interlocking-code}
alias-name | The name of the alias for the 24-byte CUG interlock code. |
interlocking-code | The 24-byte interlock code, specified as a string of 48 hexadecimal digits. |
deny-same-cug | Deny calls to or from other members of the same CUG. Use with the to-user or from-user keywords. |
to-user | Deny calls to the user from members of the same CUG. |
from-user | Deny calls from the user to members of the same CUG. |
preferential | The preferential CUG is the default CUG associated with calls from the user to the network. If a preferential CUG already exists, this command will be rejected. |
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.
Interface configuration
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 destined 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 from users attached to this interface to unknown users are permitted, the calls proceed as non-CUG calls, without generating any CUG IE.
Table 2-8 describes the relationship between the Cisco CUG terminology and the ITU-T CUG terminology.
| ITU-T CUG Terminology | Cisco Terminology |
|---|---|
preferential CUG | preferential |
incoming calls barred (ICB) | deny-same-cug to-user |
outgoing calls barred (OCB) | deny-same-cug from-user |
The following example shows assignment of the redefined closed user group switch as the preferential CUG on the interface to ATM 2/0/1.
Switch(config)# interface atm 2/0/1 Switch(config-if)# atm signalling cug assign alias switch_cug preferential
atm signalling cug access
atm signalling cug alias
show atm signalling cug
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.
atm signalling diagnostics {index | enable}Switch(cfg-atmsig-diag)# appears.
index | Specifies the diagnostics index number for the filter table, from 1 to 50, and enters the diagnostics configuration mode. |
enable | Enables signalling diagnostics globally. |
Disabled
Global configuration
ATM signalling diagnostics is a tool for troubleshooting call failures in the ATM network, and should not be enabled while the switch is operating.
The following example shows creating filter table 1.
Switch(config)# atm signalling diagnostics 1 Switch(cfg-atmsig-diag)#
age-timer
called-address-mask
called-nsap-address
calling-address-mask
calling-nsap-address
cast-type
clear-cause
connection-category
incoming-port
max-records
outgoing-port
purge
scope
segment-target
status
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.
atm signalling enableThis command has no arguments or keywords.
Enabled
Interface configuration
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.
The following example shows how to disable signalling on ATM 0/1/2.
Switch(config)# interface atm 0/1/2
Switch(config-if)# no atm signalling enable
Switch(config-if)#
%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM0/1/2.
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.
atm signalling ie aal5 mode {stream | message}
stream | Streaming mode. |
message | Message mode. |
Message mode is passed in UNI 3.0 AAL5 information elements.
Interface configuration
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.
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.
Switch(config)# config terminal Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# interface atm 1/0/0 Switch(config-if)# atm signalling ie aal5 mode message Switch (config-if)# ^Z Switch#
show running-config
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.
atm signalling ie forward {all | calling-number | calling-subaddress | called-subaddress |
all | Forward all signalling information from the calling party to the called party. |
calling-number | Forward the calling party's number to the called party. |
calling-subaddress | Forward the calling party's subaddress to the called party. |
called-subaddress | Forward the called party's subaddress to the calling party. |
higher-layer-info | Forward the broadband higher-layer information element from the calling party to the called party. |
lower-layer-info | Forward the broadband lower-layer information element from the calling party to the called party. |
bli-repeat-ind | Forward the broadband lower-layer repeat indicator information element to the called party. |
aal-info | Forward the AAL information element from the calling party to the called party. |
unknown-ie | Forward the unknown information element in the absence of a known indicator. |
Forward all IEs in the signalling message from the calling party to the called party.
Interface configuration
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.
The following example shows how to forward the calling party's number to the called party.
Switch(config)# interface atm 0/1/2 Switch(config-if)# atm signalling ie forward calling-number
To specify the value of VPCI that is 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.
atm signalling vpci vpci_number
vpci_number | VPCI number 0 to 255. |
Use the value of VPI on which the subinterface is established.
Subinterface configuration
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.
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.
Switch(config)# config terminal Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# interface atm 1/0/0 Switch(config-if)# atm pvp 99 Switch(config-if)# exit Switch(config)# interface atm 1/0/0.99
Switch(config-subif)# atm signalling vpci 0 Switch(config-subif)# end Switch#
show running-config
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.
atm snoop interface atm card/subcard/port [direction dir]
card/subcard/port | Card, subcard, and port number for the ATM interface to be monitored. The port can be any port except the ATM 0 port or the test port. |
dir | Specified as receive or transmit and determines the direction of the cell traffic to monitor. |
Receive
Interface configuration on the snoop test port.
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.
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 snoop test port number for various interfaces.
| Interface | Port Number |
|---|---|
OC-3 | 3/1/3 |
OC-12 | 3/1/0 |
DS3/E3 | Not supported |
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.
Switch(config)# interface atm 3/1/3 Switch(config-if)# shutdown Switch(config-if)# atm snoop interface atm 1/0/2 direction transmit Switch(config-if)# no shutdown
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.
atm snoop-vc [vpi-A vci-A] interface atm card/subcard/port vpi-B vci-B[direction
vpi-A | VPI of the snooping connection. |
vci-A | VCI of the snooping connection. |
card/subcard/port | Card, subcard, and port number for the ATM interface to be monitored. The port can be any port except the ATM 0 port or the test port. |
vpi-B | VPI of the snooped connection. |
vci-B | VCI of the snooped connection. |
direction | When used with the receive or transmit keywords, determines which direction of cell traffic to monitor. |
receive | Monitors cell traffic in the receive direction. |
transmit | Monitors cell traffic in the transmit direction. |
Receive
Interface configuration. Applies to the snoop test port.
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-10 defines the ATM snoop test port number for various interfaces.
| Interface | Port Number |
|---|---|
OC-3 | 3/1/3 |
OC-12 | 3/1/0 |
DS3/E3 | Not supported |
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.
Switch(config)# interface atm 3/1/3 Switch(config-if)# shutdown Switch(config-if)# atm snoop-vc interface atm 1/0/2 1 13 direction transmit Switch(config-if)# no shutdown
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.
atm snoop-vp [vpi-A vci-A] interface atm card/subcard/port vpi-B vci-B [direction
vpi-A | VPI of the snooping connection. |
vci-A | VCI of the snooping connection. |
card/subcard/port | Card, subcard, and port number for the ATM interface to be monitored. The port can be any port except the ATM 0 port or the test port. |
vpi-B | VPI of the snooped connection. |
vci-B | VCI of the snooped connection. |
direction | When used with the receive or transmit keywords, determines which direction of cell traffic to monitor. |
receive | Monitors cell traffic in the receive direction. |
transmit | Monitors cell traffic in the transmit direction. |
Receive
Interface configuration. Applies to the snoop test port.
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-11 defines the ATM snoop test port number for various interfaces.
| Interface | Port Number |
|---|---|
OC-3 | 3/1/3 |
OC-12 | 3/1/0 |
DS3/E3 | Not supported |
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.
Switch(config)# interface atm 3/1/3 Switch(config-if)# shutdown Switch(config-if)# atm snoop-vp interface atm 1/0/2 1 13 direction transmit Switch(config-if)# no shutdown
To create a soft PVC on the switch, use the atm soft-vc interface configuration command.
atm soft-vc source-vpi source-vci dest-address atm-address dest-vpi dest-vci [enable | disable]For existing soft PVCs, use the no form of the command to delete the soft PVC.
no atm soft-vc source-vpi source-vciTo respecify the explicit paths, use the redo-explicit form.
atm soft-vc source-vpi source-vci [enable | disable] [redo-explicit [explicit-path precedence
source-vpi | Source VPI number. |
source-vci | Source VCI number. |
dest-address | ATM address for the destination port. |
dest-vpi | Destination VPI number. |
dest-vci | Destination VCI number. |
enable | Allows the soft connection to be set up; enable is the default for the initial soft connection configuration. Note: If the soft-connection command is reentered for an existing connection, the default is the current enabled or disabled state. |
disable | Prevents an initial soft connection from being set up, or tears down an existing connection. |
upc upc | Usage parameter control, specified as pass | tag | drop; the default is pass. The upc option can be set to tag or drop only when the connection is not the leaf of a point-to-multipoint connection. |
pd pd | Intelligent packet discard option, specified as on | off. The default is off. |
rx-cttr index | Connection traffic table row index in the received direction. The cttr should be configured before using the atm pvc command. See the atm connection-traffic-table-row command for information on configuring the rx-cttr. The default is 1. |
tx-cttr index | Connection traffic table row index in the transmitted direction. The cttr should be configured before using the atm pvc command. See the atm connection-traffic-table-row command for information on configuring the tx-cttr. The default is 1. |
retry-interval | Configures the retry interval timers for a soft PVC. |
first retry-interval | Retry interval for the first retry after the first failed attempt, specified in milliseconds. If the first retry after the first failed attempt also fails, the subsequent attempts will be made at intervals computed using the first retry-interval as follows: (2 ** (k-1)) * first retry-interval Where the value of k is 1 for the first retry after the first failed attempt and will be incremented by 1 for every subsequent attempt. Range is from 100 to 3600000 milliseconds; the default is 5000 milliseconds. |
maximum | The maximum retry interval between any two attempts, specified in seconds. Once the retry interval is computed in the first retry-interval and becomes equal to or greater than the maximum retry-interval configured, the subsequent retries will be done at regular intervals of maximum retry-interval seconds until the call is established. Range is from 1 to 65535 seconds; the default is 60. |
redo-explicit | Applies only to existing soft connections and allows explicit paths to be respecified without tearing down connections. Existing connections will be unaffected unless a reroute takes place, and then they will use the newer explicit-path configuration. |
explicit-path | The PNNI explicit path that is manually configured for routing a soft PVC, using the atm pnni explicit-path command. |
precedence | The precedence number by which ATM PNNI explicit paths are assigned, from Up to three explicit paths can be assigned to a soft PVC. |
name path-name | The name of the ATM PNNI explicit path for routing soft PVCs. |
identifier path-id | Specifies the path ID for the explicit path being configured to route soft PVCs. |
upto partial-entry-index | Allows a subset of a longer explicit path to be used, so that all included nodes after the specified entry index will be disregarded. If the destination is reachable at any next node or segment target, the remaining included nodes in the explicit path will be disregarded automatically. |
only-explicit | If one or more explicit paths have been specified and if the explicit path fails, the soft connection will remain down until it is retried at its next retry interval. If this option is not specified, the system will use the standard on-demand routing instead of waiting for the next retry interval. |
See "Syntax Description."
Interface configuration
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 may 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 will be tried first. If it fails, then the next precedence path will be 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.
The following example shows how a user at the destination switch displays the address of the destination port.
Switch# show atm address Switch Address(es):47.0091810000000003BE59ED00.0003BE59ED00.00 active Soft VC Address(es): 47.0091.8100.0000.0003.be59.ed00.4000.0c81.0000.00 ATM2/0/0 47.0091.8100.0000.0003.be59.ed00.4000.0c81.8000.00 ATM3/0/0 47.0091.8100.0000.0003.be59.ed00.4000.0c81.8010.00 ATM3/0/1 47.0091.8100.0000.0003.be59.ed00.4000.0c81.8020.00 ATM3/0/2 47.0091.8100.0000.0003.be59.ed00.4000.0c81.8030.00 ATM3/0/3 47.0091.8100.0000.0003.be59.ed00.4000.0c82.1000.00 ATM3/1/0 47.0091.8100.0000.0003.be59.ed00.4000.0c82.1000.05 ATM3/1/0.5 47.0091.8100.0000.0003.be59.ed00.4000.0c82.1010.00 ATM3/1/1 47.0091.8100.0000.0003.be59.ed00.4000.0c82.1020.00 ATM3/1/2 47.0091.8100.0000.0003.be59.ed00.4000.0c82.1030.00 ATM3/1/3 ILMI Switch Prefix(es): 47.0091.8100.0000.0003.be59.ed00 ILMI Configured Interface Prefix(es): LECS Address(es):
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:
src vpi = 100, src vci = 200, dest port address = 47.0091.8100.0000.0003.be59.ed00.4000.0c82.1000.0, dest vpi = 100 dest vci = 200
Switch(config-if)# atm soft-vc 100 200 dest-address
47.0091.8100.0000.0003.be59.ed00.4000.0c82.1000.05 100 200
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.
Switch(config)# interface atm 0/1/3 Switch(config-if)# atm soft-vc 0 40 dest-address
47.0091.8100.0000.0003.be59.ed00.4000.0c82.1000.05 100 200
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.
Switch(config)# interface atm 0/1/3 Switch(config-if)# atm soft-vc 0 40 redo-explicit explicit-path 1 name chicago.path1 explicit-path 2 name chicago.path2 only-explicit Modify with new explicit path options [yes], or abort changes [no]? [yes/no]:y
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 will not be changed until a soft PVC reroute occurs.
Switch(config)# interface atm 0/1/3 Switch(config-if)# atm soft-vc 0 40 redo-explicit Modify with new explicit path options [yes], or abort changes [no]? [yes/no]:y
atm pnni explicit-path
show atm addresses
show atm pnni explicit-paths
show atm vc interface
To create a soft PVP on the switch, use the atm soft-vp interface configuration command.
atm soft-vp vpi-s dest-address address vpi-d [upc upc] [rx-cttr index] [tx-cttr index]For existing soft PVPs, use the no form of the command to delete the soft PVP.
no atm soft-vp vpi-sUse the redo-explicit form of the command to respecify explicit paths.
atm soft-vp vpi-s [enable | disable]
vpi-s | Source VPI number. |
dest-address | ATM address for the destination port. |
vpi-d | Destination VPI number. |
upc upc | Usage parameter control, specified as pass | tag | drop; the default is pass. The upc option can be set to tag or drop only under the following conditions: · The ATM interface is not the route processor port (ATM 0) or a logical port (VP tunnel). · The connection is not the leaf of a point-to-multipoint connection. |
rx-cttr index | Connection traffic table row index in the received direction. The cttr should be configured before using the atm soft-vp command. See the atm connection-traffic-table-row command for information on configuring the rx-cttr. The default is 1. |
tx-cttr index | Connection traffic table row index in the transmitted direction. The cttr should be configured before using the atm soft-vp command. See the atm connection-traffic-table-row command for information on configuring the tx-cttr. The default is 1. |
retry-interval | Configures retry interval timers for a soft VP. |
first retry-interval | Retry interval for the first retry after the first failed attempt, specified in milliseconds. If the first retry after the first failed attempt also fails, the subsequent attempts will be made at intervals computed using the first retry-interval as follows: (2 ** (k-1)) * first retry-interval Where the value of k is 1 for the first retry after the first failed attempt, and will be incremented by 1 for every subsequent attempt. Range is from 100 to 3600000 milliseconds; the default is 5000 milliseconds. |
maximum | The maximum retry interval between any two attempts, specified in seconds. Once the retry interval is computed in the first retry-interval and becomes equal to or greater than the maximum retry-interval configured, the subsequent retries will be done at regular intervals of maximum retry-interval seconds until the call is established. Range is from 1 to 65535 seconds; the default is 60. |
enable | Allows the soft connection to be set up. Enable is the default for the initial soft connection configuration. If the soft connection command is reentered for an existing connection, the default is the current enabled or disabled state. |
disable | Prevents an initial soft connection from being set up, or tears down an existing connection. |
redo-explicit | Applies only to existing soft connections and allows explicit paths to be respecified without tearing down connections. Existing connections will be unaffected unless a reroute takes place, and then they will use the newer explicit path configuration. |
explicit-path | The PNNI explicit path that is manually configured for routing a soft PVP, using the atm pnni explicit-path command. |
precedence | The precedence number by which ATM PNNI explicit paths are assigned, from Up to three explicit paths can be assigned to a soft PVP. |
name path-name | The name of the ATM PNNI explicit path for routing soft PVPs. |
identifier path-id | Specifies the path ID for the explicit path being configured to route soft PVPs. |
upto partial-entry-index | Allows a subset of a longer explicit path to be used, so that all included nodes after the specified entry index will be disregarded. If the destination is reachable at any next-node or segment-target, the remaining included nodes in the explicit path will be disregarded automatically. For more information, see the atm pnni explicit-path next-node and atm pnni explicit-path segment-target PNNI explicit path configuration commands. |
only-explicit | If one or more explicit paths have been specified and if the explicit path fails, the soft connection will remain down until it is retried at its next retry-interval. If this option is not specified, the system will use the standard on-demand routing instead of waiting for the next retry interval. |
See "Syntax Description."
Interface configuration
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 will be tried first. If it fails, then the next precedence path will be 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.
The following example shows how a user at the destination switch displays the address of the destination port.
Switch# show atm interface atm 3/0/1 Interface: ATM3/0/1 Interface Status: DOWN Auto-configuration: enabled Auto-configuration status: waiting for response from peer Port-type: External Interface-type: UNI, Interface-side: User Uni-type: Public, Uni-version: V3.0 Max-VPI-bits: 12, Max-VCI-bits: 14 Max-VP: 4095, Max-VC: 32768 Number of PVP: 0 Number of SVP: 0 Number of SoftVP: 0 Number of PVC: 3 Number of SVC: 0 Number of SoftVC: 0 Number of logical port (VP-tunnel): 0 Total number of connections: 3 Input cells: 0, Output cells: 0 5 minute input rate: 0 bits/sec, 0 cells/sec 5 minute output rate: 0 bits/sec, 0 cells/sec ATM Address for Soft VC: 47.0091.8100.0000.0003.be59.ed00.4000.0c82.0010.00
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.
Switch(config-if)# atm soft-vp 150 dest-address 47.0091.8100.0000.0003.be59.ed00.4000.0c82.0010.00 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 will be used.
Switch(config)# interface atm 0/1/3 Switch(config-if)# atm soft-vp 3 dest-address 47.0091.8100.0000.1061.705b.d900.4000.0c81.9000.00 3 explicit-path 1 name chicago.path1
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.
Switch(config)# interface atm 0/1/3 Switch(config-if)# atm soft-vp 3 redo-explicit explicit-path 1 name chicago.path1 explicit-path 2 name chicago.path2 only-explicit Modify with new explicit path options [yes], or abort changes [no]? [yes/no]:y
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 will not be changed until a soft PVP reroute occurs.
Switch(config)# interface atm 0/1/3 Switch(config-if)# atm soft-vp 3 redo-explicit Modify with new explicit path options [yes], or abort changes [no]? [yes/no]:y
atm pnni explicit-path
show atm addresses
show atm pnni explicit-paths
show atm vp interface
To change the Sustained 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.
atm sustained-cell-rate-margin-factor percent
s-value | Percent value that dictates the weighting of PCR with respect to SCR in computing the bandwidth used in the CAC of VBR connections. |
1 percent
Global configuration
The following equation is used in the CAC of VBR connections to define the bandwidth requested.
bandwidth = (SCRMF * (PCR-SCR))/100 + SCR
In the following example, the SCRMF of the switch is set to 35 percent.
Switch(config)# atm sustained-cell-rate-margin-factor 35
To install frame discard and to select the criteria used on SVCs, use the atm svc-frame-discard-on-aal5ie global configuration command. To install frame discard on UNI 4 or PNNI interfaces, use the no form of this command (see "Usage Guidelines").
atm svc-frame-discard-on-aal5ieThis command has no arguments or keywords.
Install packet discard based on the presence of the AAL5 IE in the SETUP message.
Global configuration
The common term "frame discard" is referred to as "packet discard" in the LightStream 1010 VC environment.
This command changes information used by the switch when determining whether to install frame discard on SVCs. UNI 4.0 signalling allows explicit signalling of frame discard. Prior to UNI 4.0, the presence of the AAL5 IE was used to determine whether or not to install frame discard. If the AAL5 IE is present, frame discard is installed.
Use the atm svc-frame-discard-on-aal5ie command to install frame discard if the AAL5 IE is present. Use the no atm svc-frame-discard-on-aal5ie command if frame discard is to be installed on UNI 4 or PNNI interfaces, and only if explicitly requested by the SETUP and CONNECT messages.
The installation of frame discard is controlled by the signalled messages. Even if the configuration specifies using AAL5 IE, if the UNI 4.0 signalling element controlling frame discard is present when the SETUP or CONNECT transits a UNI 4 or PNNI interface, and the AAL5 IE is not present, frame discard is controlled by the TM Options ID.
The signalling element is the Traffic Management Options ID in the ATM Traffic Descriptor Information Element in the SETUP or CONNECT message.
In the following example, the switch behavior is set to not use the AAL5 IE to dictate frame discard.
Switch(config)# no atm svc-frame-discard-on-aal5ie
To change the intended UPC mode to use on the cell flow received into the switch fabric for SVCs on an interface, use the atm svc-upc-intent interface configuration command. Any change in this parameter is applied to SVCs subsequently established on the interface. To assign the default value to the parameter, use the no form of this command.
atm svc-upc-intent [pass | tag | drop]
pass | Cells received on the interface are passed to the switching fabric with no change, regardless of their conformance to the traffic contract. |
tag | Cells received on the interface violating the traffic contract have their CLP bit set prior to entering the switching fabric. |
drop | Cells received on the interface violating the traffic contract are dropped. |
pass
Interface configuration
This configuration parameter determines the UPC to use for SVCs and for the destination leg of soft VC and VP. If policing is desired, it should be applied once for traffic entering a network.
In the following example, the intended UPC for SVCs on an interface is set to tagging.
Switch(config-if)# atm svc-upc-intent tag
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.
atm svcc vci min value
value | Minimum VCI value, in the range of 33 to 16383. |
33
Interface configuration
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 non-autoconfiguration mode.
The following example illustrates how to set the minimum SVCC VCI value on ATM interface 0/0/1 to 100.
Switch(config)# interface atm 0/0/1 Switch(config-if)# atm svcc vci min 100
atm svcc vpi max
atm template-alias
show atm interface
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.
atm svcc vpi max value
value | Maximum VPI value. Allowed values have the following ranges, by interface type: · From 0 to 3 for 25-MB port adapters · 0 only for logical and CPU interfaces · From 0 through 255 for other interfaces |
0 for CPU interfaces; 255 for other interfaces.
Interface configuration
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 non-autoconfiguration mode.
The following example illustrates how to set the maximum SVCC VPI value on ATM interface 0/0/1 to 3.
Switch(config)# interface atm 0/0/1 Switch(config-if)# atm svcc vpi max 3
atm svcc vci min
atm template-alias
show atm interface
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.
atm svpc vpi max value
value | Maximum VPI value. Allowed values have the following ranges, by interface type: · From 0 to 3 for 25-MB port adapters · 0 only for logical and CPU interfaces · From 0 through 255 for other interfaces |
0 for CPU interfaces; 255 for other interfaces.
Interface configuration
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.
The following example illustrates how to set the maximum SVPC VPI value on ATM interface 0/0/1 to 3.
Switch(config)# interface atm 0/0/1 Switch(config-if)# atm svpc vpi max 3
atm svcc vci min
atm svcc vpi max
show atm interface
To configure an ATM address template alias, use the atm template-alias global configuration command. To delete the specified alias, use the no form of this command.
atm template-alias name template
name | Name for the template alias. |
template | ATM address template, which can be a single ATM address that matches itself or contains wildcards and/or prefixes or suffixes, allowing a single template to match many addresses. The symbols used for wildcards, prefixes, and suffixes are as follows: · Asterisk (*) to match any single 4-bit nibble in the address. · Ellipsis (...) to match any number of leading or trailing 8-bit hexadecimal digits in the address. · Asterisk (*) to match any single binary digit in a 4-bit nibble in the address, where the 4 binary bits are enclosed within parentheses. |
No alias list is defined.
Global configuration
Address templates are pattern forms that match one or more ATM addresses. They can be simple, single ATM addresses matching themselves or containing wildcards, prefixes, and suffixes, allowing a single template to match many addresses.
The simplest address template matches a single address, as shown in this example.
Switch(config)# 47.0005.1234.5678.9abc.def0.00
Wildcard digits, which can match any value, are indicated with asterisks (*). The following template matches the above address and any other 12-byte address that starts with 47.0005.1234.5678.
Switch(config)# 47.0005.1234.5678.****.****.**
The following template matches any address of any length and begins with the prefix 47.0005.1234.5678.
Switch(config)# 47.0005.1234.5678...
In other cases, matching a suffix of the address is also important, such as when matching system IDs. The following template matches any address ending with the suffix 0000.0c01.2345.00.
Switch(config)# ...0000.0c01.2345.00
You might want to match addresses on a single-bit granularity, rather than half-byte (4-bit or nibble) granularity.
This pattern matching is supported by allowing the hex digits that represent four bits to be replaced by groups of four binary bits, represented by the numbers 0 and 1. These four binary digits are enclosed within parentheses. The following template matches any address that starts with 47.0005 followed by the binary bits 10. The final two binary bits in the nibble can be either 0 or 1 and are represented with asterisks.
Switch(config)# 47.0005.(10**)...
Use this command to define aliases for commonly referenced address templates. The use of these aliases reduces the chances for typographical error in the creation of ATM filter sets.
The following example shows setting ATM template aliases.
Switch(config)# atm template-alias atm_addr1 47.1328... Switch(config)# atm template-alias atm_addr2 47.0012.(10**)... Switch(config)# atm template-alias atm_addr3 ...1234.(01*1)
show running-config
write terminal
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.
id-num | Module identification number. (Catalyst 8540 MSR) |
tg-num | Threshold group number, in the range of 1 to 6. |
pct | The percentage of queue-full in the threshold. To disable the threshold, use 100. The range is 0 to 100. |
87 percent
Global configuration
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.
The following example demonstrates configuring the discard threshold for group 3 to 50 percent.
Switch(config)# atm threshold-group 3 discard-threshold 50
atm threshold-group max-cells
atm threshold-group max-queue-limit
atm threshold-group min-queue-limit
show atm resource
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.
id-num | Module identification number. (Catalyst 8540 MSR) |
tg-num | Threshold group number, in the range of 1 through 6. |
pct | The percentage of queue-full in the threshold. To disable the threshold, use 100. The range is 0 to 100. |
25 percent
Global configuration
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.
The following example demonstrates configuring the marking threshold for group 3 to 50 percent.
Switch(config)# atm threshold-group 3 marking-threshold 50
atm threshold-group max-cells
atm threshold-group max-queue-limit
atm threshold-group min-queue-limit
show atm resource
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.
id-num | Module identification number. (Catalyst 8540 MSR) |
tg-num | Threshold group number, in the range of 1 to 6. |
cell-num | Cell number, in the range of 0 to 65535. |
65535
Global configuration
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.
The following example shows how to set the maximum number of cells for threshold group
3 to 32000.
Switch(config)# atm threshold-group 3 max-cells 32000
atm threshold-group discard-threshold
atm threshold-group marking-threshold
atm threshold-group max-queue-limit
atm threshold-group min-queue-limit
show atm resource
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.
id-num | Module identification number. (Catalyst 8540 MSR) |
tg-num | Threshold group number, in the range of 1 to 6. |
cells | Number of cells. This value is limited to the lesser of 16383 or the value specified with the |
Depends on the threshold group.
Global configuration
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.
The following example shows setting the maximum queue limit for group 3 to 16383.
Switch(config)# atm threshold-group 3 max-queue-limit 16383
atm threshold-group discard-threshold
atm threshold-group marking-threshold
atm threshold-group max-cells
atm threshold-group min-queue-limit
show atm resource
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.
id-num | Module identification number. (Catalyst 8540 MSR) |
tg-num | Threshold group number, in the range of 1 to 6. |
cells | Number of cells. This value is limited to the lesser of 1023 or the value specified by the atm threshold-group max-queue-limit command. |
Depends on the threshold group.
Global configuration
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 following example shows setting the minimum queue limit for group 3 to 31.
Switch(config)# atm threshold-group 3 min-queue-limit 31
atm threshold-group discard-threshold
atm threshold-group marking-threshold
atm threshold-group max-queue-limit
atm threshold-group max-cells
show atm resource
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.
id-num | Module identification number. (Catalyst 8540 MSR) |
tg-num | Threshold group number, in the range of 1 to 5. |
tg-name | Threshold group name, in the range of 1 to 15 characters. |
1 - cbr-default
2 - vbrrt-default
3 - vbrnrt-default
4 - abr-default
5 - ubr-default
Global configuration
You cannot rename the well-known VC threshold group.
The following example shows changing the name of threshold group 3 to bigq.
Switch(config)# atm threshold-group 3 name bigq
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.
atm threshold-group service {cbr | vbr-rt | vbr-nrt | abr | ubr} tg-num
cbr | The constant bit rate parameter. |
vbr-rt | The variable bit rate real-time parameter. |
vbr-nrt | The variable bit rate when the parameter is not real-time. |
abr | The available bit rate parameter. |
ubr | The unspecified bit rate parameter. |
tg-num | Threshold group number, in the range of 1 to 5. |
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
Global configuration
The following example shows setting the threshold group to use subsequently in connection setup for CBR connections to group 3.
Switch(config)# atm threshold-group service cbr 3
show atm resource
To configure an ATM UNI on the specified physical or logical port, use the atm uni interface configuration command.
atm uni [side side] [version ver] [type type]
side | Specified as user | network. The default is network. |
ver | Specified as 3.0, 3.1, or 4.0 |
type | Specified as private | public. The default is private. |
See "Syntax Description."
Interface configuration
Before using this command, ILMI autoconfiguration must be disabled (see the atm auto-configuration command). When autoconfiguration is disabled, the interface continues to run without disruption. The same interface parameters are used in subsequent interface restarts. 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.
The atm auto-configuration, atm iisp, and atm nni commands are mutually exclusive. Configuring the atm uni command overwrites any previous configuration of the atm iisp or
atm nni commands for this interface. Future configuration of the atm auto-configuration, atm iisp, or atm uni command on this interface overwrites the atm uni command.
The following example configures ATM interface 3/1/1 as the network side of a private UNI running version 3.1, with the maximum number of active VCI bits set to 10.
Switch# interface atm 3/1/1 Switch(config-if)# no atm auto-configuration Switch(config-if)# %ATM-6ILMIOAUTOCFG: ILMI(ATM/0/0): Auto-configuration is disabled, current interface parameters will be used at next interface restart. Switch(config-if)# atm uni version 3.1 Switch(config-if)# atm maxvci-bits 10
The following example configures ATM interface 1/1/3 as the user side of a public UNI.
Switch# interface atm 1/1/3 Switch(config-if)# no atm auto-configuration Switch(config-if)# %ATM-6-ILMINOAUTOCFG: ILMI(ATM1/1/3): Auto-configuration is disabled, current interface parameters will be used at next interface restart. Switch(config-if)# atm uni side user type public Switch(config-if)# %ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM1/1/3.
atm auto-configuration
atm iisp
atm nni
show atm interface
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.
protocol protocol-address atm-vc vci [class class-name] [broadcast] [aal5mux]
protocol | The keyword ip. |
protocol-address | The destination address being mapped to this PVC. |
vci | Is 31 < vci < 2**14 - 1 (default max-VCI bits is 14). |
class-name | The name of a table that contains encapsulation-specific parameters. Such a table can be shared between maps that have the same encapsulation. |
broadcast | This map entry is to be used when the corresponding protocol sends broadcast packets to the interface. |
aal5mux | Specifies AAL5 multiplexing encapsulation. The default is snap. |
No map statements are defined.
Map-list configuration
This command is required with the map-list command when you are configuring an SVC.
The following example show creating a map-list named atm, followed by a map statement for the protocol address being mapped.
Switch(config)# map-list atm Switch(config-map-list)# ip 172.21.168.112 atm-vc 99
Posted: Mon Aug 16 14:40:00 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.