|
|
This chapter describes the signalling and signalling-related features for the ATM switch router, and includes the following sections:
You enable signalling information element (IE) forwarding of the specified IE from the calling party to the called party.
To configure interface signalling IE transfer, perform the following steps, beginning in global configuration mode:
| Step | Command | Task |
|---|---|---|
| 1 | interface atm card/subcard/port | Select the interface to be configured. |
| 2 | atm signalling ie forward {aal-info | all | bli-repeat-ind | called-subaddress | calling-number | higher-layer-info | lower-layer-info | unknown-ie} | Configure the signalling information element forwarding. |
The following example shows how to disable signalling of all forwarded IEs on ATM interface 0/0/0:
Switch(config)# interface atm 0/0/0 Switch(config-if)# no atm signalling ie forward all
To display the interface signalling IE forwarding configuration, use the following privileged EXEC command:
| Command | Task |
|---|---|
more system:running-config | Display the interface signalling IE forwarding configuration. |
The following example displays the modified configuration of the signalling IE forwarding:
Switch# more system:running-config Building configuration... Current configuration: ! version XX.X 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 ! <information deleted>
You can 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 this global configuration function to modify frame discard for all connections.
To configure frame discard, use the following command in global configuration mode:
| Command | Task |
|---|---|
Configure the SVC frame discard. |
This command changes the information that the ATM switch router uses to decide whether or not to install frame discard on SVCs. User-Network Interface (UNI) 4.0 signalling allows for explicit signalling 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 it is not.
For example:
In the following example, the ATM switch router behavior is set to not use the AAL5 information element to dictate frame discard.
Switch(config)# no atm svc-frame-discard-on-aal5ie
To display the ATM frame discard configuration, use the following privileged EXEC command:
| Command | Task |
|---|---|
more system:running-config | Display the frame discard configuration. |
The following example shows how to display the frame discard configuration:
Switch# more system:running-config Building configuration... Current configuration: ! version XX.X no service pad service udp-small-servers service tcp-small-servers ! hostname Switch ! network-clock-select 1 ATM0/0/0 network-clock-select 4 ATM0/0/0 ip host-routing no atm svc-frame-discard-on-aal5ie ! <information deleted>
E.164 support allows networks that use E.164 ATM address formats (for example, 45.000001234567777F00000000.000000000000.00) to work with networks that use E.164 address formats (for example, 1-123-456-7777). Generally, E.164 ATM addresses are used in ATM networks, and E.164 addresses are used in telephone networks.
There are several types of E.164 addresses. The ATM switch router supports the following E.164 address formats:
There are three features you can configure on the ATM switch router for E.164 address conversion. The feature you chose depends on the address format you are using. The features are as follows:
 | Caution Manually creating the E.164 to AESA address translation table is a time consuming and error prone process. We strongly recommend that you use either the E.164 gateway or E.164 autoconversion feature instead of the E.164 one-to-one address translation feature. |
