Table Of Contents
multilink
multilink bundle-name
multilink-group
multilink max-fragments
multilink virtual-template
name (dial peer cor custom)
netbios nbf
network-clock-priority
number
peer default ip address
peer match aaa-pools
permission (dial peer voice)
pool-member
pool-range
port (global)
port modem autotest
ppp
ppp accm
ppp bap call
ppp bap callback
ppp bap drop
ppp bap link types
ppp bap max
ppp bap monitor load
ppp bap number
ppp bap timeout
ppp bridge appletalk
ppp bridge ip
ppp bridge ipx
ppp callback (DDR)
ppp callback (PPP client)
ppp caller name
ppp dnis
ppp encrypt mppe
ppp ipcp
ppp iphc max-header
ppp iphc max-period
ppp iphc max-time
ppp lcp delay
ppp lcp fast-start
ppp link reorders
ppp loopback ignore
ppp max-bad-auth
ppp mru match
ppp ms-chap refuse
ppp ms-chap-v2 refuse
ppp mtu adaptive
ppp multilink
ppp multilink endpoint
ppp multilink fragment delay
ppp multilink fragment disable
ppp multilink fragmentation
ppp multilink fragment maximum
ppp multilink group
ppp multilink idle-link
ppp multilink interleave
ppp multilink links maximum
ppp multilink links minimum
ppp multilink load-threshold
ppp multilink slippage
ppp quality
ppp reliable-link
ppp timeout authentication
ppp timeout idle
ppp timeout multilink link add
ppp timeout multilink link remove
ppp timeout multilink lost-fragment
ppp timeout ncp
ppp timeout retry
pptp flow-control receive-window
pptp flow-control static-rtt
pptp tunnel echo
multilink
To limit the total number multilink PPP (MLP) sessions for all virtual private dialup network (VPDN) multilink users, enter the multilink command in VPDN group configuration mode. To remove the MLP session limit, enter the no form of this command.
multilink {bundle bundles | link links}
no multilink {bundle bundles | link links}
Syntax Description
bundle bundles
|
Configures the number of MLP bundles supported for a VPDN group. In general, each user requires one bundle. Valid values for the bundles argument range from 0 to 32,767.
|
link links
|
Configures the number of sessions supported for each bundle. Valid values for the links argument range from 0 to 32,767.
|
Command Default
No MLP session limit is set.
Command Modes
VPDN group configuration
Command History
Release
|
Modification
|
12.0(4)XI
|
This command was introduced.
|
12.0(5)T
|
This command was integrated into Cisco IOS Release 12.0(5)T.
|
Usage Guidelines
Use the multilink VPDN group configuration command to limit the total number of sessions for all MLP users. Each user requires one bundle, regardless if the user is a remote modem client or an ISDN client.
One modem client using one B channel requires one link. One ISDN BRI node may require up to two links for one BRI line connection. The second B channel of an ISDN BRI node comes up when the maximum threshold is exceeded.
Examples
The following example configures a VPDN group called group1 to initiate Layer 2 Tunnel Protocol (L2TP) tunnels to the tunnel server at IP address 10.2.2.2. Ten MLP bundles are configured for users that dial in to the domain cisco.com. Each bundle is configured to support a maximum of 5 links, limiting the total number of MLP sessions to 50.
Router(config)# vpdn-group group1
Router(config-vpdn)# request-dialin
Router(config-vpdn-req-in)# protocol l2tp
Router(config-vpdn-req-in)# domain cisco.com
Router(config-vpdn-req-in)# exit
Router(config-vpdn)# initiate-to ip 10.2.2.2
Router(config-vpdn)# multilink bundle 10
Router(config-vpdn)# multilink link 5
Related Commands
Command
|
Description
|
request-dialin
|
Creates a request dial-in VPDN subgroup that configures a NAS to request the establishment of a dial-in tunnel to a tunnel server, and enters request dial-in VPDN subgroup configuration mode.
|
vpdn-group
|
Creates a VPDN group and enters VPDN group configuration mode.
|
multilink bundle-name
To select a method for naming multilink bundles, use the multilink bundle-name command in global configuration mode. To remove the selection method, use the no form of this command.
multilink bundle-name {authenticated | endpoint | both}
no multilink bundle-name {authenticated | endpoint | both}
Syntax Description
authenticated
|
Authenticated name of the peer. This is the default.
|
endpoint
|
Endpoint discriminator of the peer.
|
both
|
Authenticated name and endpoint discriminator of the peer.
|
Defaults
Authenticated name of the peer.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
Usage Guidelines
The authenticated keyword defines the selection criteria for the bundle name as the authenticated name, the endpoint discriminator if the link is not authenticated, or the caller ID if neither an authenticated name nor an endpoint is supplied.
The endpoint keyword defines the selection criteria for the bundle name as the endpoint discriminator, the authenticated name if no endpoint is supplied, or the caller ID if neither an authenticated name nor an endpoint is supplied.
The both keyword defines the selection criteria for the bundle name as an authenticated name-endpoint discriminator pair, the authenticated name if no endpoint is supplied, the endpoint discriminator if the link is not authenticated, or the caller ID if neither an authenticated name nor an endpoint is supplied.
Examples
The following example sets the selection criteria for the multilink bundle name as the endpoint discriminator:
multilink bundle-name endpoint
multilink-group
The multilink-group command is replaced by the ppp multilink group command. See the description of the ppp multilink group command for more information.
Note
The command is still recognized and accepted by the Cisco IOS software. The show running-config and write memory commands will display and generate the original command in Cisco IOS Release 12.2.
multilink max-fragments
The multilink max-fragments command is replaced by the ppp multilink fragment maximum command. See the description of the ppp multilink fragment maximum command for more information.
multilink virtual-template
To specify a virtual template from which the specified Multilink PPP (MLP) bundle interface can clone its interface parameters, use the multilink virtual-template command in global configuration mode. To remove the defined virtual template, use the no form of the command.
multilink virtual-template number
no multilink virtual-template number
Syntax Description
number
|
Number of virtual templates. An integer in the range from 1 to the largest number of virtual templates the software image supports (typically 25).
|
Defaults
No template number is defined.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
Configuring a specific IP address in a virtual template can result in the establishment of erroneous routes and the loss of IP packets.
Examples
The following example specifies an MLP virtual template to be used and then defines the template to be applied to an MLP bundle interface:
multilink virtual-template 1
interface virtual-template 1
Related Commands
Command
|
Description
|
interface virtual-template
|
Creates a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces.
|
name (dial peer cor custom)
To specify the name for a custom class of restrictions (COR), use the name command in dial peer COR custom configuration mode. To remove a specified COR, use the no form of this command.
name class-name
no name class-name
Syntax Description
class-name
|
Name that describes the specific COR.
|
Defaults
No default behavior or values.
Command Modes
Dial peer COR custom configuration
Command History
Release
|
Modification
|
12.1(3)T
|
This command was introduced.
|
Usage Guidelines
The dial-peer cor custom and name commands define the names of capabilities on which to apply COR operation. Examples of names might include any of the following: call1900, call527, call9, or call 911. You must define the capabilities before you specify the COR rules.
You can define a maximum of 64 COR names.
Examples
The following example defines three COR names:
Related Commands
Command
|
Description
|
dial-peer cor custom
|
Specifies that named CORs apply to dial peers.
|
netbios nbf
To enable the NetBIOS Frames Protocol (NBF) on an interface, use the netbios nbf command in interface configuration mode. To disable NetBIOS Frames Protocol support on an interface, use the no form of this command.
netbios nbf
no netbios nbf
Syntax Description
This command has no arguments or keywords.
Defaults
Command is disabled.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following example enables NBF on asynchronous interface 1 (connected to remote access client using a NetBEUI application) and Ethernet interface 0 (connected to the remote router):
Related Commands
Command
|
Description
|
netbios name-cache
|
Defines a static NetBIOS name cache entry, tying the server with the name netbios-name to the mac-address, and specifying that the server is accessible either locally through the interface-name specified, or remotely through the ring-group group-number specified.
|
show nbf sessions
|
Displays NetBEUI connection information.
|
show netbios cache
|
Displays a list of NetBIOS cache entries.
|
network-clock-priority
To specify the clock-recovery priority for the BRI voice ports in a BRI voice module (BVM), use the network-clock-priority command in interface configuration mode. To restore the default (low) clock-recovery priority, use the no form of this command.
network-clock-priority {low | high}
no network-clock-priority {low | high}
Syntax Description
low
|
The BRI port is second priority to recover clock.
|
high
|
The BRI port is first priority to recover clock.
|
Defaults
Each BRI voice port has low clock-recovery priority. The BRI VIC port provides clocking (high).
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(3)XG
|
This command was introduced on the Cisco MC3810 concentrator.
|
12.1(3)XI
|
This command was implemented on the Cisco 2600 series and Cisco 3600 series.
|
Usage Guidelines
Because the BRI VIC can support both NT and TE ports, this command allows a "local loop" to be configured for testing. By default the TE port on the BRI VIC receives the clock source to drive the whole BRI (network-clock-priority high). Setting the clock priority to low allows the connected port to provide clocking.
This command becomes effective only when the BVM is the clock source for the Cisco MC3810, which can happen in one of three ways:
•
When the BVM is specified as the first-priority network clock source through the network-clock-select command.
•
When the BVM is specified as a lower-priority network clock source, and a higher-priority network clock source is lost.
•
When the BVM is the only network clock source.
The BRI voice port supplying clock operates as a line source; if there are other BRI voice ports configured as TE, they operate in loop-timed mode.
Regardless of the network-clock-priority setting, the first TE-configured BRI voice port that becomes active is automatically chosen to supply clock. The clock source does not change if another BRI voice port configured for network-clock-priority high becomes active.
If the chosen clocking port becomes inactive, the system searches for clock on the active TE-configured ports in the following order:
1.
Ports configured as network-clock-priority high in order from lowest (1) to highest (4).
2.
Ports configured as network-clock-priority low in order from lowest (1) to highest (4).
If the originally chosen port then reactivates, it resumes its role as clock source regardless of its network-clock-priority setting.
If you enter either the no network-clock-priority low or the no network-clock-priority high command, the network clock priority defaults to low.
Examples
The following example configures BRI voice port 1 as a first priority clock source:
network-clock-priority high
Related Commands
Command
|
Description
|
network-clock-select
|
Specifies selection priority for the clock sources.
|
number
To add a Calling Line Identification (CLID) or Dialed Number Identification Service (DNIS) number to a dialer group, use the number command in CLID group configuration or DNIS group configuration mode followed by the specifying number. To remove a number from a group, use the no form of this command.
number ID-number
no number ID-number
Syntax Description
ID-number
|
CLID or DNIS number, which can have up to 65 digits.
|
Note
The CLID screening feature rejects this number if it matches the CLID of an incoming call. Valid CLID numbers are all numeric, or numbers that contain the wildcard x. You can use x (signifying a single number don't care state), X or . as wildcards within each CLID number. The asterisk (*) wildcard is not accepted.
Defaults
No default behavior or values.
Command Modes
CLID group configuration
DNIS group configuration
Command History
Release
|
Modification
|
12.0(4)XI
|
This command was introduced.
|
12.1(5)T
|
This command was enhanced to add CLID numbers to a CLID group and DNIS numbers to a DNIS group.
|
Usage Guidelines
You can organize CLID numbers for a customer or service type into a CLID group. You can add multiple CLID groups to a customer profile. Add all CLID numbers into one CLID group, or subdivide the CLID numbers using criteria such as call type, geographical location, or division.
The Cisco IOS software also includes a feature that streamlines the DNIS configuration process. By replacing any digit with an X (for example, issuing the number 555222121x command), clients dialing different numbers, such as 5552221214 or 5552221215, are automatically mapped to the same customer profile. The X variable is a placeholder for the digits 1 through 9.
Examples
The following example shows the command to use to assign a number to a CLID group named "zot":
The following example shows a DNIS group called dnis_isp_1 and DNIS numbers 1234 and 5678 assigned to the DNIS group:
dialer dnis group dnis_isp_1
Related Commands
peer default ip address
To specify an IP address, an address from a specific IP address pool, or an address from the Dynamic Host Configuration Protocol (DHCP) mechanism to be returned to a remote peer connecting to this interface, use the peer default ip address command in interface configuration mode. To disable a prior peer IP address pooling configuration on an interface, or to remove the default address from your configuration, use the no form of this command.
peer default ip address {ip-address | dhcp | pool [pool-name-list]}
no peer default ip address
Syntax Description
ip-address
|
Specific IP address to be assigned to a remote peer dialing in to the interface. To prevent duplicate IP addresses from being assigned on more than one interface, this argument cannot be applied to a dialer rotary group nor to an ISDN interface.
|
dhcp
|
Retrieves an IP address from the DHCP server.
|
pool
|
Uses the global default mechanism as defined by the ip address-pool command unless the optional pool-name-list argument is supplied. This is the default.
|
pool-name-list
|
(Optional) Name of one or more local address pools created using the ip local pool command. Software retrieves an address from this pool regardless of the global default mechanism set.
|
Defaults
The default is pool.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
Usage Guidelines
This command applies to point-to-point interfaces that support the PPP or Serial Line Internet Protocol (SLIP) encapsulation. This command sets the address used on the remote (PC) side.
Note
This command replaces the async default ip address command.
This command allows an administrator to configure all possible address pooling mechanisms on an interface-by-interface basis.
The peer default ip address command can override the global default mechanism defined by the ip address-pool command on an interface-by-interface basis, as follows:
•
For all interfaces not configured with a peer default IP address mechanism (equivalent to selecting the peer default ip address pool command), the router uses the global default mechanism that is defined by the ip address-pool command.
•
If you select the peer default ip address pool pool-name-list form of this command, then the router uses the locally configured pool on this interface and does not follow the global default mechanism.
•
If you select the peer default ip address ip-address form of this command, the specified IP address is assigned to any peer connecting to this interface and any global default mechanism is overridden for this interface.
•
If you select the peer default ip address dhcp form of this command, the DHCP proxy-client mechanism is used by default on this interface and any global default mechanism is overridden for this interface.
Examples
The following command specifies that this interface will use a local IP address pool named pool3:
peer default ip address pool pool3
The following command specifies that this interface will use the IP address 172.19.34.21:
peer default ip address 172.19.34.21
The following command reenables the global default mechanism to be used on this interface:
peer default ip address pool
The following example specifies address 192.168.7.51 for asynchronous interface 6:
peer default ip address 192.168.7.51
Related Commands
Command
|
Description
|
async dynamic address
|
Specifies dynamic asynchronous addressing versus default addressing.
|
encapsulation slip
|
Enables SLIP encapsulation.
|
exec
|
Allows an EXEC process on a line.
|
ip address-pool
|
Enables an address pooling mechanism used to supply IP addresses to dial in asynchronous, synchronous, or ISDN point-to-point interfaces.
|
ip dhcp-server
|
Specifies which DHCP servers to use on a network, and specifies the IP address of one or more DHCP servers available on the network.
|
ip local pool
|
Configures a local pool of IP addresses to be used when a remote peer connects to a point-to-point interface.
|
ppp
|
Starts an asynchronous connection using PPP.
|
show cot dsp
|
Displays the current DHCP settings on point-to-point interfaces.
|
slip
|
Starts a serial connection to a remote host using SLIP.
|
peer match aaa-pools
To specify that any IP address pool name supplied by authentication, authorization, and accounting (AAA) servers must also be present in the list of pool names specified in the peer default ip address pool interface configuration command, use the peer match aaa-pools command in interface configuration mode. To configure the software to use any pool name supplied by the AAA server (default configuration), use the no form of this command.
peer match aaa-pools
no peer match aaa-pools
Syntax Description
This command has no arguments or keywords.
Defaults
Command is disabled.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(6)T
|
This command was introduced.
|
Usage Guidelines
This command provides the ability to control or restrict the use of pool names supplied by AAA to only those pool names that are configured on the router. This ability is useful in cases where the AAA server and the router and its local configuration are controlled by different administrators, as would be the case for a wholesale dial supplier where the AAA servers are owned by individual customers.
When the peer match aaa-pools command is configured on an interface, the IP address pool names used are those specified in the local configuration as part of the peer default ip address command and the pool names supplied by the AAA server.
When the no peer match aaa-pools command is used, pool name selection is controlled by the AAA server, as follows: When the AAA server supplies a pool name, that is the only pool used. If AAA does not supply a pool name, then the normal IP default pool name processing is used as described in the peer default ip address command page.
Examples
The following example shows how to configure pool name restrictions in a Resource Pool Management (RPM) customer profile template:
peer default ip address pool poolA poolB
resource-pool profile customer WORD
aaa group-configuration AAA-group1
peer default ip address pool tahoe
ppp authentication chap isdn-users
Related Commands
Command
|
Description
|
ip local pool
|
Configures a local pool of IP addresses to be used when a remote peer connects to a point-to-point interface.
|
peer default ip address
|
Specifies an IP address, an address from a specific IP address pool, or an address from the DHCP mechanism to be returned to a remote peer connecting to this interface.
|
peer pool backup
|
Directs the pool software to use the local pool name configured with the peer default ip address interface configuration command to supplement the pool names supplied by AAA.
|
peer pool static
|
Suppresses an attempt to load all dynamic pools from the AAA server when a missing pool name is encountered.
|
permission (dial peer voice)
To specify whether incoming or outgoing calls are permitted on the defined dial peer, use the permission command in dial peer voice configuration mode. To remove the specified permission, use the no form of this command.
permission {orig | term | both | none}
no permission {orig | term | both | none}
Syntax Description
orig
|
This dial peer is permitted to originate calls. Thus, the access server can accept incoming calls from the dial peer.
|
term
|
This dial peer is permitted to terminate calls. Thus, the access server can send outgoing calls to the dial peer.
|
both
|
This dial peer is permitted to originate and terminate calls. Both incoming and outgoing calls are permitted (default).
|
none
|
No incoming or outgoing calls can be made to or from this dial peer.
|
Defaults
Both incoming and outgoing calls are permitted.
Command Modes
Dial peer voice configuration
Command History
Release
|
Modification
|
12.1(3)T
|
This command was introduced.
|
Usage Guidelines
After a dial peer is associated with an incoming call, the permission is checked to determine whether incoming calls are permitted on the dial peer. If permission is not set to orig or both, the incoming call is blocked.
After a dial peer is matched for an outgoing call, the permission is checked to determine whether outgoing calls are permitted on the dial peer. If permission is not set to term or both, the outgoing call using this dial peer fails.
Note
The call may "rotary" to the next dial peer if the current dial peer does not have the huntstop command set.
Examples
The following example configures a dial peer and sets its permission to both originate and terminate calls:
answer-address 408526....
Related Commands
Command
|
Description
|
dial-peer voice
|
Enters dial-peer voice configuration mode and defines a remote VoIP dial peer.
|
pool-member
To assign a request-dialout virtual private dialup network (VPDN) subgroup to a dialer pool, use the pool-member command in VPDN request-dialout configuration mode. To remove the request-dialout VPDN subgroup from a dialer pool, use the no form of this command.
pool-member pool-number
no pool-member [pool-number]
Syntax Description
pool-number
|
Dialer pool to which this VPDN group belongs.
|
Defaults
Command is disabled.
Command Modes
VPDN request-dialout configuration
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Before you can enable the pool-member command, you must first enable the protocol l2tp command on the request-dialout VPDN subgroup. Removing the protocol l2tp command will remove the pool-member command from the request-dialout VPDN subgroup.
You can only configure one dialer profile pool (using the pool-member command) or dialer rotary group (using the rotary-group command). If you attempt to configure a second dialer resource, you will replace the first dialer resource in the configuration.
Examples
The following example configures VPDN group 1 to request L2TP dial-out to IP address 172.16.4.6 using dialer profile pool 1 and identifying itself using the local name "user1."
initiate-to ip 172.16.4.6
Related Commands
Command
|
Description
|
initiate-to
|
Specifies the IP address that will be tunneled to.
|
protocol (VPDN)
|
Specifies the Layer 2 tunneling protocol that the VPDN subgroup will use.
|
request-dialout
|
Enables an LNS to request VPDN dial-out calls by using L2TP.
|
rotary-group
|
Assigns a request-dialout VPDN subgroup to a dialer rotary group.
|
pool-range
To assign a range of modems to a modem pool, use the pool-range command in modem-pool configuration mode. To remove the range of modems, use the no form of the command.
pool-range [tty] {modem1-modemN | x/y}
no pool-range [tty] {modem1-modemN | x/y}
Syntax Description
tty
|
(Optional) Sets the range to terminal controller (TTY) lines.
|
modem1-modemN
|
Range of lines, which correspond to a range of modems or to a modem pool. A hyphen (-) is required between the two numbers. The range of modems you can choose from is equivalent to the number of modems in your access server that are not currently associated with another modem pool, up to a maximum of 48.
|
x/y
|
Slot/port numbers for an internal modem. A range of numbers is not accepted. The slash mark is required.
|
Defaults
Command is disabled. All modems are configured to be part of the system default modem pool.
Command Modes
Modem pool configuration
Command History
Release
|
Modification
|
11.2 P
|
This command was introduced on the Cisco AS5200 and Cisco AS5300.
|
Usage Guidelines
For a complete description of modem pools and how they are configured on Cisco access servers, see the command page for the modem-pool command.
Replace themodem1-modemN arguments with the modem TTY line numbers that correspond with the range of modems you want in the modem pool. TTY line numbers start from 1, and they map to modem numbers that start from 0. For example, if you want to include modems 1/0 through 1/23 in a pool range, use the TTY line numbers 1 to 24. To verify the modem to TTY line numbering scheme, use the show modem slot/port command.
Note
MICA technologies modems and Microcom modems support incoming analog calls over ISDN PRI. However, only MICA modems support modem pooling for CT1 and CE1 configurations with channel-associated signaling.
Examples
The following example assigns modem TTY line numbers 30 to 50 to a modem pool. The Dialed Number Information Service (DNIS) number is set to 2000. The customers dialing 2000 are guaranteed access to 21 modems. The 22nd client to dial in is refused connectivity because the maximum number of allowable connections is exceeded.
called-number 2000 max-conn 21
The following configuration rejects the pool-range 30 command, because modem TTY line 30 is already a member of the modem pool v90service, which was configured in the previous example. Each modem in the access server is automatically assigned to a unique TTY line. TTY line numbers are assigned according to your shelf, slot, or port hardware configuration.
% TTY 30 is already in another pool.
Related Commands
Command
|
Description
|
called-number (modem pool)
|
Assigns a called party number to a pool of modems.
|
clear modempool-counters
|
Clears active or running counters associated with one or more modem pools.
|
modem-pool
|
Creates a new modem pool or specifies an existing modem pool, which allows you to physically or virtually partition your access server for dial-in and dial-out access.
|
show modem-pool
|
Displays the configuration and connection status for one or more modem pools.
|
port (global)
To enter the port configuration mode, use the port command in global configuration mode. To exit port configuration mode, use the no form of this command.
Cisco AS5400 with NextPort DFC
port {slot | slot/port}
no port {slot | slot/port}
Cisco AS5800 with Universal Port Card
port {shelf/slot | shelf/slot/port}
no port {shelf/slot | shelf/slot/port}
Syntax Description
slot
|
All ports on the specified slot. For the Cisco AS5400, slot values range from 0 to 7. The slash mark is required.
|
slot/port
|
All ports on the specified slot and SPE. For the Cisco AS5400, slot values range from 0 to 7 and port values range from 0 to 107. The slash mark is required.
|
shelf/slot
|
All ports on the specified shelf and slot. For the Cisco AS5800, shelf values are 0 and 1, and UPC slot values range from 2 to 11. The slash mark is required.
|
shelf/slot/port
|
All ports on the specified SPE. For the Cisco AS5800, shelf values are 0 and 1, slot values range from 2 to 11, and port values range from 0 to 323. The slash mark is required.
|
Defaults
Command is disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.1(3)T
|
This command was introduced.
|
Usage Guidelines
The port command helps you to enter the port configuration mode. The port configuration mode allows you to shut down or put individual ports or ranges of ports in busyout mode.
Examples
The following example shows how to enter port configuration mode on ports 1 to 18 to perform further tasks on the ports:
Router(config)# port 1/1 1/18
Router(config-port)# shutdown
Related Commands
Command
|
Description
|
clear port
|
Resets the port and clears any active calls to the port.
|
port modem autotest
To automatically and periodically perform a modem diagnostics test for modems inside the access server or router, use the port modem autotest command in global configuration mode. To disable or turn off the modem autotest service, use the no form of this command.
port modem autotest {error threshold | minimum modems | time hh:mm [interval]}
no port modem autotest
Syntax Description
error threshold
|
Maximum modem error threshold. When the system detects this many errors with the modems, the modem diagnostics test is automatically triggered. Specify a threshold count from 3 to 50.
|
minimum modems
|
Minimum number of modems that will remain untested and available to accept calls during each test cycle. You can specify from 5 to 48 modems. The default is 6 modems on the Cisco AS5400. The range for the Cisco AS5800 is from 73 to 756.
|
time hh:mm
|
Time you want the modem autotest to begin. You must use the military time convention and a required colon (:) between the hours and minutes variables for this feature. For example, 1:30 p.m. is issued as 13:30.
|
interval
|
(Optional) Long-range time variable used to set the modem autotest more than one day in advance. The range of hours is from 1 hour to 168 hours. For example, if you want to run the test once per week, issue 168. There are 168 hours in one week.
|
Defaults
Modem diagnostics tests are disabled.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
12.1(1)XD
|
This command was introduced on the Cisco AS5400 as the port modem autotest command and replaced the modem autotest command for the NextPort dial feature card (DFC) only.
|
12.1(3)T
|
This command was implemented on the Cisco AS5400 and Cisco AS5800.
|
Examples
The following example shows how to set the modem autotest to run once per week at 3:00 a.m. Additionally, the autotest activates if the system detects a modem error count higher than 40 errors.
Determine the current time set on the access server with the show clock EXEC command. In this example, the time and date set is 3:00 p.m, Monday, August 25, 1997:
*15:00:01.031 EST Aug 25 1997
Enter global configuration mode and set the time you want the modem autotest to activate. In this example, the access server is configured to run the modem autotest at 3:00 a.m. and every 168 hours (week) thereafter:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# port modem autotest time 03:00 168
Configure the autotest to activate if the system detects a high modem error count. In this example, the autotest activates if the system detects a modem error count higher than 40 errors. For the list of modem errors that are monitored by the modem autotest command, see the show modem call-stats command.
Router(config)# port modem autotest error 40
Related Commands
Command
|
Description
|
show clock
|
Displays the system clock.
|
show modem
|
Displays a high-level performance report for all the modems or a single modem inside Cisco AS5200 and Cisco AS5300 access servers.
|
show modem test
|
Displays the modem test log.
|
ppp
To start an asynchronous connection using PPP, use the ppp command in EXEC mode.
ppp {/default | {remote-ip-address | remote-name} [@tacacs-server]} [/routing] negotiate
Syntax Description
/default
|
Makes a PPP connection when a default address has been configured.
|
remote-ip-address
|
IP address of the client workstation or PC. This parameter can be specified only if the line is set for dynamic addresses using the async address dynamic line configuration command.
|
remote-name
|
Name of the client workstation or PC. This parameter can be specified if the line is set for dynamic addresses using the async address dynamic line configuration command.
|
@tacacs-server
|
(Optional) IP address or IP host name of the TACACS server to which the user's TACACS authentication request is sent. The at sign is required.
|
/routing
|
(Optional) Indicates that the remote system is a router and that routing messages should be exchanged over the link. The line must be configured for asynchronous routing using PPP encapsulation.
|
negotiate
|
Use PPP negotiated IP address.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
When you connect from a remote node computer to an EXEC session on the access server and want to connect from the access server to a device on the network, issue the ppp command.
If you specify an address for the TACACS server (either /default or @tacacs-server), the address must be the first parameter in the command after you type ppp. If you do not specify an address or enter the default keyword, you are prompted for an IP address or host name. You can enter the default keyword at this point.
To terminate a session, disconnect from the device on the network using the command specific to that device. Then, exit from the EXEC by using the exit command.
Examples
The following example shows a line that is in asynchronous mode using PPP encapsulation. The name of the computer (ntpc in this example) must be in the Domain Name System (DNS) so that it can be resolved to a real IP address). The computer must be running a terminal emulator program.
ppp accm
To specify the Asynchronous Control Character Map (ACCM) sent to a peer in PPP outbound requests, use the ppp accm command in interface configuration mode. To restore the default state, use the no form of this command.
ppp accm hex-number
no ppp accm
Syntax Description
hex-number
|
Specifies the initial value for the ACCM. The value must be a hexadecimal number in the range from 0x0 to 0xffffffff, where the bit positions from right to left correspond to the characters 0x00 through 0x1F. The default character map (0xA0000) escapes the characters represented by 0x11 (^Q, DC1, and X-on) and 0x13 (^S, DC3, and X-off).
Note The leading 0x is not necessary when entering the hex-number argument, but is accepted by the software.
|
Defaults
The default ACCM is 0xA0000.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.2
|
This command was introduced.
|
Usage Guidelines
The ppp accm command specifies the control character mapping table sent to a peer in a PPP outbound Config-Request packet, to inform the peer which characters need to be escaped when transmitting data containing control characters. The escaped characters set by the ppp accm command are useful for allowing data to pass uninterpreted through a network that would normally interpret the control sequences as a command.
For example, the ^Q and ^S characters are software flow control commands used by asynchronous modems to start and stop data transmissions. To allow these characters to be sent as part of a data stream and not be interpreted as control codes by intervening devices, the characters must be escaped, and the ppp accm command specifies which characters to use.
The ppp accm command is meaningful only on asynchronous interfaces. If entered on other interface types, it will be ignored.
Examples
In the following example, all characters can be transmitted intact to the receiver so that it is not necessary for the transmitter to escape anything:
ppp bap call
To set PPP Bandwidth Allocation Protocol (BAP) call parameters, use the ppp bap call command in interface configuration mode. To disable processing of a specific type of incoming connection, use the no form of this command.
ppp bap call {accept | request | timer seconds}
no ppp bap call {accept | request | timer}
Syntax Description
accept
|
Peer initiates link addition. This is the default.
|
request
|
Local side initiates link addition.
|
timer seconds
|
Number of seconds to wait between call requests the router sends, in the range from 2 to 120 seconds. No default value is set.
|
Defaults
Peers can initiate the addition of links to a multilink bundle; the timer is disabled.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
Usage Guidelines
This command can be included in a virtual interface template for configuring virtual interfaces or can be used to configure a dialer interface.
Examples
The following example configures a dialer interface to accept calls. Accepting calls is the default, but the command is included for the sake of the example.
ppp bap link types isdn analog
ppp bap timeout pending 60
Related Commands
Command
|
Description
|
ppp bap callback
|
Enables PPP BAP callback and set callback parameters.
|
ppp bap drop
|
Sets parameters for removing links from a multilink bundle.
|
ppp bap link types
|
Specifies the types of links that can be included in a specific multilink bundle.
|
ppp bap callback
To enable PPP Bandwidth Allocation Protocol (BAP) callback and set callback parameters, use the ppp bap callback command in interface configuration mode. To remove the PPP BAP callback configuration, use the no form of this command.
ppp b