|
|
This chapter describes special features added to the LightStream 1010 switch configuration software. Most LightStream 1010 ATM switch users probably will not use these features.
This chapter includes the descriptions and examples you need to configure the following special features:
The ATM interface to a public network commonly uses an E.164 address for ATM signaling, with network service access point (NSAP) addresses carried in the subaddress fields of the message.
Configuring an E.164 one-to-one translation table to an interface is a two step process and is described in this section.
Step 1 Configure an interface as an E.164 interface.
Step 2 Configure the E.164 Translation table.
The one-to-one translation table allows signaling to look up the E.164 addresses and the NSAP addresses in a database, allowing a one-to-one correspondence between NSAP addresses and E.164 addresses.
Egress Operation---When a signaling message attempts to establish a call out an interface, the called and calling party addresses are in NSAP format.
If the interface has been configured for E.164 translation, signaling attempts to find a match for the NSAP addresses. If found, the E.164 addresses corresponding to the NSAP addresses are placed into the called and calling party addresses. The original NSAP addresses are also placed into the called and calling party subaddresses.
Ingress Operation---If the interface is configured for 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 will be used to forward the call.
If subaddresses are not present due to the network blocking them, or to the switch at the entry to the E.164 network not using subaddresses, signaling attempts to find a match for the NSAP address in the ATM E.164 translation table.
E.164 Addresses in the Translation Table---If matches are found, the NSAP addresses corresponding to the E.164 addresses will be placed into the called and calling party addresses. The call is then forwarded using the NSAP addresses.
Configuring one-to-one E.164 translation tables requires the following steps:
Step 1 Configure specific ATM interface(s) to connect to E.164 public networks to use the translation table.
Step 2 Configure the translation table.
Step 3 Add entries to the translation table for both the called and calling parties.
This section describes configuration of E.164 translation on the interface. Use the no form of the following commands to disable translation.
| Task | Command |
|---|---|
At the privileged EXEC prompt, enter configuration mode from the terminal. | |
Select interface port. | interface atm card/subcard/port |
Configure the ATM E.164 interface. | |
Return to EXEC configuration mode. | ex |
Change to E.164 ATM configuration mode. | |
Configure the E.164 translation table. |
| 1This command is documented in the LightStream 1010 ATM Switch Command Reference (11.2) publication. |
The following example shows how to configure the ATM interface 0/0/1 to use the one-to-one E.164 translation table:
Switch# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface atm 0/0/1
Switch(config-if)# atm e164 translation
Switch(config-if)# exit
Switch(config)# atm e164 translation-table
Switch(config-atm-e164)# e164 address 1111111 nsap-address 11.111111111111111111111111.112233445566.11
Switch(config-atm-e164)# e164 address 2222222 nsap-address 22.222222222222222222222222.112233445566.22
Switch(config-atm-e164)# e164 address 3333333 nsap-address 33.333333333333333333333333.112233445566.33
In order, these commands:
1. Change to interface configuration mode for ATM interface 0/0/1.
2. Enable ATM E.164 translation on the interface.
3. Exit interface configuration mode.
4. Change to ATM E.164 configuration mode.
5. Add the E.164 address 1111111 to NSAP address 11.11111... translation table entry.
6. Add the E.164 address 2222222 to NSAP address 22.22222... translation table entry.
7. Add the E.164 address 3333333 to NSAP address 33.33333... translation table entry.
Use the show running-config command to display the ATM E.164 translation table configuration.
To display the ATM E.164 translation table configuration, use the following EXEC mode commands:
| Task | Command |
|---|---|
Display the E.164 translation table configuration. | show running-config |
Display the E.164 address configuration on a per-port basis. | show atm interface atm card/subcard/port |
The following example shows how to display the E.164 translation table configuration:
Switch# show running-config
Building configuration... Current configuration: ! version 11.2 no service pad service udp-small-servers service tcp-small-servers ! hostname Switch ! ! username dtate ! atm e164 translation-table e164 address 1111111 nsap-address 11.111111111111111111111111.112233445566.11 e164 address 2222222 nsap-address 22.222222222222222222222222.112233445566.22 e164 address 3333333 nsap-address 33.333333333333333333333333.112233445566.33 ! atm service-category-limit cbr 64544 atm service-category-limit vbr-rt 64544 atm service-category-limit vbr-nrt 64544 atm service-category-limit abr-ubr 64544 atm address 47.0091.8100.0000.0040.0b0a.2b81.0040.0b0a.2b81.00 --More-- <Information Deleted> Switch#
The following example shows how to display the E.164 configuration for an ATM interface 0/0/1:
Switch# show atm interface atm 0/0/1
Interface: ATM0/0/1 Port-type: oc3suni
IF Status: DOWN Admin Status: administratively 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: 8 Max-VCI-bits: 14
Max-VP: 255 Max-VC: 16383
Svc Upc Intent: pass Signalling: Enabled
ATM Address for Soft VC: 47.9999.9999.0000.0000.0000.0216.4000.0c80.0010.00
ATM E164 Translation Interface
Configured virtual links:
PVCLs SoftVCLs SVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Installed-Conns
2 0 0 0 0 0 2 0
Logical ports(VP-tunnels): 0
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
Input AAL5 pkts: 0, Output AAL5 pkts: 0, AAL5 crc errors: 0
Switch#
This section describes manual configuration of signaling on the switch and contains the following subsections:
You enable signaling information element (IE) forwarding of the specified IE from the calling party to the called party.
To configure interface signaling IE transfer, use the following EXEC mode commands:
| Task | Command |
|---|---|
At the privileged EXEC prompt, enter configuration mode from the terminal. | configure1 |
Select the interface to be configured. | interface atm card/subcard/port |
Configure the signaling information element forwarding. | atm signalling ie forward {aal-info | all | bli-repeat-ind | called-subaddress | calling-number | higher-layer-info | lower-layer-info | unknown-ie} |
| 1These commands are documented in the LightStream 1010 ATM Switch Command Reference (11.2) publication. |
The following example shows how to disable signaling of all forwarded IEs on ATM interface 0/0/0:
Switch# config t
Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# interface atm 0/0/0
Switch(config-if)# no atm signalling ie forward all
Switch(config-if)#
To display the interface signaling IE forwarding configuration, use the following EXEC mode command:
| Task | Command |
|---|---|
Display the interface signaling IE forwarding configuration. |
The following example displays the modified configuration of the signaling IE forwarding:
Switch# show running-config
Building configuration... Current configuration: ! version 11.2 no service pad service udp-small-servers service tcp-small-servers ! hostname Switch ! <Information Deleted> ! interface ATM0/0/0 no atm signallling ie forward calling-number no atm signallling ie forward calling-subaddress no atm signallling ie forward called-subaddress no atm signallling ie forward higher-layer-info no atm signallling ie forward lower-layer-info no atm signallling ie forward blli-repeat-ind no atm signallling ie forward aal-info ! interface ATM0/0/1 ! interface ATM0/0/2 !
Signaling diagnostics allow you to diagnose a specific call failure in your network and pinpoint the location of the call failure along with the reason for the failure. To do this, you must configure a signaling diagnostics table that stores the filtering criteria and a filter index, an integer value between 1 and 50, used for uniquely identifying each set of filtering criteria you select. Each filtering criteria occupies one entry in the signaling diagnostics table. Each entry in the filter table is entered using command-line interface (CLI) commands or Simple Network Management Protocol (SNMP). Then the diagnostics software module, when enabled, filters rejected calls based on the entries in your filter table. A successful match in the filter table causes the rejected call information to be stored for analysis.
To configure the signaling diagnostics table entries, use the following EXEC mode commands:
| Task | Command |
|---|---|
At the privileged EXEC prompt, enter configuration mode from the terminal. | configure1 |
Enable signaling diagnostics from EXEC mode. | atm signalling diagnostics enable |
Change to signaling diagnostics configuration mode. | atm signalling diagnostics 1-50 |
Configure the timeout value for the entry in seconds. | age-timer seconds |
Configure a filtering criteria based on the calling address mask value to be used to identify the valid bits of the calling NSAP address of the rejected call. | calling-address-mask nsap_address_mask2 |
Configure a filtering criteria based on the called NSAP address of the rejected call. | called-nsap-address nsap_addrress |
Configure a filtering criteria based on the called address mask value used to identify the valid bits of the calling NSAP address of the rejected call. | called-address-mask nsap_address_mask2 |
Configure a filtering criteria based on the calling NSAP address of the rejected call. | calling-nsap-address nsap_addrress |
Configure a filtering criteria based on the cast type of the rejected call. (The default is all.) | cast-type {p2p | p2mp | all} |
Configure a filtering criteria based on the cleared cause code of the rejected call. | clear-cause number3 |
Configure a filtering criteria based on the VC connection category of the rejected call. | connection-category {soft-vc | soft-vp | reg-vc | all} |
Configure a filtering criteria based on the incoming port of the rejected call. | incoming-port atm card/subcard/port |
Configure the maximum number of entries to be stored in the display table for each of the entries in the filter table. | max-records number |
Configure a filtering criteria based on the outgoing port of the rejected call. | outgoing-port atm card/subcard/port |
Purge all the filtered records in the filter table. | |
Configure a filtering criteria based on the scope of the rejected call which either failed internally in the switch or externally on other switches. | scope {internal | external} |
Configure a filtering criteria based on the service category of the rejected call. | service-category {cbr | abr | vbr-rt | vbr-nrt | ubr | all} |
Configure the status of the entry in the filter table. | status [active filter_criteria | inactive filter_criteria | delete filter_criteria] |
The display table contains the records that were collected based on every filtering criteria in the filter table. Each filtering criteria has only a specified number of records that are stored in the table. After that specified number of records is exceeded, the table is overwritten.
The following example shows how to enable signaling diagnostics on the switch:
Switch# config t
Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# atm signalling diagnostics enable
Switch(config)#
The following example shows how to configure filter criteria in signaling diagnostics index 1 for call failures based on the service category:
Switch# config t
Enter configuration commands, one per line. End with CNTL/Z. Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# service-category cbr Switch(cfg-atmsig-diag)# service-category ubr
Switch(cfg-atmsig-diag)# service-category abr ubr
The following example shows how to configure filter criteria for call failures based on the category of the virtual circuit:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# connection-category soft-vc
Switch(cfg-atmsig-diag)# connection-category soft-vc soft-vp
The following example shows how to configure filter criteria for calls rejected based on the connection type:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# cast-type p2p p2mp
The following example shows how to configure filter criteria for calls that failed internally in the switch.
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# scope internal
The following example shows how to configure the filter entry for filtering failed calls that came in through interface ATM1/1/1:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# incoming-port ATM1/1/1
The following example shows how to configure the filter entry for filtering failed calls that went out through interface ATM1/1/1:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# outgoing-port ATM1/1/1
The following example shows how to configure the filter entry for filtering failed calls based on the clear cause value 3 (destination unreachable):
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# clearcause 3
The following example shows how to configure filter criteria for calls rejected based on the calling NSAP address of the call:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# calling-nsap-address 47.0091810000000061705BD901.010203040506.0.
The following example shows how to configure filter criteria for calls rejected based on the called NSAP address of the call.
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# called-nsap-address 47.0091810000000061705BD901.010203040506.0
The following example shows how to configure filter criteria for calls rejected based on the called address mask of the call:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# called-address-mask ff.ff.ff.00
The following example shows how to configure filter criteria for calls rejected based on the calling address mask of the call:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# calling-address-mask ff.ff.ff.00
The following example shows how to specify the timeout value for the entry in seconds:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# age-timer 3600
The following example shows how to purge all the filtered records corresponding to this entry in the filter table:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# purge
The following example shows how to delete an index entry in the filter table:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# status delete
The following example shows how to specify the maximum number of entries to be stored in the display table for each of the entries in the filter table:
Switch(config)# atm signalling diagnostics 1
Switch(cfg-atmsig-diag)# max-records 40
To display the signaling diagnostics information, use the following EXEC mode commands:
| Task | Command |
|---|---|
Display the ATM signaling diagnostics for a record. | show atm signalling diagnostics record filter_index |
Display the ATM signaling diagnostics for a filter. | |
Display the ATM signaling diagnostic status. | show atm signalling diagnostics status |
The following example displays the signaling diagnostic records for index 1:
Switch# show atm signalling diagnostics record 1
D I S P L A Y I N D E X 1 -------------------------------- Scope: internal, Cast Type: p2p, Conn Indicator: Setup Failure Connection Kind: switched-vc Service Category: UBR (Unspecified Bit Rate) Clear Cause: 0x29, Diagnostics: NULL Incoming Port: ATM1/0/3, Outgoing Port:ATM0/1/3 Calling-Address: 47.009181000000006011000000.470803040506.00 Calling-SubAddr: NULL Called-Address : 47.009181000000006083C42C01.750203040506.00 Called-SubAddr : NULL Crankback Type : No Crankback DTL's : NodeId:56:160:47.009181000000006011000000.006083AB9001.00 Port: 0/1/3:2 NodeId:56:160:47.00918100000000603E7B4101.00603E7B4101.00 Port: 0/0/0:2 NodeId:56:160:47.009181000000006083C42C01.006083C42C01.00 Port: 0 Switch#
The following example displays the signaling diagnostics data for filter index 1:
Switch# show atm signalling diagnostics filter 1
F I L T E R I N D E X 1 ------------------------------ Scope: internal, Cast Type: p2mp Connection Kind: soft-vc Service Category: CBR (Constant Bit Rate) UBR (Unspecified Bit Rate) Clear Cause: 0, Initial TimerValue: 600 Max Records: 20, NumMatches: 0, Timer expiry: 600 Incoming Port: ATM0/0/1, Outgoing Port: ATM0/1/1 Calling Nsap Address:47.111122223333444455556666.777788889999.00 Calling Address Mask:FF.FFFFFF000000000000000000.000000000000.00 Called Nsap Address :47.111122223333444455556666.777788889999.01 Called Address Mask :FF.FFFFFF000000000000000000.000000000000.00 Status : active Switch#
The following example displays the signaling diagnostics status:
Switch# show atm signalling diagnostics status
Signalling diagnostics disabled globally Switch#
You can configure a closed user group (CUG) to form restricted access groups (virtual private networks). Different CUGs can be defined and a specific user can be a member of one or more CUGs. Members of a CUG can communicate among themselves, but not, with users outside the group. Specific users can have additional restrictions that prevent them from originating or from receiving calls from other members of the CUG. You can also specify additional restrictions on originating and receiving calls to or from members of other CUGs.
For example, if you configure three CUGs (A, B and C) in your network, you can configure them so that groups B and C can communicate with group A without restriction, but groups B and C cannot communicate between each other.You can also configure specific members of the same group to not accept calls from members of the same group.
The basis for CUGs are interlock codes. Interlock codes are unique in the whole network. Members belonging to a CUG are assigned a unique interlock code. Members of CUGs will use this interlock code while communicating with other members of the same or different CUGs.
Interlock code is passed in CUG interlock code information element (CUG IC IE). The CUG IE also carries information that specifies if the call can go through if the called party is not a member of the specified CUG. At the network boundary where the call originates, when a call is received from the user, the switch generates the CUG IE and sends it as part of the SETUP message. In this software release, the CUG IE can only contain the preferential CUG's interlock code. The CUG IE is used at the destination network interface to determine if the call should be forwarded or rejected. The CUG IE is forwarded transparently by the intermediate switches.
Two types of interlock codes are defined:
Figure 15-1 provides an example of a CUG and is described in the following:
The following steps describe some CUG calls shown in Figure 15-1:
The following sections describe configuring CUGs:
You can define an alias for each CUG interlock code used on the switch. Using an alias can simplify configuration of a CUG on multiple interfaces. When you use an alias, you no longer need to specify the 48-hexadecimal-digit CUG interlock code on each interface attached to a CUG member.
To configure an aliases for a CUG interlock code, use the following EXEC mode commands:
| Task | Command |
|---|---|
At the privileged EXEC prompt, enter configuration mode from the terminal. | configure1 |
Configure the alias for the CUG interlock code. | atm signalling cug alias alias_name interlock-code interlock_code |
| 1These commands are documented in the LightStream 1010 ATM Switch Command Reference (11.2) publication. |
The following example shows how to configure the alias TEST for the CUG interlock code 4700918100000000603E5A790100603E5A790100.12345678:
Switch# config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# atm signalling cug alias TEST interlock-code 4700918100000000603E5A790100603E5A790100.12345678
Switch(config)#
This section describes CUG configuration on interfaces.
Your first step in CUG configuration is to identify the access interfaces. Transmission and reception of CUG interlock codes is not allowed over access interfaces. By configuring all interfaces leading outside of the network as access interfaces ensures that all CUG interlock codes are generated and used only within this network.
You implement CUG procedures only if you configure the interface as an access interface.
Each access interface can be configured to permit or deny calls either from user(s) attached to this interface or to unknown users that are not members of this interface's CUG(s). In International Telecommunications Union Telecommunications Standardization Sector (ITU-T) terminology, this is called outgoing access. Similarly, each access interface can be configured to permit or deny calls either to the user(s) attached to this interface or from unknown users that are not members of this interface's CUG(s). In ITU-T terminology, this is called incoming access.
You can configure each access interface to have one or more CUGs associated with it, but only one CUG can be selected as the preferential CUG. In this software release, 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 for the interface.
For each CUG configured on the interface, you can specify that calls to or from other members of the same CUG be denied. In ITU-T terminology, this is called outgoing-calls-barred (OCB) and incoming-calls-barred (ICB), respectively.
Table 15-1 describes the relationship between the ITU-T CUG terminology and Cisco CUG terminology:
| ITU-T CUG Terminology | Cisco CUG Terminology |
|---|---|
preferential CUG | preferential |
incoming access allowed | permit-unknown-cugs to-user |
outgoing access allowed | permit-unknown-cugs from-user |
incoming calls barred (ICB) | deny-same-cug to-user |
outgoing calls barred (OCB) | deny-same-cug from-user |
To configure an access interface and the CUG(s) in which the interface is a member, use the following EXEC mode commands:
| Task | Command |
|---|---|
At the privileged EXEC prompt, enter configuration mode from the terminal. | configure1 |
Specify an ATM interface and enter interface configuration mode. | interface atm card/subcard/port |
Configure the interface as a CUG access interface. | atm signalling cug access [permit-unknown-cugs {to-user | from-user permanent | both-direction permanent}] |
Configure the CUG where this interface is a member. | atm signalling cug assign {alias alias_name | interlock-code interlock_code} [deny-same-cug {to-user | from-user}] [preferential] |
| 1These commands are documented in the LightStream 1010 ATM Switch Command Reference (11.2) publication. |
The following example shows how to configure an interface as a CUG access interface and to assign a preferential CUG.
Switch# config t
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# interface atm 3/0/0
Switch(config-if)# atm signalling cug access permit-unknown-cugs both-direction permanent
Switch(config-if)# atm signalling cug assign interlock-code 4700918100000000603E5A790100603E5A790100.12345678 preferential
Switch(config-if)#
To display the global CUG configuration, use the following EXEC mode commands:
| Task | Command |
|---|---|
Display the CUG interface configuration status. | |
Display the CUG global configuration status. | show running-config |
The following example displays the global CUG configuration using the show atm signalling cug command:
Switch# show atm signalling cug
Interface: ATM3/0/0 Cug Alias Name: Cug Interlock Code: 4700918100000000603E5A790100603E5A790100.12345678 Non preferential Cug Permit Network to User Calls Permit User to Network Calls Switch#
The following example displays the global CUG access configuration using the show atm signalling cug access command:
Switch# show atm signalling cug access
Closed User Group Access Interface Parameters: Interface: ATM3/0/0 Network To User (incoming) access: Permit calls from unknown CUGs to User User To Network (outgoing) access: Permit permanent calls to unknown groups Switch#
The following example displays the CUG global configuration using the show running-config command:
Switch# show running-config
Building configuration... Current configuration: ! version 11.2 no service pad service udp-small-servers service tcp-small-servers ! hostname ls1010-2 ! ! atm signalling cug alias TEST interlock-code 47.0091810000000061705BDA01.0061705BDA01.00.12345678 ! atm address 47.0091.8100.0000.0061.705b.da01.0061.705b.da01.00 <Information Deleted> ! ! interface ATM0/0/0 atm signalling cug access permit-unknown-cugs both-direction permanent ! interface ATM0/0/1 <Information Deleted> Switch#
To display the ATM signaling statistics, use the following EXEC mode command:
| Task | Command |
|---|---|
Display the ATM signaling statistics. |
The following example displays the ATM signaling statistics:
Switch# show atm signalling statistics
Global Statistics:
Calls Throttled: 0
Max Crankback: 3
Max Connections Pending: 255
Max Connections Pending Hi Water Mark: 1
ATM 2/0/0:0 UP Time 01:06:20 # of int resets: 0
----------------------------------------------------------------
Terminating connections: 0 Soft VCs: 0
Active Transit PTP SVC: 0 Active Transit MTP SVC: 0
Port requests: 0 Source route requests: 0
Conn-Pending: 0 Conn-Pending High Water Mark: 1
Calls Throttled: 0 Max-Conn-Pending: 40
Messages: Incoming Outgoing
--------- -------- --------
PTP Setup Messages: 0 0
MTP Setup Messages: 0 0
Release Messages: 0 0
Restart Messages: 0 0
Message: Received Transmitted Tx-Reject Rx-Reject
Add Party Messages: 0 0 0 0
Failure Cause: Routing CAC Access-list Addr-Reg Misc-Failure
Location Local: 0 0 0 0 12334
Location Remote: 0 0 0 0 0
ATM 0/0/3:0 UP Time 3d21h # of int resets: 0
----------------------------------------------------------------
Terminating connections: 0 Soft VCs: 0
Active Transit PTP SVC: 0 Active Transit MTP SVC: 0
Port requests: 0 Source route requests: 0
Conn-Pending: 0 Conn-Pending High Water Mark: 0
Calls Throttled: 0 Max-Conn-Pending: 40
<Information Deleted>
Switch#
If you disable signaling on a PNNI interface, PNNI routing is also disabled and ILMI is automatically restarted whenever signaling is enabled or disabled.
To disable signaling on an interface, use the following EXEC commands. Use the no form of the atm signalling command to disable
| Task | Command |
|---|---|
At the privileged EXEC prompt, enter configuration mode from the terminal. | |
Select the interface to be configured. | interface atm card/subcard/port |
Disable signaling on the interface. | no atm signalling enable |
Return to EXEC configuration mode. | ^Z |
| 1This command is documented in the LightStream 1010 ATM Switch Command Reference (11.2) publication. |
The following example shows how to shut down signaling on ATM interface 0/1/2:
Switch# config t
Enter configuration commands, one per line. End with CNTL/Z. 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. Switch(config-if)# ^Z
Switch#
Use the atm svc-frame-discard-on-aal5ie command to select the criteria used to install frame discard on switched virtual circuits (SVCs). The default is to install packet discard based on the presence of the ATM adaptation layer 5 (AAL5) information element in the SETUP message.
You can use the global configuration function to modify the frame discard for all available bit rate (ABR) connections.
To configure frame discard, perform the following tasks in global configuration mode:
| Task | Command |
|---|---|
At the privileged EXEC prompt, enter configuration mode from the terminal. | configure1 |
Configure the SVC frame discard. |
| 1These commands are documented in the LightStream 1010 ATM Switch Command Reference (11.2) publication. |
This global configuration command changes the information that the switch uses to decide whether or not to install frame discard on SVCs. User-Network Interface (UNI) 4.0 signaling allows for explicit signaling of frame discard. Pre-UNI 4.0 versions use the presence of the AAL5 information elements to determine whether or not to install frame discard (if the AAL5 information element is present, frame discard is installed; otherwise do not).
For example:
In the following example, the switch behavior is set to not use the AAL5 information element to dictate frame discard.
Switch(config)# no atm svc-frame-discard-on-aal5ie
Switch(config)#
To display the ATM frame discard configuration, perform the following task in user EXEC mode:
| Task | Command |
|---|---|
Display the frame discard configuration. | show running-config |
The following example shows how to display the frame discard configuration:
Switch# show running-config
Switch# show running-config Building configuration... Current configuration: ! ! Last configuration change at 19:02:51 UTC Thu Feb 27 1997 ! version 11.2 no service pad service udp-small-servers service tcp-small-servers ! hostname Switch ! boot bootldr bootflash:/tftpboot/rbhide/ls1010-wp-mz.112-1.4.WA3.0.15 ! network-clock-select 1 ATM0/0/0 network-clock-select 4 ATM0/0/0 ip host-routing no atm svc-frame-discard-on-aal5ie
|
|