Proceed to the appropriate subsection for configuration information.
If your network uses ARB_AESA, you can configure the E.164 gateway feature. To configure the E.164 gateway feature, you must first configure a static ATM route with an E.164 address. Then configure the E.164 address to use on the interface.
This section describes how to configure the E.164 gateway feature and includes the following procedures:
When a static route is configured on an interface, all ATM addresses that match the configured address prefix are routed through that interface to an E.164 address.
Signalling uses E.164 addresses in the called and calling party IEs, and uses AESAs in the called and calling party subaddress IEs.
Figure 16-1 illustrates an E.164 gateway configuration. The AESA address is used to initiate the call at the ingress to the public network. The public network routes the call based on the E.164 address. AESA subaddresses are carried through the public network in the subaddress fields. The AESA address is used to complete the call at the egress from the public network.
To configure an E.164 address static route, use the following command in global configuration mode:
| Command | Task |
|---|---|
atm route address-prefix atm card/subcard/port | At the configure prompt, configure the static route prefix with the E.164 address. |
The following example uses the atm route command to configure a static route using the 13-byte switch prefix 47.00918100000000410B0A1081 to ATM interface 0/0/0 with the E.164 address 1234567:
Switch(config)# atm route 47.00918100000000410B0A1081 atm 0/0/0 e164-address 7654321
To complete the E.164 address static route configuration, proceed to the section "Configure an ATM E.164 Address on an Interface."
To display the E.164 address configuration, use the following privileged EXEC command:
| Command | Task |
|---|---|
Display the static route E.164 address configuration. |
The following example displays the E.164 address configuration using the show atm route privileged EXEC command:
Switch# show atm route
Codes: P - installing Protocol (S - Static, P - PNNI, R - Routing control),
T - Type (I - Internal prefix, E - Exterior prefix, SE -
Summary Exterior prefix, SI - Summary Internal prefix,
ZE - Suppress Summary Exterior, ZI - Suppress Summary Internal)
P T Node/Port St Lev Prefix
~ ~~ ~~~~~~~~~~~~~~~~ ~~ ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
S E 1 ATM0/1/0 DN 0 47.0091.8100.0000.0001/72
P SI 1 0 UP 0 47.0091.8100.0000.0002.eb1f.fe00/104
R I 1 ATM2/0/0 UP 0 47.0091.8100.0000.0002.eb1f.fe00.0002.eb1f.fe00/152
R I 1 ATM2/0/0 UP 0 47.0091.8100.0000.0002.eb1f.fe00.4000.0c/128
P SI 1 0 UP 0 47.0091.8100.0000.0040.0b0a.2b81/104
S E 1 ATM0/0/0 DN 0 47.0091.8100.0000.0040.0b0a.2b81/104
(E164 Address 1234567)
R I 1 ATM2/0/0 UP 0 47.0091.8100.0000.0040.0b0a.2b81.0040.0b0a.2b81/152
R I 1 ATM2/0/0 UP 0 47.0091.8100.0000.0040.0b0a.2b81.4000.0c/128
One E.164 address can be configured per ATM port. Signalling uses E.164 addresses in the called and calling party IEs, and uses AESA addresses in the called and calling party subaddress IEs.
To configure an E.164 address on a per-interface basis, perform the following tasks, beginning in global configuration mode:
| Step | Command | Task |
|---|---|---|
| 1 | interface atm card/subcard/port | Select an interface port. |
| 2 | atm e164 address e164-address | Associate the E.164 address to the interface. |
The following example shows how to configure the E.164 address 7654321 on ATM interface 0/0/1:
Switch(config)# interface atm 0/0/1 Switch(config-if)# atm e164 address 7654321
To display the E.164 configuration, use the following EXEC command:
| Command | Task |
|---|---|
show atm interface atm card/subcard/port | Show the E.164 address configuration on a per-port basis. |
The following example shows how to display the E.164 address configuration for ATM interface 0/0/1:
Switch# show atm interface atm 0/0/1 Interface: ATM0/0/1 Port-type: oc3suni IF Status: UP Admin Status: up Auto-config: enabled AutoCfgState: completed IF-Side: Network IF-type: NNI Uni-type: not applicable Uni-version: not applicable Max-VPI-bits: 8 Max-VCI-bits: 14 Max-VP: 255 Max-VC: 16383 ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 255 ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 255 ConfMinSvccVci: 35 CurrMinSvccVci: 35 Svc Upc Intent: pass Signalling: Enabled ATM Address for Soft VC: 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.0010.00
ATM E164 Address: 7654321 <information deleted>
When the E.164 gateway feature is configured, the switch first attempts to make a connection using the E.164 gateway feature. If that connection fails, the switch attempts to make the connection using the E.164 address autoconversion feature. Proceed to the next section, "Configure E.164 Address Autoconversion," for configuration instructions.
If your network uses E164_ZDSP or E164_AESA addresses, you can configure E.164 address autoconversion. The E164_ZDSP and E164_AESA addresses include an embedded E.164 number in the E.164 portion of an E.164 ATM address. This embedded E.164 number is used in the autoconversion process.
The E.164 portion of an E.164 ATM address is the first 15 digits following the authority and format identifier (AFI) of 45, shown in Figure 16-2. The E.164 portion is right justified and ends with an "F." If all fifteen digits are not being used, the unused digits are filled with zeroes. In Figure 16-2, the embedded E.164 number is 1234567777, but it is signaled at the egress of the switch and in the E.164 public network as 31323334353637373737.
The autoconversion process differs slightly between the E164_ZDSP and E164_AESA address formats. Table 16-1 compares the E.164 address autoconversion process by address type. The main difference between the two types is the way the IEs are signaled at the egress of the switch, as described in the second row of Table 16-1. Note that during the final conversion process, the calling AESA and called AESA return to their original values.
| Action | E164_ZDSP | E164_AESA |
Originates as | Calling AESA: 45.000001234567777F00000000.000000000000.00 Calling subaddress: None Called AESA: 45.000007654321111F00000000.000000000000.00 Called subaddress: None | Calling AESA: 45.000001234567777FAAAAAAAA.BBBBBBBBBBBB.00 Calling subaddress: None Called AESA: 45.000007654321111FCCCCCCCC.DDDDDDDDDDDD.00 Called subaddress: None |
Signalled at egress of switch as | Calling E.164: 31323334353637373737 Calling subaddress: None Called E.164: 37363534333231313131 Called subaddress: None | Calling E.164: 31323334353637373737 Calling subaddress: 45.0000012345677777FAAAAAAAA.BBBBBBBBBBBB.00 Called E.164: 37363534333231313131 Called subaddress: 45.000007654321111FCCCCCCCC.DDDDDDDDDDDD.00 |
Converted back at ingress of switch to | Calling AESA: 45.000001234567777F00000000.000000000000.00 Calling subaddress: None Called AESA: 45.000007654321111F00000000.000000000000.00 Called subaddress: None | Calling AESA: 45.000001234567777FAAAAAAAA.BBBBBBBBBBBB.00 Calling subaddress: None Called AESA: 45.000007654321111FCCCCCCCC.DDDDDDDDDDDD.00 Called subaddress: None |
Figure 16-3 shows an example of an E164_ZDSP address autoconversion. In Figure 16-3, a call (connection) from end system A is placed to end system B on the other side of an E.164 public network. The call originates as an E.164 ATM address and is signaled in native E.164 format at the egress port of switch A and within the E.164 public network. When the call reaches the ingress port of switch B, at the edge of the E.164 public network, the call is converted back to E.164 ATM address format.
Figure 16-4 shows an example of an E164_AESA address autoconversion. In Figure 16-4, a call from end system A is placed to end system B on the other side of an E.164 public network. The call originates as an E.164 ATM address and at the egress port of switch A and within the E.164 public network:
When the call reaches the ingress port of switch B, at the edge of the E.164 public network, the call is converted back to E.164 ATM address format and:
E.164 address autoconversion configuration is the same, regardless of which type of address (E164_ZDSP or E164_AESA) your network uses. To configure E.164 address autoconversion, perform the following steps, beginning in global configuration mode:
| Step | Command | Task |
|---|---|---|
| 1 | atm route address-prefix atm card/subcard/port | At the configure prompt, configure the static route prefix with the E.164 address. |
| 2 | interface atm card/subcard/port | Select the ATM interface. |
| 3 | Configure E.164 autoconversion. | |
| 4 | exit | Return to global configuration mode. |
In the example networks shown in Figure 16-3 and Figure 16-4, interface 0/0/1 of switch A is configured as follows:
Switch(config)# atm route 45.000007654321111F atm 0/0/1 Switch(config)# int atm 0/0/1 Switch(config-if)# atm e164 auto-conversion
Interface 0/0/1 of switch B is configured as follows:
Switch(config)# atm route 45.000001234567777F atm 0/0/1 Switch(config)# int atm 0/0/1 Switch(config-if)# atm e164 auto-conversion
To display the E.164 configuration on an interface, use the following EXEC command:
| Command | Task |
|---|---|
show atm interface atm card/subcard/port | Show the E.164 address configuration on a per-port basis. |
The following example shows how to display the E.164 configuration for 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: down Auto-config: disabled AutoCfgState: not applicable 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 ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 255 ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 255 ConfMinSvccVci: 33 CurrMinSvccVci: 33 Svc Upc Intent: pass Signalling: Enabled ATM Address for Soft VC: 47.0091.8100.0000.0002.eb1f.fe00.4000.0c80.0010.00
ATM E164 Auto Conversion Interface Configured virtual links: PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns 2 0 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
The ATM interface to a public network commonly uses an E.164 address for ATM signalling, with ARB_AESA addresses carried in the subaddress fields of the message.
| Caution Manually mapping AESA addresses to E.164 addresses is a time consuming and error prone process. We highly recommend that you use either the E.164 gateway or E.164 autoconversion feature instead of the E.164 one-to-one address translation feature. |
The one-to-one translation table allows signalling to look up the E.164 addresses and the ARB_AESA addresses in a database, allowing a one-to-one correspondence between ARB_AESA addresses and E.164 addresses.
During egress operation, when a signalling message attempts to establish a call out an interface, the called and calling party addresses are in ARB_AESA format.
If the interface has been configured for E.164 translation, signalling attempts to find a match for the ARB_AESA addresses. If found, the E.164 addresses corresponding to the ARB_AESA addresses are placed into the called and calling party addresses. The original ARB_AESA addresses are also placed into the called and calling party subaddresses.
During 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 ARB_AESA-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, signalling attempts to find a match for the ARB_AESA address in the ATM E.164 translation table.
If matches are found, the ARB_AESA addresses corresponding to the E.164 addresses in the translation table will be placed into the called and calling party addresses. The call is then forwarded using the ARB_AESA 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.
To configure E.164 translation on the interface, perform the following steps, beginning in global configuration mode:
| Step | Command | Task |
|---|---|---|
| 1 | interface atm card/subcard/port | Select an interface port. |
| 2 | Configure the ATM E.164 interface. | |
| 3 | exit | Return to EXEC configuration mode. |
| 4 | Change to E.164 ATM configuration mode. | |
| 5 | e164 address address nsap-address1 nsap-address | Configure the E.164 translation table. |
| 1The NSAP address is the same as the ARB_AESA address. |
The following example shows how to configure the ATM interface 0/0/1 to use the one-to-one E.164 translation table and specifies three table entries:
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
To display the ATM E.164 translation table configuration, use the following EXEC commands:
| Command | Task |
|---|---|
more system:running-config | Display the E.164 translation table configuration. |
show atm interface atm card/subcard/port | Display the E.164 address configuration on a per-port basis. |
The following example shows how to display the E.164 translation table configuration:
Switch# more system:running-config Building configuration... Current configuration: ! version XX.X no service pad service udp-small-servers service tcp-small-servers ! hostname Switch ! 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 ! <information deleted>
The following example shows how to display the E.164 configuration for 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 ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 255 ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 255 ConfMinSvccVci: 35 CurrMinSvccVci: 35 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
Signalling diagnostics enable 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 signalling diagnostics table that stores the filtering criteria and a filter index, an integer value between 1 and 50, used to uniquely identify each set of filtering criteria you select. Each filtering criteria occupies one entry in the signalling 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 signalling diagnostics table entries, perform the following tasks, beginning in global configuration mode:
| Step | Command | Task |
|---|---|---|
| 1 | Enable ATM signalling diagnostics. | |
| 2 | Change to ATM signalling diagnostics configuration mode. | |
| 3 | age-timer seconds | Configure the timeout value for the entry, in seconds. |
| 4 | calling-address-mask nsap-address-mask2 | 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. |
| 5 | called-nsap-address nsap-addrress | Configure a filtering criteria based on the called NSAP address of the rejected call. |
| 6 | called-address-mask nsap-address-mask1 | 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. |
| 7 | calling-nsap-address nsap-address | Configure a filtering criteria based on the calling NSAP address of the rejected call. |
| 8 | cast-type {p2p | p2mp | all} | Configure a filtering criteria based on the cast type of the rejected call. (The default is all.) |
| 9 | clear-cause clear-cause-code2 | Configure a filtering criteria based on the cleared cause code of the rejected call. |
| 10 | connection-category {soft-vc | soft-vp | reg-vc | all} | Configure a filtering criteria based on the VC connection category of the rejected call. |
| 11 | incoming-port atm card/subcard/port | Configure a filtering criteria based on the incoming port of the rejected call. |
| 12 | max-records max-num-records | Configure the maximum number of entries to be stored in the display table for each of the entries in the filter table. |
| 13 | outgoing-port atm card/subcard/port | Configure a filtering criteria based on the outgoing port of the rejected call. |
| 14 | Purge all the filtered records in the filter table. | |
| 15 | scope {internal | external} | Configure a filtering criteria based on the scope of the rejected call which either failed internally in the switch or externally on other switches. |
| 16 | service-category {cbr | abr | vbr-rt | vbr-nrt | ubr | all} | Configure a filtering criteria based on the service category of the rejected call. |
| 17 | status [active filter-criteria | inactive filter-criteria | delete filter-criteria] | Configure the status of the entry in the filter table. |
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 signalling diagnostics on the ATM switch router:
Switch(config)# atm signalling diagnostics enable
The following example shows how to configure filter criteria in signalling diagnostics index 1 for call failures based on the service category:
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 signalling diagnostics information, use the following EXEC commands:
| Command | Task |
|---|---|
show atm signalling diagnostics record filter-index | Display the ATM signalling diagnostics for a record. |
Display the ATM signalling diagnostics for a filter. | |
Display the ATM signalling diagnostic status. |
The following example displays the signalling 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
The following example displays the signalling 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
The following example displays the signalling diagnostics status:
Switch# show atm signalling diagnostics status Signalling diagnostics disabled globally
The following sections describe configuring 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 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.
Two types of interlock codes are defined:
Figure 16-5 provides examples of CUGs and consists of the following components:
Two CUG calls shown in Figure 16-5 are as follows:
You can define an alias for each CUG interlock code used on the ATM switch router. 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 alias for a CUG interlock code, use the following command in global configuration mode:
| Command | Task |
|---|---|
atm signalling cug alias alias-name interlock-code interlock-code | Configure the alias for the CUG interlock code. |
The following example shows how to configure the alias TEST for the CUG interlock code 4700918100000000603E5A790100603E5A790100.12345678:
Switch(config)# atm signalling cug alias TEST interlock-code 4700918100000000603E5A790100603E5A790100.12345678
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. 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 16-2 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, perform the following tasks, beginning in global configuration mode:
| Step | Command | Task |
|---|---|---|
| 1 | interface atm card/subcard/port | Specify an ATM interface and enter interface configuration mode. |
| 2 | atm signalling cug access [permit-unknown-cugs {to-user | from-user permanent | both-directions permanent}] | Configure the interface as a CUG access interface. |
| 3 | atm signalling cug assign {alias alias-name | interlock-code interlock-code} [deny-same-cug {to-user | from-user}] [preferential] | Configure the CUG where this interface is a member. |
The following example shows how to configure an interface as a CUG access interface and assign a preferential CUG.
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
To display the global CUG configuration, use the following EXEC commands:
| Command | Task |
|---|---|
show atm signalling cug | Display the CUG interface configuration status. |
more system:running-config | Display the CUG global configuration status. |
The following example displays the global CUG configuration using the show atm signalling cug EXEC 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
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
The following example displays the CUG global configuration using the more system:running-config command:
Switch# more system:running-config Building configuration... Current configuration: ! version XX.X 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 ! <information deleted>
To display the ATM signalling statistics, use the following EXEC command:
| Command | Task |
|---|---|
Display the ATM signalling statistics. |
The following example displays the ATM signalling 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
ATM0: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>
If you disable signalling on a PNNI interface, PNNI routing is also disabled and ILMI is automatically restarted whenever signalling is enabled or disabled.
| Step | Command | Task |
|---|---|---|
| 1 | interface atm card/subcard/port | Select the interface to be configured. |
| 2 | no atm signalling enable | Disable signalling on the interface. |
The following example shows how to shut down signalling on ATM interface 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.
Multipoint-to-point funnel signalling (funneling) merges multiple incoming SVCs into a single outgoing SVC. An incoming SVC is called a leaf SVC, and the outgoing SVC is called the funnel SVC.
The ATM switch router performs funnel merging on SVCs that originate from the UNI. With the exception of the funnel switch (see Figure 16-6), the multipoint-to-point funnel appears to the network as a point-to-point connection.
Figure 16-6 illustrates multipoint-to-point funnel signalling.
Mulitpoint-to-point funnel signalling requires no configuration. For funneling to operate, traffic parameters must be the same for all the SVC leaves on a particular funnel call. The aggregate bandwidth of the source links (SVC leaves) cannot exceed the bandwidth allocated to the funnel link. A maximum of 255 links (leaf SVCs) can join the funnel link. Arbitration is performed between the sources to avoid overloading of the funnel link by the application running.
When the ATM switch router receives a setup message containing a leaf-initiated join information element, the ATM switch router searches for funnel SVCs with existing connections to the destination. The leaf-initiated join information element connection ID and the destination ATM address uniquely identify each funnel SVC.
If a funnel SVC to the same destination arrives with the same leaf-initiated join element connection ID, as one that is already present, the ATM switch router checks to see if the traffic parameters specified in the incoming setup message are the same as those in the funnel SVC. If the parameters are the same, then the leaf is joined to the funnel SVC, and the connection is acknowledged. If the traffic parameters are different, then the setup request is denied. If a funnel SVC to the specified destination is not available when an incoming setup message arrives, then a point-to-point SVC is set up to transmit the message.
To display multipoint-to-point funnel connections, use the following EXEC commands:
| Command | Task |
|---|---|
Display the number of active funnels. | |
Display the status of the multipoint-to-point messages on the specific interfaces. |
Use the show atm status command to display the number of active funnels, point-to-point and point-to-multipoint setup messages. An example of the show atm status command output follows:
Switch# show atm status
NUMBER OF INSTALLED CONNECTIONS: (P2P=Point to Point, P2MP=Point to MultiPoint, MP2P=Multipoint to Point)
Type PVCs SoftPVCs SVCs TVCs PVPs SoftPVPs SVPs Total
P2P 26 0 0 0 2 0 0 28
P2MP 1 0 0 0 0 0 0 1
MP2P 0 0 1 0 0 0 0 1
TOTAL INSTALLED CONNECTIONS = 30
PER-INTERFACE STATUS SUMMARY AT 13:34:48 UTC Thu Jan 29 1998:
Interface IF Admin Auto-Cfg ILMI Addr SSCOP Hello
Name Status Status Status Reg State State State
------------- -------- ------------ -------- ------------ --------- --------
ATM0/0/0 UP up done UpAndNormal Active 2way_in
ATM0/0/1 DOWN down waiting n/a Idle n/a
ATM0/0/2 UP up done UpAndNormal Active 2way_in
ATM0/0/3 UP up done UpAndNormal Active 2way_in
ATM0/0/3.55 UP up waiting WaitDevType Idle n/a
ATM0/0/3.60 UP up waiting WaitDevType Idle n/a
ATM0/0/3.65 UP up waiting WaitDevType Idle n/a
ATM0/1/0 UP up n/a UpAndNormal Active n/a
ATM0/1/1 UP up done UpAndNormal Active n/a
ATM0/1/2 DOWN shutdown waiting n/a Idle n/a
ATM0/1/3 DOWN down waiting n/a Idle n/a
Use the show atm vc cast mp2p command to display the status of the multipoint-to-point messages on the specific interfaces. An example of the show atm vc cast mp2p command output follows:
Switch# show atm vc cast mp2p
Interface VPI VCI Type X-Interface X-VPI X-VCI Encap Status
ATM0/1/0 0 40 SVC ATM0/1/1 0 35 UP
ATM0/1/1 0 36 UP
ATM0/1/1 0 35 SVC ATM0/1/0 0 40 UP
ATM0/1/1 0 36 SVC ATM0/1/0 0 40 UP
Posted: Fri Jun 16 08:27:03 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.