Table Of Contents
multilink
multilink bundle-name
multilink max-fragments
multilink virtual-template
multilink-group
netbios nbf
network-clock-priority
network-clock-select
number
pad
peer default ip address
pool-member
pool-range
ppp
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 ipcp
ppp iphc max-header
ppp iphc max-period
ppp iphc max-time
ppp lcp fast-start
ppp loopback ignore
ppp max-bad-auth
ppp ms-chap refuse
ppp ms-chap-v2 refuse
ppp multilink
ppp multilink fragmentation
ppp multilink fragment-delay
ppp multilink idle-link
ppp multilink interleave
ppp quality
ppp reliable-link
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 global configuration command. 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
|
Uses the authenticated name of the peer. This is the default.
|
endpoint
|
Uses the endpoint discriminator of the peer.
|
both
|
Uses the 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 max-fragments
To set the maximum number of fragments a packet will be segmented into before being sent over the bundle, use the multilink max-fragments interface configuration command. To reset fragmentation to the default value, use the no form of this command.
multilink max-fragments fragments
no multilink max-fragments
Syntax Description
fragments
|
Maximum number of fragments in the range from 1 to 16.
|
Defaults
16 fragments
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
Usage Guidelines
Use the multilink max-fragments command to control the number of fragments into which a PPP frame may be fragmented. The multilink max-fragments command has been used to disable fragmentation entirely by setting the number of fragments to 1. This setting is better accomplished using the no ppp multilink fragmentation command.
The limit set using the multilink max-fragments command applies only when Multilink PPP (MLP) is fragmenting packets in a mode where it is constraining the number of fragments rather than the size of the fragments. See the description about fragmentation modes in the section "Usage Guidelines" of the ppp multilink fragment-delay command for more details.
Examples
The following example uses the multilink max-fragments command to fragment each frame into no more than four fragments:
multilink max-fragments 4
Related Commands
Command
|
Description
|
ppp multilink fragmentation
|
Enables packet fragmentation.
|
ppp multilink fragment-delay
|
Specifies a maximum size, in units of time, for packet fragments on an MLP bundle.
|
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.
multilink virtual-template number
Syntax Description
number
|
Number of the virtual template; an integer in the range 1 through 9.
|
Defaults
Disabled. 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
ip local pool default 2.2.2.2
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.
|
ip local pool
|
Configures a local pool of IP addresses to be used when a remote peer connects to a point-to-point interface.
|
multilink-group
To designate an interface as part of a multilink leased line bundle, use the multilink-group command in interface configuration mode. To remove an interface from a bundle, use the no form of this command.
multilink-group group-number
no multilink-group
Syntax Description
group-number
|
Number of the multilink bundle (a nonzero number).
|
Defaults
Disabled
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
12.0(3)T
|
Support for MLP was introduced for VIP-based T1 and E1 interfaces on the Cisco 7500 Series.
|
12.0(4)T
|
Support for this command was implemented for non-VIP-based T1 and E1 interfaces and on the Cisco 7200 Series.
|
Usage Guidelines
All interfaces in a multilink bundle must have the same bandwidth.
Examples
The following example designates serial interface 1 as part of multilink bundle 1:
Related Commands
Command
|
Description
|
interface multilink
|
Creates a multilink bundle or enters multilink interface configuration mode.
|
ppp multilink fragmentation
|
Enables or disables MLP fragmentation. Disabling allows multilink packets to be forwarded across platforms.
|
netbios nbf
To enable the NetBIOS Frames Protocol (NBF) on an interface, use the netbios nbf command in interface configuration mode. Use the no form of this command to disable NetBIOS Frames Protocol support on an interface.
netbios nbf
no netbios nbf
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following example enables NetBIOS Frames Protocol 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 netbios cache
|
Displays a list of NetBIOS cache entries.
|
show nbf sessions
|
Displays NetBEUI connection information.
|
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 . Use the no form of this command to restore the default (low) clock-recovery priority.
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.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(3)XG
|
This command was introduced.
|
Usage Guidelines
This command is supported only on the Cisco MC3810.
This command is only valid for BRI ports configured as TE. It allows you to select which PINX (PBX) is the first-priority clock source.
This command becomes effective only when the BVM is the clock source for the Cisco MC3810; this happens in 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
network-clock-select
To specify selection priority for the clock sources, use the network-clock-select command in global configuration mode. Use the no form of this command to cancel the network clock selection.
network-clock-select priority {serial 0 | system | bvm | controller}
no network-clock-select priority {serial 0 | system | bvm | controller}
Syntax Description
priority
|
Selection priority for the clock source from 1 (highest) to 4 (lowest).
|
serial 0
|
Clocking priority for serial interface 0.
|
system
|
Clocking priority for the system clock.
|
bvm
|
Clocking priority for the BRI voice module (BVM).
|
controller
|
Clocking priority for either the trunk controller (T1/E1 0) or the digital voice module (T1/E1/ 1).
|
Defaults
No network clock source is specified.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.3MA
|
This command was introduced.
|
12.0(3)XG
|
The BVM as a possible network clock source was added.
|
Usage Guidelines
When an active clock source fails, the system chooses the next lower priority clock source specified by this command. When a higher-priority clock becomes available, the system automatically reselects the higher-priority clock source.
Note
If the BRI backup port (BRI 0) is installed and becomes active, it automatically recovers network clock for as long as it remains active. However, you can not give port BRI 0 a clock-selection priority.
Use the network-clock-select command to establish the clock-selection priority when there are multiple sources of line (network) clocking in a Cisco MC3810. Possible sources of line clocking for the Cisco MC3810 are the BRI voice module (BVM), the multiflex trunk module (MFT), and a serial port configured for clock rate line.
Examples
The following example sets a possible clock selection priority in a Cisco MC3810 with a digital voice module (DVM) installed:
network-clock-select 1 T1 0
network-clock-select 2 T1 1
network-clock-select 3 serial 0
network-clock-select 4 system
The following example sets a possible clock selection priority in a Cisco MC3810 with a BRI voice module (BVM) installed:
network-clock-select 1 T1 0
network-clock-select 2 bvm
network-clock-select 3 serial 0
network-clock-select 4 system
Related Commands
Command
|
Description
|
network-clock-switch
|
Configures the switch delay time to the next priority network clock source when the current network clock source fails.
|
network-clock-priority
|
Specifies the clock-recovery priority for the BRI voice ports in a BVM.
|
number
To add a DNIS number to a dialer DNIS group, use the number command in DNIS group configuration mode followed by the specifying number. Use the no form of this command to remove a DNIS number from a DNIS group.
number number
no number number
Syntax Description
number
|
Specifies a DNIS number, which can have up to 65 digits.
|
Defaults
No default behavior or values.
Command Modes
DNIS group configuration
Command History
Release
|
Modification
|
12.0(4)XI
|
This command was introduced.
|
Usage Guidelines
Use the number DNIS group configuration command to enter a DNIS number to a dialer DNIS group. 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 place holder for the digits 1 through 9.
Examples
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
Command
|
Description
|
dnis group
|
Includes a group of DNIS numbers in a customer profile.
|
pad
To log in to a packet assembler/disassembler (PAD), use the pad command in EXEC mode.
pad {x121-address | hostname} [/cud text] [/debug] [/profile name] [/quiet message] [/reverse]
[/use-map]
Syntax Description
x121-address
|
Specifies the X.121 address of the X.25 host.
|
hostname
|
Specifies the X.25 host name if the host-to-address mapping has been set with the X.25 host command.
|
/cud text
|
(Optional) Includes the specified text in the Call User Data field of the outgoing Call Request Packet.
|
/debug
|
(Optional) Displays the informational level of logging messages whenever the remote host changes an X.3 parameter setting or sends any other X.29 control packet.
|
/profile name
|
(Optional) Sets X.3 PAD parameters for the name script. This is the same as issuing the x29 profile global configuration command when translating X.25. If the X.29 profile is set to default, the profile is applied to all incoming X.25 PAD calls, including the calls used for protocol translation.
|
/quiet message
|
(Optional) Suppresses information messages. Replace the argument message with the actual message that you want to suppress.
|
/reverse
|
(Optional) Causes reverse-charge calls to be accepted on a per-call (rather than a per-interface) basis.
|
/use-map
|
(Optional) Applies x25 map pad command entry options (such as CUD and idle) and facilities (such as packet in, packet out, win in, and win out) to the outgoing PAD call. This function occurs only if a matching X.121 destination address exists in a x25 map pad command entry.
|
Command Modes
User EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
The pad command supports one-word connections. You need not enter the pad command; just entering the address is enough to start the connection. A PAD can also be accessed and X.3 parameters configured with the x28 EXEC command, which uses the standard X.28 user interface.
You can have several PAD connections open at the same time and switch between them. You also can exit a connection and return to the user EXEC prompt at any point. To open a new connection, first exit the current connection by entering the escape sequence (Ctrl-Shift-6 then x [Ctrl^x] by default) to return to the EXEC prompt, then open the new connection. If the /use-map option is selected on the outgoing pad command, the x25 map pad command entries are searched for a matching X.121 destination address. If a match is found, the x25 map pad command entry options (such as CUD and idle) and facilities (such as packet in, packet out, win in, and win out) are applied to the outgoing PAD call.
To display information about packet transmission and X.3 PAD parameter settings, use the show x25 pad command.
To exit a session, simply log off the remote system. Then, terminate the active session by entering the exit command.
Examples
Use the ? command to display pad command options, as shown in this example:
/profile Use a defined X.3 profile
/quiet Suppress informational messages
/reverse X25 Address reverse
/use-map Use x25 map pad command facilities for outgoing Calls
The following example starts a PAD session:
You can also access a PAD using standard X.28 commands. The following example enters X.28 mode with the x28 EXEC command and configures a PAD with the set X.3 parameter command. The set command sets the idle time delay to 40 seconds.
The following example uses the /use-map option to configure a larger window and packet size than the default specified on the interface, and it sets the VC idle time to 2 seconds. Notice that the map values are used rather than the interface default values.
Router-A(config-if)# x25 map pad 2194441 cud gmcmilla windowsize 7 7 packetsize 1024
1024 idle 2
%SYS-5-CONFIG_I: Configured from console by console.
Router-A# pad 2194441 /cud gmcmillla /use-map
06:31:12: pad_open_connection: found a matching x25 map pad
06:31:12: Serial1: X.25 O R1 Call (22) 8 lci 1024
06:31:12: From(7): 2191111 To(7): 2194441
06:31:12: Facilities: (6)
06:31:12: Packet sizes: 1024 1024
06:31:12: Window sizes: 7 7
06:31:12: Call User Data (12): 0x01000000 (pad)
06:31:12: Serial1: X.25 I R1 Call Confirm (5) 8 lci 1024
06:31:12: From(0): To(0):
06:31:12: Facilities: (0)
06:31:12: PAD0: Call completed
Related Commands
Command
|
Description
|
translate x25
|
Automatically translates the request to another outgoing protocol connection type when an X.25 connection request to a particular destination address is received.
|
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. Use the no form of this command to disable a prior peer IP address pooling configuration on an interface.
To remove the default address from your configuration, use the no form of this command also.
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 command argument cannot be applied to a dialer rotary group nor to an ISDN interface.
|
dhcp
|
Retrieve an IP address from the DHCP server.
|
pool
|
Use 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 a 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 called pool3:
peer default ip address pool pool3
The following command specifies that this interface will use the IP address 172.140.34.21:
peer default ip address 172.140.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.31.7.51 for async interface 6:
peer default ip address 192.31.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.
|
pool-member
To assign a request-dialout virtual private dialup network (VPDN) subgroup to a dialer pool, use the pool-member command in 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
|
The dialer pool that this VPDN group belongs to.
|
Defaults
Disabled
Command Modes
Request-dialout configuration
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
You must first enable the protocol l2tp on the request-dialout VPDN subgroup before you can enable the pool-member command. Removing the protocol l2tp command will remove the pool-member command from the request-dialout 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 dialout to IP address 172.5.4.6 using dialer profile pool 1 and identifying itself using the local name harold.
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.
Cisco AS5200 and Cisco AS5300 access servers
pool-range number-number
Syntax Description
number-number
|
Assigns a range of TTY lines, which correspond to ranges of modems, to a modem pool. A dash (-) is required between the two modem 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.
|
Defaults
Disabled. All modems are configured to be part of the system default modem pool.
Command Modes
Modem pool configuration
Command History
Release
|
Modification
|
11.2P
|
This command was introduced.
|
Usage Guidelines
For a complete description of modem pools and how they are configured on Cisco access servers, see the command reference page for the modem-pool command.
Replace the number-number variable 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, which 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 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 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
|
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.
|
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]
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 only be specified 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.
|
/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.
|
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 PC's name (ntpc in this example) must be in the Domain Name System (DNS) so that it can be resolved to a real IP address). The PC must be running a terminal emulator program.
ppp bap call
To set PPP Bandwidth Allocation Protocol (BACP) call parameters, use the ppp bap call command in interface configuration mode. Use the no form of this command to disable processing of a specific type of incoming connection.
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 2 to 120 seconds. No default value is set.
|
Defaults
accept—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 BACP 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 (BACP) callback and set callback parameters, use the ppp bap callback command in interface configuration mode. Use the no form of this command to remove the PPP BACP callback configuration.
ppp bap callback {accept | request | timer seconds}
no ppp bap callback {accept | request | timer}
Syntax Description
accept
|
Local router initiates link addition upon peer notification.
|
request
|
Local router requests that a peer initiate link addition.
|
timer seconds
|
Number of seconds to wait between callback requests the router sends, in the range 2 to 120 seconds. Disabled by default.
|
Defaults
Callback is disabled and no callback parameters are set.
The timer is disabled.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
Examples
The following example configures a BRI interface for active mode BACP:
dialer load-threshold 10 either
dialer map ip 172.21.13.101 name bap-peer 14085778899
ppp bap pending timeout 30
ppp bap number default 5664567
ppp bap number secondary 5664568
Related Commands
Command
|
Description
|
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.
|
show ppp bap
|
Displays the configuration settings and run-time status for a multilink bundle.
|
ppp bap drop
To set parameters for removing links from a multilink bundle, use the ppp bap drop command in interface configuration mode. Use the no form of this command to disable a specific type of default processing.
ppp bap drop {accept | after-retries | request | timer seconds}
no ppp bap drop {accept | after-retries | request | timer}
Syntax Description
accept
|
Peer can initiate link removal. Enabled by default.
|
after-retries
|
Local router can remove the link without Bandwidth Allocation Protocol (BACP) negotiation when no response to the drop requests arrives.
|
request
|
Local router can initiate removal of a link. Enabled by default.
|
timer seconds
|
Number of seconds to wait between drop requests sent.
|
Defaults
accept, request: Peers can initiate link removal and this router also can initiate link removal.
no ppp bap drop after-retries: The link is not dropped when there is no response to drop requests.
timer: Disabled; no default value is defined.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
Usage Guidelines
The no ppp bap drop accept command disables the router's ability to respond favorably to link drop requests from a peer. However, the router can still remove the link when it receives such requests.
The no ppp bap drop after-retries command is the default behavior; the ppp bap drop after-retries command must be entered explicitly to be effective.
The no ppp bap drop request command disables the router's ability to send link drop requests to a peer. However, the peer can still remove the link on its own behalf; for example, when there is too little traffic to justify keeping the link up.
The ppp bap max command specifies the maximum number of requests and retries.
Examples
The following partial example sets a 60-second wait between drop requests:
Related Commands
Command
|
Description
|
ppp bap max
|
Sets upper limits on the number of retransmission for PPP BACP.
|
ppp bap link types
To specify the types of links that can be included in a specific multilink bundle, use the ppp bap link types command in interface configuration mode. Use the no form of this command to remove a type of interface that was previously allowed to be added.
ppp bap link types [isdn] [analog]
no ppp bap link types [isdn] [analog]
Syntax Description
isdn
|
(Optional) ISDN interfaces can be added to a multilink bundle. This is the default.
|
analog
|
(Optional) Asynchronous serial interfaces can be added to a multilink bundle.
|
Defaults
isdn
Command Modes