- A through B
- C
- debounce-time rai through dialer rotor
- dialer string through group-range
- interface bri through isdn busy
- isdn call interface through isdn send-alerting
- isdn sending-complete through loopback remote (controller)
- map-class dialer through modem inout
- modem cts-alarm
- peer default ip address through ppp iphc max-header
- ppp iphc max-period through ppp multilink slippage
- ppp pap wait through rotary-group
- script activation through show dial-shelf
- show dial-shelf split through show nbf cache
- show nbf sessions through show tech-support spe
- show tgrm through x25 map ppp
- show tgrm
- show trunk group
- sh ow v template
- shutdown (port)
- shutdown (spe)
- signaling-class cas
- snapshot client
- snapshot server
- source template
- spe
- spe call-record modem
- spe country
- spe download maintenance
- spe log-size
- spe recovery
- start- character
- start-chat
- stop-character
- tdm clock priority
- template
- test modem back-to-back
- test port modem back-to-back
- timeout absolute
- timer
- trunk a ctivate port-threshold
- trunk group (global)
- trunk-group (timeslots)
- tunnel
- virtual-profile aaa
- virtual-profile if-needed
- virtual-profile virtual-template
- vty-async
- vty-async dynamic-routing
- vty-async header-compression
- vty-async ipx ppp-client loopback
- vty-async keepalive
- vty-async mtu
- vty-async ppp authentication
- vty-async ppp use-tacacs
- vty-async virtual-template
- x25 aodi
- x25 map ppp
show tgrm
To display information for debugging purposes about defined trunk groups and interfaces that have been assigned to the trunk groups, use the show tgrm command in EXEC mode.
Syntax Description
Command Modes
Command History
|
|
|
|---|---|
Examples
The following is sample output from the show tgrm command:
Table 1 describes the significant fields shown in the display.
show trunk group
To display information for one or more trunk groups, use the show trunk group command in user EXEC or privileged EXEC mode.
show trunk group [ name [ cic ] [ sort [ ascending | descending ]]
Syntax Description
Command Default
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Examples
The following sample output shows that for trunk group 1, preemption is enabled, with a preemption tone timer of 10 seconds, and the preemption level is flash.
Table 2 describes the significant fields shown in the output. Fields are listed in alphabetical order.
Related Commands
show vtemplate
To display information about all configured virtual templates, use the show vtemplate command in privileged EXEC mode.
Syntax Description
Command Modes
Command History
Examples
The following is sample output from the show vtemplate command:
Table 3 describes the significant fields shown in the example.
Related Commands
shutdown (port)
To disable a port, use the shutdown command in port configuration mode. To change the administrative state of a port from out-of-service to in-service, use the no form of this command.
Syntax Description
Command Default
Command Modes
Port configuration (config-port)
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5350. |
Usage Guidelines
The shutdown command disables a port.
Note
The shutdown command is similar to the modem shutdown MICA technologies modem command.
Examples
The following example disables ports 1 to 18 and then reenables them:
Related Commands
shutdown (spe)
To take a service processing element (SPE) out of service, use the shutdown command in SPE configuration mode. To change the administrative state of this SPE from down to up, use the no form of this command.
Syntax Description
Command Default
Command Modes
SPE configuration (config-spe)
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5350. |
Examples
The following example disables SPE ports 1 to 18 and then reenables them:
Related Commands
signaling-class cas
To define a signaling class with a template formed by directives guiding the Call Service Module (CSM) to process the digit sequence, use the signaling-class cas command in global configuration mode. To remove the signaling class assignment, use the no form of this command.
Syntax Description
The signaling class name, which specifies the template that processes the ANI/DNIS delimiter. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Examples
The following example enables the signaling-class cas command:
signaling-class cas test
profile incoming S<*a<*d<*n
controller T1 1/0/1
cas-custom 1
class test
Related Commands
|
|
|
Defines a template formed by directives guiding the CSM to process the digit sequence for a signaling class. |
snapshot client
To configure a client router for snapshot routing, use the snapshot client command in interface configuration mode. To disable a client router, use the no form of this command.
snapshot client active-time quiet-time [ suppress-statechange-updates ] [ dialer ]
no snapshot client active-time quiet-time [ suppress-statechange-updates ] [ dialer ]
Syntax Description
Command Default
The active-time and quiet-time arguments have no default values.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The value of the active-time argument must be the same for the client and server routers.
To specify that the remote server routers be called by this client router during each active period, use the dialer map snapshot command.
Examples
The following example configures a client router for snapshot routing:
Related Commands
|
|
|
|---|---|
Defines a dialer map for the Cisco snapshot routing protocol on a client router connected to a DDR interface. |
|
Displays snapshot routing parameters associated with an interface. |
|
snapshot server
To configure a server router for snapshot routing, use the snapshot server command in interface configuration mode. To disable a server router, use the no form of this command.
snapshot server active-time [ dialer ]
no snapshot server active-time [ dialer ]
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The value of the active-time argument must be the same for the client and server routers.
Examples
The following example configures a server router for snapshot routing:
Related Commands
|
|
|
|---|---|
Displays snapshot routing parameters associated with an interface. |
|
source template
To attach a configured customer profile template to a particular customer profile, use the source template command in customer profile configuration mode.
Syntax Description
Command Default
Command Modes
Customer profile configuration
Command History
|
|
|
|---|---|
Usage Guidelines
All PPP and peer-default commands are allowed for a particular customer profile template under this grouping.
Examples
The following example shows the creation and configuration of a customer profile template named cisco1-direct and its subsequent assignment to the customer profile cisco1:
Related Commands
|
|
|
|---|---|
Accesses the template configuration mode for configuring a particular customer profile template. |
spe
To enter service processing element (SPE) configuration mode and set the range of SPEs, use the spe command in global configuration mode.
Cisco AS5350 and Cisco AS5400 with the NextPort Dial Feature Card (DFC)
spe { slot | slot / spe } [ slot | slot / spe ]
Cisco AS5800 with the Universal Port Card (UPC)
spe { shelf / slot | shelf / slot / spe } [ shelf / slot | shelf / slot / spe ]
Syntax Description
Command Default
Command Modes
Command History
Usage Guidelines
The spe global configuration command enables the SPE configuration mode. Configure your SPE by specifying a slot and an SPE associated with the slot; or, you can configure a range of SPEs by specifying the first and last SPE in the range.
Examples
The following example shows the spe command being used from global configuration mode to access the SPE configuration mode for the SPE range from 1/2 to 1/4:
When the universal gateway is booted, the spe global configuration command specifies the location from where the firmware image is downloaded to the SPE. If the spe configuration command is used to download the firmware from Flash memory and then subsequently the no version of the exact command is entered, then the spe command downloads the embedded firmware.
Note Use this command when traffic is low because the spe download does not begin until the modems have no active calls.
The
spe command is a configuration command. Save it using the
write memory command; otherwise, the configuration is not saved. If the configuration is not saved, the downloading of the specified firmware does not occur after the next reboot.
The following example shows the spe command being used from global configuration mode to access the SPE configuration mode for the range of SPEs from 1/2 to 1/4 on the Cisco AS5400:
The following example specifies the range for use of the shutdown command:
Related Commands
|
|
|
|---|---|
spe call-record modem
To generate a modem call record at the end of each call, use the spe call-record modem command in global configuration mode. To cancel the request to generate the reports, use the no form of the command.
spe call-record modem { max-userid number | quiet }
no spe call-record modem { max-userid number | quiet }
Syntax Description
Maximum length of the user ID for the modem call record report in number of bytes. The range is from 0 to 100. |
|
Disables logging to console and terminal, but not to syslog. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5350. |
Usage Guidelines
The spe modem-call-record command generates a modem call record at the end of each call.
Note The spe call-record modem command is similar to the modem call-record command.
Examples
The following example displays an SPE call record:
The following is a partial example of traces generated when a call terminates. The logs from the show port modem log command do not change as a result of using the spe call-record modem command.
Related Commands
|
|
|
|---|---|
Activates the logging of a summary of modem events upon the termination of a call. |
spe country
To specify the country while setting the modem card parameters (including country code and encoding), use the spe country command in global configuration mode. To set the country code to the default value, use the no form of this command.
spe country { country-name | e1 - default | t1 - default }
no spe country { country-name | e1 - default | t1 - default }
Syntax Description
Name of the country, See Table 4 for a list of supported country name keywords. |
|
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5350. |
Usage Guidelines
On the Cisco universal gateway, DS0 companding law selection is configured for the entire system rather than on individual voice ports. Set the spe country command to the appropriate country.
If T1 lines are configured, the default is t1-default ; if E1 lines are configured, the default is e1-default.
The Cisco universal gateway must be in an Idle state (no calls are active) for the spe country command to function. All sessions on all modules in all slots must be in the Idle state.
Note The spe country command is similar to the modem country mica and modem country microcom_hdms commands.
Table 4 lists the country names and corresponding companding law.
|
|
|
|
|---|---|---|
Examples
The following example configures the setting of the country code to the default for E1:
The following example configures the setting of the country code to the default for T1:
Related Commands
|
|
|
|---|---|
Configures the modem country code for a bank of MICA technologies modems. |
|
Configures the modem country code for a bank of Microcom modems. |
|
spe download maintenance
To perform download maintenance on service processing elements (SPEs) that are marked for recovery, use the spe download maintenance command in global configuration mode. To disable download maintenance on SPEs, use the no form of the command.
spe download maintenance { time hh:mm | stop-time hh:mm | max-spes number-of-spes | window time-period | expired-window { drop-call | reschedule }}
no spe download maintenance { time hh:mm | stop-time hh:mm | max-spes number-of-spes | window time-period | expired-window { drop-call | reschedule }}
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5350. |
Usage Guidelines
The SPE download maintenance activity takes place when SPEs are marked for recovery. The settings are enabled by default. When you want to change the default settings to a desired setting, use the spe download maintenance command parameters to perform SPE download maintenance activity with the specific changes.
Enter the time hh:mm keyword to set a time to start the SPE download maintenance activity. Then enter the stop-time hh:mm keyword to set a time to stop the download maintenance. Next enter the max-spes number-of-spes keyword to set the number of SPEs for the download maintenance. Then enter the window time-period keyword to set a time period to perform the download maintenance. Finally, enter the expired-window keyword to set actions in the event the SPE download maintenance is not completed in the set window time-period.
The download maintenance activity starts at the set start time and steps through all the SPEs that need recovery and the SPEs that need a firmware upgrade and starts maintenance on the maximum number of set SPEs for maintenance. The system waits for the window delay time for all the ports on the SPE to become inactive before moving the SPE to the Idle state. Immediately after the SPE moves to the Idle state, the system starts to download firmware. If the ports are still in use by the end of window delay time, depending upon the expired-window setting, connections on the SPE ports are shut down and the firmware is downloaded by choosing the drop-call option, or the firmware download is rescheduled to the next download maintenance time by choosing the reschedule option. This process continues until the number of SPEs under maintenance is below the max-spes value, or until the stop-time value (if set), or until all SPEs marked for recovery or upgrade have had their firmware reloaded.
Examples
The following example displays the SPE download maintenance with the different keyword parameters:
Related Commands
|
|
|
spe log-size
To set the size of the port event log, use the spe log-size command in global configuration mode. To restore the default size, use the no version of this command.
Syntax Description
The number of recorded events. Valid values for the number argument range from 0 to 100. The default value is 50 events. |
Command Default
Command Modes
Command History
Examples
The following example sets the size of the event log to 70 events:
Related Commands
|
|
|
|---|---|
Displays the digital data event log with the oldest event first. |
|
Displays the modem port history event log or modem test log. |
spe recovery
To set a service processing element (SPE) port for recovery, use the spe recovery command in global configuration mode. To disable SPE recovery or to restore the default port-threshold value, use the no form of this command.
spe recovery { port-action { disable | recover } | port-threshold number-failures }
no spe recovery { port-action | port-threshold }
Syntax Description
Command Default
There is no default port-action value. SPE recovery is disabled.
The default port-threshold value is 30 failed attempts.
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(11)T and implemented on the Cisco AS5350. |
Usage Guidelines
Failure of an SPE port to connect after repeated tries indicates that a problem exists in the SPE or firmware. An SPE port in this state is recovered by downloading firmware.
When an SPE port fails to connect consecutively for a number of times, as specified by the port-threshold number-failures keyword and argument, the SPE is moved to a state based on the port-action configuration.
If the spe recovery port-action recover command has been configured, when the port-threshold number-failures value is exceeded, the port is temporarily marked as disabled (“d” state) to avoid further incoming calls, and it is then marked for recovery (“r” state). Any SPE that has a port marked for recovery will download firmware when the SPE is idle (when none of the ports on the SPE have active calls).
If the spe recovery port-action disable command has been configured, when the port-threshold number-failures value is exceeded, the port is marked as bad (“BAD” state). An SPE with a port that is marked as bad must be explicitly cleared in order for that port to be used again.
If no port-action is configured, the port will be marked as not in use (“_” state). An SPE with a port marked as not in use will remain unusable until it is explicitly cleared, and the SPE will not accept incoming calls on any of the ports.
SPE recovery can be disabled by issuing the no spe recovery port-action command. If SPE recovery is disabled, the SPE will behave as if no port-action has been configured.
Note Beginning with Cisco IOS Release 12.1(2.3)T1, the modem recovery action for MICA technologies modems on the Cisco AS5800 platforms is done using the spe recovery command rather than the modem recovery command.
Examples
The following example configures the SPE to recover ports that exceed the call failure threshold:
The following example sets a value of 50 for the number of consecutive failed attempts on the port before the port-action keyword is applied:
Related Commands
start-character
To set the flow control start character, use the start-character command in line configuration mode. To remove the character, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command defines the character that signals the start of data transmission when software flow control is in effect. Refer to the “ASCII Character Set and Hex Values” appendix in the Cisco IOS Configuration Fundamentals and Network Management Command Reference for a list of ASCII characters.
Examples
The following example changes the start character to Ctrl-B, which is decimal 2:
line 2
start-character 2
Related Commands
|
|
|
|---|---|
Sets the method of data flow control between the terminal or other serial device and the router. |
|
Changes the flow control start character for the current session. |
start-chat
To specify that a chat script start on a specified line at any point, use the start-chat command in privileged EXEC mode. To stop the chat script, use the no form of this command.
start-chat regexp [[ aux | console | vty ] line-number [ dialer-string ]]
Syntax Description
Command Default
If you do not specify a line number, the current line number is chosen. If the specified line is busy, the script is not executed and an error message appears. If the dialer-string argument is specified, line-number must be entered; it is not optional if you specify a dialer string. This command functions only on physical terminal (TTY) lines. It does not function on virtual terminal (VTY) lines.
Command Modes
Command History
Usage Guidelines
This command provides modem dialing commands for a chat script that you want to apply immediately to a line. If you do not specify a line, the script runs on the current line. If the specified line is already in use, the script is not activated and an error message appears.
The argument regexp is used to specify the name of the modem script that is to be executed. The first script that matches the argument in this command and the dialer map command will be used. For more information about regular expressions, refer to the “Regular Expressions” appendix in this publication.
This command functions only on physical terminal (TTY) lines. It does not function on virtual terminal lines.
Examples
The following example shows how to force a dialout on line 8 using the script named “telebit”:
Related Commands
stop-character
To set the flow control stop character, use the stop-character command in line configuration mode. To remove the character, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command defines the character that signals the end of data transmission when software flow control is in effect. Refer to the “ASCII Character Set and Hex Values” appendix in the Cisco IOS Configuration Fundamentals and Network Management Command Reference for a list of ASCII characters.
Examples
The following example changes the stop character to Ctrl-E, which is decimal 5:
line 3
stop-character 5
Related Commands
|
|
|
|---|---|
Sets the method of data flow control between the terminal or other serial device and the router. |
|
tdm clock priority
To configure the clock source and priority of the clock source used by the time-division multiplexing (TDM) bus on the Cisco AS5350, AS5400, and AS5850 access servers, use the tdm clock priority command in global configuration mode. To return the clock source and priority to the default values, use the no form of this command.
tdm clock priority priority-number { slot / ds1-port | slot / ds3-port : ds1-port | external | freerun }
no tdm clock priority priority-number { slot / ds1-port | slot / ds3-port : ds1-port | external | freerun }
Syntax Description
Command Default
If no clocks are configured, the system uses a default, primary clock. An external clock is never selected by default; it must be explicitly configured.
Command Modes
Command History
|
|
|
|---|---|
This command was integrated into Cisco IOS Release 12.2(33)SRA. |
Usage Guidelines
The TDM bus can receive an input clock from one of three sources on the gateway:
- CT1, CE1, and CT3 trunk cards
- An external T1/E1 clock source feed directly through the Building Integrated Timing Supply (BITS) interface port on the motherboard
- Free-running clock providing clock from an oscillator
Note BITS is a single building master timing supply. BITS generally supplies DS1- and DS0-level timing throughout an office. BITS is the clocks that provide and distribute timing to a wireline network’s lower levels.
The TDM bus can be synchronized with any trunk cards. On the CT1/CE1 trunk card, each port receives the clock from the T1/E1 line. The CT3 trunk card uses an M13 multiplexer to receive the DS1 clock. Each port on each trunk-card slot has a default clock priority. Also, clock priority is configurable through the tdm clock priority command.
The TDM bus can be synchronized with an external clock source that can be used as an additional network reference. If no clocks are configured, the system uses a primary clock through a software-controlled default algorithm. If you want the external T1/E1 clock (from the BITS interface) as the primary clock source, you must configure it using the external keyword with the tdm clock priority command; the external clock is never selected by default.
The BITS interface requires a T1 line composite clock reference set at 1.544 MHz and an E1 line composite clock reference set at 2.048 MHz.
If there is no good clocking source from a trunk card or an external clock source, then select the free-running clock from the internal oscillator using the freerun keyword with the tdm clock priority command.
Examples
In the following example, BITS clock is set at priority 1:
In the following example, a trunk clock from a CT1 trunk card is set at priority 2 and uses slot 4 and DS1 port (controller) 6:
In the following example, a trunk clock from a CT3 trunk card is set at priority 2 and uses slot 1, DS3 port 0, and DS1 port 19:
In the following example, free-running clock is set at priority 3:
Related Commands
|
|
|
|---|---|
Configures the clock source and priority of the clock source used by the TDM bus on the dial shelf of the Cisco AS5800. |
|
template
To access the template configuration mode for configuring a particular customer profile template, use the template command in global configuration mode. To delete the template of the specified name, use the no form of this command.
template name [ default | exit | multilink | no | peer | ppp ]
no template name [ default | exit | multilink | no | peer | ppp ]
Syntax Description
(Optional) Accesses peer parameters for point-to-point interfaces. |
|
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
All PPP and peer-default commands are enabled for a customer profile template under this grouping.
Examples
The following example shows the creation and configuration of a customer profile template named “cisco1-direct” and its subsequent assignment to the customer profile “cisco1”:
Related Commands
|
|
|
|---|---|
Attaches a configured customer profile template to a customer profile. |
test modem back-to-back
To diagnose an integrated modem that may not be functioning properly, use the test modem back-to-back command in EXEC mode.
test modem back-to-back first-slot / port second-slot / port
Syntax Description
Slot and modem number of the first test modem. You must include the slash mark |
|
Slot and modem number of the second test modem. You must include the slash mark |
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to perform back-to-back testing of two modems. You might need to enable this command on several different combinations of modems to determine which one is not functioning properly.
Examples
The following example performs a back-to-back modem test between modem 2/0 and modem 2/1 and removes modem 2/1 (which is associated with TTY line 26) from all dial-in and dial-out services:
Related Commands
test port modem back-to-back
To test two specified ports back-to-back and transfer a specified amount of data between the ports, use the test port modem back-to-back command in EXEC mode.
Cisco AS5350 and Cisco AS5400 with the NextPort Dial Feature Card (DFC)
test port modem back-to-back slot / port
Cisco AS5800 with the Universal Port Card (UPC)
test port modem back-to-back shelf / slot / port
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
The test modem back-to-back form of this command was introduced. |
|
This command was integrated into Cisco IOS Release 12.2(11)T and support was added for the Cisco AS5350. |
Usage Guidelines
The test port modem back-to-back command should be performed on different combinations to determine a good port.
Note The test port modem back-to-back command is similar to the test modem back-to-back MICA technologies modem command.
Examples
The following example displays a back-to-back test:
Related Commands
timeout absolute
To specify a timeout period that controls the duration for which a session can be connected before it is terminated, use the timeout absolute command in interface configuration mode. To remove the session timeout period, use the no form of this command.
timeout absolute minutes [ seconds ]
Syntax Description
(Optional) Session lifetime, in seconds. The range is 0 to 59. |
Command Default
Command Modes
Interface configuration (config-if)
Command History
|
|
|
|---|---|
Examples
The following example shows how to impose a 15-minute (900-second) idle timeout and a 12-hour (720-minute) absolute timeout for session connections:
Related Commands
|
|
|
|---|---|
timer
To set the Redundant Link Manager (RLM) timer, use the timer command in RLM configuration mode. The associated options can overwrite the default setting of timeout values. To disable this function, use the no form of this command.
timer { force-down | keepalive | minimum-up | open-wait | recovery | retransmit | switch-link } seconds
no timer { force-down | keepalive | minimum-up | open-wait | recovery | retransmit | switch-link } seconds
Syntax Description
Defaults
Command Modes
Command History
|
|
|
|---|---|
Examples
The following example configures a ten second retransmission timer for unacknowledged control packets:
Related Commands
trunk activate port-threshold
To specify the percentage of available port resources required to enable a trunk card transmitter, use the trunk activate port-threshold command in global configuration mode. To restore the default value, use the no form of this command.
trunk activate port-threshold resource-percentage
Syntax Description
Decimal integer from 0 through 100 that indicates the percentage of universal port Dial Feature Card (DFC) resources required before a trunk line is enabled. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M. |
Usage Guidelines
Use the trunk activate port-threshold command if you have a CT3 DFC and one or more universal port DFCs on the same platform and calls are dropped at system startup. This command enables the universal port modules to initialize before calls are routed to the platform. If the universal port modules do not initialize, the platform is identified as unavailable and calls are dropped.
Examples
The following example shows how to set the port threshold for the trunk card to 70 percent:
trunk group (global)
To define or modify the definition of a trunk group and to enter trunk group configuration mode, use the trunk group command in global configuration mode. To delete the trunk group, use the no form of this command.
Syntax Description
Name of the trunk group. Valid names contain a maximum of 63 alphanumeric characters. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use the trunk group command to assign a number or a name to a set of trunk characteristics. The set of characteristics, or profile, is assigned to specific trunks as part of the usual trunk configuration steps.
The trunk group command initiates the profile definition and switches from global configuration to trunk group configuration mode. Additional commands are available to construct the characteristics of the profile.
Up to 1000 trunk groups can be configured on the gateway provided that the gateway has sufficient memory to store the profiles. If you see the message “Trunk group name could not be added as the threshold has been reached”, enter the debug tgrm command and check the number of trunk groups or check for insufficient memory.
To associate a trunk group with an interface, use the trunk-group (interface) command. A trunk group that was created using the trunk group (global) command can be associated with an interface. However, a trunk group need not be defined globally before being associated with an interface. If a trunk group has not been defined globally, it will be created by issuing the trunk-group (interface) command.
Examples
The following example creates trunk group 5 and configures the trunk group profile:
The following example creates a trunk group named “mytrunk” and configures the trunk group profile:
Related Commands
trunk-group (timeslots)
To direct an outbound synchronous or asynchronous call initiated by dial-on-demand routing (DDR) to use specific B or digital service 0 (DS0) channels of an ISDN circuit on Cisco AS5800 series access servers, use the trunk - group command in CAS custom configuration, controller configuration, or interface configuration mode. To delete DS0s from the trunk group, use the no form of this command.
trunk-group name [ timeslots timeslot-list [ preference preference - number ] ]
no trunk-group name [ timeslots timeslot-list [ preference preference - number ] ]
Syntax Description
Command Default
All DS0s in the signaling circuit are assigned to the trunk group.
Command Modes
CAS custom configuration
Controller configuration
Interface configuration
Command History
|
|
|
|---|---|
Usage Guidelines
Dial-out trunk groups can include individual DS0s from more than one DS1.
Two types of DS0 resources can be pooled: DS0s from common channel signaling circuits (CCS) such as PRI, Non-Facility Associated Signaling (NFAS), Signaling System 7 (SS7), and so on, and DS0s from channel-associated signaling (CAS) circuits.
The large-scale dial-out architecture is an integral part of dial-out trunk groups. The large-scale dial-out architecture is based on dialer rotary groups where physical interfaces are statically bound to dialer interfaces, meaning that the physical interfaces inherit the configuration parameters of the dialer interface. A call placed using a specific dialer interface (dialer rotary) can be done only through a rotary member, and this same rule applies to DDR over DS0 trunk groups.
As an example, a trunk group can have DS0s from three different physical interfaces that are also rotary members of a dialer interface. When an outgoing call is placed through the dialer interface, the Trunk Group Resource Manager (TGRM) provides a DS0 that belongs to a physical interface. The call will fail, however, if the physical interface is not a rotary member of a dialer interface. See the “Examples” section for more about the limitations large-scale dial-out places on selecting DS0s from physical interfaces.
The large-scale dial-out framework is used to place outgoing calls over a synchronous or asynchronous line. The framework also enables provisioning of dial-out configurations on an authentication, authorization, and accounting (AAA) server. A trunk group label can be configured as part of a dialer string command, or the large-scale dial-out framework can be used to download the trunk group identifier along with the dialer string.
Examples
The following examples show how to configure DS0 trunk groups on a CAS:
The following example shows how to configure NFAS/SS7 circuits. With these circuits, signaling can take place over a circuit different than the one over which the data is being transported. The DS0 dial-out trunk group configuration is done in controller configuration mode, because the trunk group is configured under the NFAS primary serial interface, all the NFAS group interface member DS0s are added into the trunk group. The NFAS primary serial interface will not have the timeslots keyword enabled under its configuration mode. The timeslots option is not available in the serial interface configuration mode because a serial interface may represent an NFAS serial interface. Remember that trunk group configurations under the NFAS member controllers and the respective serial interface (D channel) are mutually exclusive.
Configuring and Associating DS0 Trunk Groups for DDR
The following examples show how to configure the dialer interface and apply a static dial-out trunk configuration on the NAS.
The following example configures a static trunk group dialer association on the NAS:
Router(config-if)# dialer string 5550112 trunkgroup trunkgroup1
The following example configures a static dial-out trunk group on the NAS:
The following example configures a dial-out trunk group Cisco AVPair:
Dial-Out Trunk Groups in Dialer Rotary Configurations
In the following examples, dial-out trunk groups 15 and 16 have DS0s from PRI interfaces 0:23 and 6:23. These interfaces are also rotary members of dialer interface 0, and are configured correctly for dial-out trunk groups and outbound calling.
The following example configures the AAA server:
The following example configures a static dial-out trunk group on the NAS:
In the following example, trunk group 15 has member DS0s from PRI interfaces 0:23, 6:23, and 7:23. When an outgoing call is placed through interface dialer 0, TGRM could return a DS0 that belongs to physical interfaces serial 6:23 or serial 7:23, which are not part of the same rotary group as serial 0:23. Because these physical serial interfaces are not rotary members of interface dialer 0, the call will fail.
The following example configures the AAA server incorrectly:
The following example configures the static dial-out trunk group on the NAS incorrectly:
Related Commands
tunnel
To set up a network layer connection to a router, use the tunnel command in EXEC mode.
Syntax Description
Name or IP address of a specific host on a network that can be reached by the router. |
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
If you are a mobile user, it is often impractical to dial in to your “home” router from a remote site. The asynchronous mobility feature allows you to dial in to different routers elsewhere on the internetwork while experiencing the same server environment that you would if you were connecting directly to your home router.
This asynchronous host mobility is accomplished by packet tunneling, a technique by which raw data from the dial-in user is encapsulated and transported directly to the host site where your home router performs the actual protocol processing.
You enable asynchronous mobility by entering the tunnel command to set up a network layer connection to a specified host. From a router other than a Cisco router, however, you need to use the Telnet protocol.
After a connection is established, you receive an authentication dialog or prompt from your home router and can proceed as if you are connected directly to it. When communications are complete, the network connection can be closed and terminated from either end of the connection.
Examples
The following example establishes a network layer connection with an IBM host named mktg:
virtual-profile aaa
Note Effective with Cisco IOS Release 12.2, the virtual-profile aaa command is not available in Cisco IOS software.
To enable virtual profiles by authentication, authorization, and accounting (AAA) configuration, use the virtual-profile aaa command in global configuration mode. To disable virtual profiles, use the no form of this command.
Syntax Description
Defaults
Command Modes
Command History
Usage Guidelines
The effect of this command for any specific user depends on the router being configured for AAA and the AAA server being configured for that user’s specific configuration information.
In releases later than Cisco IOS Release 12.2, the router automatically creates virtual profiles when AAA attributes require a profile.
Examples
The following example configures virtual profiles by AAA configuration only:
Related Commands
|
|
|
|---|---|
Enables AAA authentication to determine if a user can access the privileged command level. |
|
virtual-profile if-needed
To specify that a virtual profile be used to create a virtual access interface only if the inbound connection requires a virtual access interface, use the virtual-profile if-needed command in global configuration mode. To create virtual access interfaces for every inbound connection, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command is intended to prevent the creating of virtual-access interfaces for inbound calls on physical interfaces that do not require virtual-access interfaces.
This command is compatible with local, RADIUS, and TACACS+ AAA.
Examples
The following example enables selective virtual-access interface creation:
Related Commands
|
|
|
|---|---|
Creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces. |
|
virtual-profile virtual-template
To enable virtual profiles by virtual interface template, use the virtual-profile virtual-template command in global configuration mode. To disable this function, use the no form of this command.
virtual-profile virtual-template number
no virtual-profile virtual-template number
Syntax Description
Number of the virtual template to apply, ranging from 1 to 30. |
Command Default
Disabled. No virtual template is defined, and no default virtual template number is used.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
When virtual profiles are configured by virtual templates only, any interface-specific configuration information that is downloaded from the AAA server is ignored in configuring the virtual access interface for a user.
The interface virtual-template command defines a virtual template to be used for virtual profiles. Because several virtual templates might be defined for different purposes on the router (such as MLP, PPP over ATM, and virtual profiles), it is important to be clear about the virtual template number to use in each case.
Examples
The following example configures virtual profiles by virtual templates only. The number 2 was chosen because virtual template 1 was previously defined for use by Multilink PPP.
Related Commands
|
|
|
|---|---|
Creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces. |
vty-async
To configure all virtual terminal lines on a router to support asynchronous protocol features, use the vty-async command in global configuration mode. To disable asynchronous protocol features on virtual terminal lines, use the no form of this command.
Syntax Description
Command Default
By default, asynchronous protocol features are not enabled on virtual terminal lines.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The vty-async command extends asynchronous protocol features from physical asynchronous interfaces to virtual terminal lines. Normally, SLIP and PPP can function only on asynchronous interfaces, not on virtual terminal lines. However, extending asynchronous functionality to virtual terminal lines permits you to run SLIP and PPP on these virtual asynchronous interfaces. One practical benefit is the ability to tunnel SLIP and PPP over X.25 PAD, thus extending remote node capability into the X.25 area. You can also tunnel SLIP and PPP over Telnet or LAT on virtual terminal lines. To tunnel SLIP and PPP over X.25, LAT, or Telnet, you use the protocol translation feature in the Cisco IOS software.
To tunnel SLIP or PPP inside X.25, LAT, or Telnet, you can use two-step protocol translation or one-step protocol translation, as follows:
- If you are tunneling SLIP or PPP using the two-step method, you need to first enter the vty-async command. Next, you perform two-step translation.
- If you are tunneling SLIP or PPP using the one-step method, you do not need to enter the vty-async command. You need to issue only the translate command with the SLIP or PPP keywords, because the translate command automatically enables asynchronous protocol features on virtual terminal lines.
Examples
The following example enables asynchronous protocol features on virtual terminal lines:
Related Commands
|
|
|
|---|---|
Enables asynchronous protocol features on virtual terminal lines. |
vty-async dynamic-routing
To enable dynamic routing on all virtual asynchronous interfaces, use the vty-async dynamic-routing command in global configuration mode. To disable asynchronous protocol features on virtual terminal lines, and therefore disable routing on virtual terminal lines, use the no form of this command.
Syntax Description
Command Default
Dynamic routing is not enabled on virtual asynchronous interfaces.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This feature enables IP routing on virtual asynchronous interfaces. When you issue this command and a user later makes a connection to another host using SLIP or PPP, the user must specify /routing on the SLIP or PPP command line.
If you had not previously entered the vty-async command, the vty-async dynamic-routin g command creates virtual asynchronous interfaces, and then enables dynamic routing on them.
Examples
The following example enables dynamic routing on virtual asynchronous interfaces:
Related Commands
|
|
|
|---|---|
Enables manually configured routing on an asynchronous interface. |
|
Enables manually configured routing on an asynchronous interface. |
vty-async header-compression
To compress the headers of all TCP packets on virtual asynchronous interfaces, use the vty-async header-compression command in global configuration mode. To disable virtual asynchronous interfaces and header compression, use the no form of this command.
vty-async header-compression [ passive ]
no vty-async header-compression
Syntax Description
Defaults
Header compression is not enabled on virtual asynchronous interfaces.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This feature compresses the headers on TCP/IP packets on virtual asynchronous connections to reduce the size of the packets and to increase performance.This feature only compresses the TCP header, so it has no effect on UDP packets or other protocol headers. The TCP header compression technique, described fully in RFC 1144, is supported on virtual asynchronous interfaces using SLIP or PPP encapsulation. You must enable compression on both ends of a connection.
Examples
The following example compresses outgoing TCP packets on virtual asynchronous interfaces only if incoming TCP packets are compressed:
Related Commands
|
|
|
|---|---|
Enables manually configured routing on an asynchronous interface. |
vty-async ipx ppp-client loopback
To enable IPX-PPP on virtual terminal lines, use the vty-async ipx ppp-client loopback command in global configuration mode. To disable IPX-PPP sessions on virtual terminal lines, use the no form of this command.
vty-async ipx ppp-client loopback number
no vty-async ipx ppp-client loopback
Syntax Description
Number of the loopback interface configured for IPX to which the virtual terminal lines are assigned. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command enables users to log into the router from a device running a virtual terminal protocol, then issue the PPP command at the EXEC prompt to connect to a remote device.
A loopback interface must already have been defined and an IPX network number must have been assigned to the loopback interface before the vty-async ipx ppp-client loopback command will permit IPX–PPP on virtual terminal lines.
Examples
The following example enables IPX over PPP on virtual terminal lines:
Related Commands
|
|
|
|---|---|
Enables IPX routing on a particular interface and optionally selects the type of encapsulation (framing). |
vty-async keepalive
To change the frequency of keepalive packets on all virtual asynchronous interfaces, use the vty-async keepalive command in global configuration mode. To disable asynchronous protocol features on virtual terminal lines, use the no vty-async keepalive command. To disable keepalive packets on virtual terminal lines, use the vty-async keepalive 0 command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to change the frequency of keepalive updates on virtual asynchronous interfaces, or to disable keepalive updates. To determine if keepalive is enabled on an interface, use the show running-config command. If the router has not received a keepalive packet after three update intervals have passed, the connection is considered down.
Examples
The following example sets the keepalive interval to 30 seconds:
The following example sets the keepalive interval to 0 (off):
Related Commands
|
|
|
|---|---|
Displays the contents of the currently running configuration file. |
vty-async mtu
To set the maximum transmission unit (MTU) size on virtual asynchronous interfaces, use the vty-async mtu command in global configuration mode. To disable asynchronous protocol features on virtual terminal lines, use the no form of this command.
Syntax Description
MTU size of IP packets that the virtual asynchronous interface can support. The default MTU is 1500 bytes. Valid values for the MTU range from 64 bytes to 1000000 bytes. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to modify the MTU for packets on a virtual asynchronous interfaces. You might want to change to a smaller MTU size for IP packets transmitted on a virtual terminal line configured for asynchronous functions for any of the following reasons:
- The SLIP or PPP application at the other end only supports packets up to a certain size.
- You want to ensure a shorter delay by using smaller packets.
- The host echoing takes longer than 0.2 seconds.
Do not change the MTU size unless the SLIP or PPP implementation running on the host at the other end of the virtual asynchronous interface supports reassembly of IP fragments. Because each fragment occupies a spot in the output queue, it might also be necessary to increase the size of the SLIP or PPP hold queue if your MTU size is such that you might have a high amount of packet fragments in the output queue.
Examples
The following example sets the MTU for IP packets to 256 bytes:
Related Commands
|
|
|
|---|---|
vty-async ppp authentication
To enable PPP authentication on virtual asynchronous interfaces, use the vty-async ppp authentication command in global configuration mode. To disable PPP authentication, use the no form of this command.
vty-async ppp authentication { chap | pap }
no vty-async ppp authentication { chap | pap }
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command configures the virtual asynchronous interface to either authenticate CHAP or PAP while running PPP. After you have enabled CHAP or PAP, the local router requires a password from remote devices. If the remote device does not support CHAP or PAP, no traffic will be passed to that device.
Examples
The following example enables CHAP authentication for PPP sessions on virtual asynchronous interfaces:
Related Commands
|
|
|
|---|---|
Configures all virtual terminal lines on a router to support asynchronous protocol features. |
|
Enables TACACS authentication for PPP on virtual asynchronous interfaces. |
vty-async ppp use-tacacs
To enable TACACS authentication for PPP on virtual asynchronous interfaces, use the vty-async ppp use-tacacs command in global configuration mode. To disable TACACS authentication on virtual asynchronous interfaces, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
This command requires the extended TACACS server.
After you have enabled TACACS, the local router requires a password from remote devices.
This feature is useful when integrating TACACS with other authentication systems that require a clear-text version of a user’s password. Such systems include one-time password systems and token card systems.
If the username and password are contained in the CHAP password, the CHAP secret is not used by the router. Because most PPP clients require that a secret be specified, you can use any arbitrary string; Cisco IOS software ignores it.
You cannot enable TACACS authentication for SLIP on asynchronous or virtual asynchronous interfaces.
Examples
The example enables TACACS authentication for PPP sessions:
Related Commands
|
|
|
|---|---|
Enables PPP authentication on virtual asynchronous interfaces. |
vty-async virtual-template
To configure virtual terminal lines to support asynchronous protocol functions based on the definition of a virtual interface template, use the vty-async virtual-template command in global configuration mode. To disable virtual interface templates for asynchronous functions on virtual terminal lines, use the no form of this command.
vty-async virtual-template number
Syntax Description
Command Default
Asynchronous protocol features are not enabled by default on virtual terminal lines.
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
The vty-async virtual-template command enables you to support tunneling of SLIP or PPP across X.25, TCP, or LAT networks by using two-step protocol translation.
Before issuing the vty-async virtual-template command, create and configure a virtual interface template by using the interface virtual-template command. Configure this virtual interface as a regular asynchronous serial interface. That is, assign the virtual interface template the IP address of the Ethernet interface, and configure addressing, just as on an asynchronous interface. You can also enter commands in interface configuration mode that compress TCP headers or configure CHAP authentication for PPP.
After creating a virtual interface template, apply it by issuing the vty-async virtual-template command. When a user dials in through a virtual terminal line, the router creates a virtual access interface, which is a temporary interface that supports the asynchronous protocol configuration specified in the virtual interface template. This virtual access interface is created dynamically, and is freed up as soon as the connection drops.
Before virtual templates were implemented, you could use the vty-async command to extend asynchronous protocol functions from physical asynchronous interfaces to virtual terminal lines. However, in doing so, you created a virtual asynchronous interface, rather than the virtual access interface. The difference is that the virtual asynchronous interfaces are allocated permanently, whereas the virtual access interfaces are created dynamically when a user calls in and closed down when the connection drops.
You can have up to 25 virtual templates interfaces, but you can apply only one template to vty-async interfaces on a router. There can be up to 300 virtual access interfaces on a router.
Examples
The following example enables asynchronous protocol features on virtual terminal lines:
Related Commands
x25 aodi
To enable the Always On/Dynamic ISDN (AO/DI) client on an interface, use the x25 aodi command in interface configuration mode. To remove AO/DI client functionality, use the no form of this command.
Syntax Description
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use this command to enable the AO/DI client on an interface.
Examples
The following example enables the AO/DI client on the interface running X.25, using the x25 aodi command:
Note Configuring the BRI interface with the isdn x25 dchannel command creates a configurable interface (bri 0:0) for other necessary X.25 commands. Refer to the description for this command earlier in this publication for additional information about this command.
Related Commands
|
|
|
|---|---|
Creates a configurable interface for X.25 traffic over the ISDN D channel. |
x25 map ppp
To enable a PPP session over the X.25 protocol, use the x25 map ppp command in interface configuration mode. To remove a prior mapping, use the no form of this command.
x25 map ppp x121-address interface cloning-interface [ no-outgoing ]
no x25 map ppp x121-address interface cloning-interface [ no-outgoing ]
Syntax Description
(Optional) Ensures that the X.25 map does not originate calls. |
Command Default
Command Modes
Command History
|
|
|
|---|---|
Usage Guidelines
Use x25 map ppp command to allow a PPP session to run over X.25.
The interface keyword refers to the interface that will be used to clone the configuration.
Note For the x25 map command used in standard X.25 implementations, refer to the Cisco IOS Wide-Area Networking Command Reference publication.
Examples
The following example enables the AO/DI client on the interface and configures the D channel (BRI interface 0:0) with the x25 map statement in order to allow PPP sessions over X.25 encapsulation with the configured AO/DI server:
x25 aodi
x25 htc 4
x25 win 3
x25 wout 3
x25 map ppp 16193368209 interface dialer 1
The following example enables the AO/DI server to receive calls from the AO/DI client and configures the D channel (BRI0:0) with the x25 map statement which allows PPP sessions over X.25 encapsulation with the configured AO/DI client. The no-outgoing option is used with the x.25 map command since the AO/DI server is receiving, versus initiating, calls.
x25 address 16193368209
x25 htc 4
x25 win 3
x25 wout 3
x25 map ppp 16193368208 interface dialer 1 no-outgoing
Note Configuring the BRI interface with the isdn x25 dchannel command creates a configurable interface (bri 0:0).
Related Commands
|
|
|
|---|---|
Creates a configurable interface for X.25 traffic over the ISDN D channel. |
Feedback