|
|
To enable encapsulation for communication with routers or bridges using the Combinet Proprietary Protocol (CPP), use the encapsulation cpp command in interface configuration mode. Use the no form of this command to disable CPP encapsulation.
encapsulation cppSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
11.2 This command was introduced.
Release
Modification
Usage Guidelines
Use this command to communicate over an ISDN interface with Cisco 700 and 800 series (formerly Combinet) routers that do not support PPP but do support CPP.
Currently, most Cisco routers do support PPP. Cisco routers can communicate over ISDN with these devices by using PPP encapsulation, which supports both routing and fast switching.
The Cisco 700 and 800 series routers support only IP, IPX, and bridging. For AppleTalk, these Cisco routers automatically perform half-bridging.
This command is supported on ISDN BRIs and Primary Rate Interfaces (PRIs) only.
Examples
The following example configures BRI 0 to communicate with a router or bridge that does not support PPP:
interface bri 0 encapsulation cpp cpp callback accept cpp authentication
The following example configures PRI interface serial 1/1:23 to communicate with a router or bridge that does not support PPP:
controller t1 1/1 framing esf linecode b8zs pri-group timeslots 1-23 isdn switchtype primary-4ess ! interface Serial1/1:23 encapsulation cpp cpp callback accept
cpp authentication
Related Commands
Enables negotiation of authentication with a router or bridge that supports the CPP and that is calling in to this router. cpp callback accept Enables the router to accept callback from a router or bridge that supports the CPP.
Command
Description
To download firmware into the modems, use the firmware location command in Service Processing Element (SPE) configuration mode. The no form of the command reverts the router back to the system embedded image default.
firmware location {system | flash}: filename
Syntax Description
system If system is specified, the router loads the firmware from a built-in file within the Cisco IOS image. flash If flash is specified, the router loads the firmware from the Flash NVRAM located within the router. filename The name of the desired firmware file. If system is specified, enter the path to the filename you want to download.
Defaults
None
Command Modes
SPE configuration
Command History
12.0(4)XI1 This command was introduced. 12.0(6)T This command was migrated to Release 12.0(6)T.
Release
Modification
Usage Guidelines
Use the firmware location SPE configuration command to download firmware into your modems. The no form of the command reverts the router back to the system embedded default. When the access server is booted, the firmware location command displays the location for the firmware that is embedded in the Cisco IOS image. If the firmware location command was given to download a firmware image from flash and then the no version of the exact command is subsequently given, then the firmware location command will download the embedded firmware in Cisco IOS Software.
The firmware location command was first supported in Cisco IOS Release 12.0(4)XI1 along with the Resource Pool Management feature (although it can be used independently). For earlier images, use the copy command. For the Cisco IOS Release 12.0(4)XI1 images, the copy {flash | system | tftp} modem command will be disabled for MICA technologies modems and newer versions of Microcom modems (that is, 56 kbps). Old V.34 Microcom modems still use the copy command for downloading in Cisco IOS Release 12.0(4)XI1 images.
![]() |
Note This command should be used when traffic is low because the firmware location download will not begin until the modems have no active calls. Otherwise, use the firmware upgrade command to customize the scheduling of modem downloads for your needs. |
![]() |
Note The firmware location command is a configuration command---if you do not save it using the write memory command, then the configuration will not be saved; hence, the downloading of the specified firmware will not occur after the next reboot. |
Examples
The following examples show downloads of firmware that was not bundled with the Cisco IOS image:
spe 1/2 1/4 firmware location flash:portware.2620.ios spe 2/2 2/8 firmware location flash:mcom-fw-dsp.5.1.9_47.22.bin spe 2/12 2/23 firmware location feature_card_flash
The following examples show downloads of firmware that was bundled with the Cisco IOS image:
spe 2/9 2/9 firmware location system:/ucode/microcom_firmware spe 1/5 1/7 firmware location system:/ucode/mica_port_firmware
Related Commands
firmware upgrade Specifies the method in which the SPE will be downloaded.
Command
Description
To modify the way in which the Service Processing Element (SPE) will be downloaded, use the firmware upgrade command in SPE configuration mode. The no form of the command reverts the SPE back to the default SPE firmware upgrade option, busyout.
firmware upgrade {busyout | recovery | reboot}
Syntax Description
busyout Starts firmware upgrade immediately. (Default) recovery Delays firmware upgrade until recovery maintenance time. reboot Delays firmware upgrade until reboot.
Defaults
Busyout
Command Modes
SPE configuration
Command History
12.0(6)T This command introduced.
Release
Modification
Usage Guidelines
This command is for SPEs that contain more than 1 modem.
The SPE firmware location command is designed to integrate all continuous SPE ranges containing the same firmware location. However, the firmware upgrade command will not affect the SPE ranges. As such, all SPEs within the SPE range must have the same firmware upgrade mode or the router will default the upgrade mode to busyout. As such, if you want to upgrade a single SPE within an existing SPE range with a different upgrade mode than is currently configured, you must first change the upgrade mode for the entire SPE range and then change the firmware location for the specific SPE being upgraded.
Furthermore, each time you merge SPE ranges due to configuration changes, verify that the configuration of the SPE firmware upgrade remains effective to what is desired.
Examples
If the busyout upgrade command is specified, or if no upgrade mode is specified, the SPE modems are set into a "pending download" state when you use the firmware location command on the specified SPE. The "pending download" state prevents any modem in that state to be allocated for new calls until the state is cleared. Modems with active calls remain active for their call durations, but enter the "pending download" state when they terminate. This "pending download" state can only be cleared when the SPE is finally downloaded. When all modems within the SPE are in the "pending download" and no active calls remain on the SPE, the SPE is reloaded. The busyout option is the fastest way to upgrade modems on an active router but can severely impact the capacity of the router during the upgrade. This is the default option for the firmware upgrade process:
firmware upgrade busyout
If reboot upgrade is specified, the SPE modems are not reloaded to the new firmware location until the router is rebooted. The reboot upgrade option is useful for routers which need to have their SPE upgraded and are also going to be rebooted for maintenance. The new firmware can be configured, but will not take affect until the reboot takes place:
firmware upgrade reboot
If recovery upgrade is specified, the SPE modem are reloaded based on the modem recovery algorithm. The SPE modems are all set into a "pending upgrade" state when you use the firmware location command on this SPE. The "pending upgrade" state continues to allow modems to be allocated to modems for as long as there are active calls on the SPE. Only when no active calls exist on the SPE will the firmware download take place. Furthermore, at the configured "modem recovery maintenance time" (3:00 a.m.), the modem recovery maintenance process will, in a controller fashion, attempt to reload the modems by busying out the modems for a window duration of time to make the download take place. Consult the modem recovery documentation for further details. The recovery upgrade option is the least impacting way to upgrade modems on an active router. Capacity is kept at a maximum. However, this option may take a few days for all modems to be reloaded to the new firmware location:
firmware upgrade recovery
Related Commands
firmware location Downloads firmware into the modems from this file location. modem recovery maintenance time Specifies the modem maintenance recovery behavior, time of day for the scheduled modem recovery. modem recovery maintenance window Specifies the modem maintenance recovery behavior, amount of time for normal recovery to take place. modem recovery maintenance action Specifies the modem maintenance recovery behavior, mode of recovery.
Command
Description
To set the method of data flow control between the terminal or other serial device and the router, use the flowcontrol command in line configuration mode. Use the no form of this command to disable flow control.
flowcontrol {none | software [lock] [in | out] | hardware [in | out]}
Syntax Description
none Turns off flow control. software Sets software flow control. An optional keyword specifies the direction: in causes the Cisco IOS software to listen to flow control from the attached device, and out causes the software to send flow control information to the attached device. If you do not specify a direction, both are assumed. lock (Optional) Used to make it impossible to turn off flow control from the remote host when the connected device needs software flow control. This option applies to connections using the Telnet or rlogin protocols. hardware Sets hardware flow control. An optional keyword specifies the direction: in causes the software to listen to flow control from the attached device, and out causes the software to send flow control information to the attached device. If you do not specify a direction, both are assumed. For more information about hardware flow control, see the hardware manual that was shipped with your router.
Defaults
No flow control
Command Modes
Line configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
When software flow control is set, the default stop and start characters are Ctrl-S and Ctrl-Q (XOFF and XON). You can change them with the stop-character and start-character commands.
If a remote Telnet device requires software flow control, the remote system should not be able to turn it off. Using the lock option makes it possible to refuse "dangerous" Telnet negotiations if they are inappropriate.
Examples
The following example sets hardware flow control on line 7:
line 7 flowcontrol hardware
Related Commands
Sets the flow control start character. Sets the flow control stop character.
Command
Description
To force the L2TP network server (LNS) to reauthenticate the client, use the force-local-chap command in VPDN group configuration mode. To disable reauthentication, use the no form of this command.
force-local-chapSyntax Description
This command has no arguments or keywords.
Defaults
CHAP authentication at the LNS is disabled; default authentication occurs at the LAC.
Command Modes
VPDN group configuration
Command History
11.3(5)AA This command was introduced. 12.0(1)T This command was migrated to Release 12.0(1)T. 12.0(5)T This command was modified to only be available if the accept-dialin VPDN subgroup is enabled.
Release
Modification
Usage Guidelines
You must enable the accept-dialin command on the VPDN group before you can use the force-local-chap command. Removing the accept-dialin command will remove the force-local-chap command from the VPDN group.
This command is only used if CHAP authentication is enabled for PPP (using the ppp authentication chap command). This command forces the LNS to re-authenticate the client in addition to the proxy authentication that occurs at the LAC. If the force-local-chap command is used, then the authentication challenge occurs twice. The first challenge comes from the LAC and the second challenge comes from the LNS. Some PPP clients may experience problems with double authentication. If this occurs, authentication challenge failures may be seen if the debug ppp authentication command is enabled.
Examples
The following example enables CHAP authentication at the LNS:
vpdn-group 1 accept dialin protocol l2tp virtual-template 1 terminate-from pat force-local-chap on-mismatch
Related Commands
Specifies the LNS to use for authenticating, and the virtual template to use for cloning, new virtual access interfaces when an incoming L2TP tunnel connection is requested from a specific peer. Allows the LNS to renegotiate the LCP on dial-in calls, using L2TP or L2F.
Command
Description
To select the frame type for the T1 or E1 data line, use the framing command in controller configuration mode.
T1 Line
framing {sf | esf}
E1 Line
Syntax Description
sf Specifies Super Frame as the T1 frame type. esf Specifies Extended Super Frame as the T1 frame type. crc4 Specifies CRC4 frame as the E1 frame type. no-crc4 Specifies no CRC4 frame as the E1 frame type. australia (Optional) Specifies the E1 frame type used in Australia.
Defaults
Super Frame is the default on a T1 line. CRC4 frame is the default on an E1 line.
Command Modes
Controller configuration
Command History
11.1 This command was introduced.
Usage Guidelines
Use this command in configurations where the router or access server is intended to communicate with T1 or E1 fractional data line. The service provider determines which framing type, either the sf, esf, or crc4 keyword, is required for your T1/E1 circuit.
Examples
The following example selects Extended Super Frame as the T1 frame type:
Related Commands
Defines the time slots that belong to each T1 or E1 circuit. linecode Selects the linecode type for T1 or E1 line. To create a list of member asynchronous interfaces (associated with a group interface), use the group-range command in interface configuration mode. Use the no form of the command to remove an interface from the member list.
Syntax Description
low-end-of-range Beginning interface number to be made a member of the group interface. high-end-of-range Ending interface number to be made a member of the group interface.
Defaults
No interfaces are designated as members of a group.
Command Modes
Interface configuration
Command History
11.1 This command was introduced.
Usage Guidelines
Using the group-range command, you create a group of asynchronous interfaces that are associated with a group asynchronous interface on the same device. This group interface is configured by using the interface group-async command. This one-to-many structure allows you to configure all associated member interfaces by entering one command on the group interface, rather than entering this command on each interface. You can customize the configuration on a specific interface by using the member command.
Examples
The following example defines interfaces 2, 3, 4, 5, 6, and 7 as members of asynchronous group interface 0:
Related Commands
interface group-async Creates a group interface that will serve as master, to which asynchronous interfaces can be associated as members. Alters the configuration of an asynchronous interface that is a member of a group. To specify the IP address that will be tunneled to, use the initiate-to command in VPDN group configuration mode. To remove an IP address from the VPDN group, use the no form of the command.
Syntax Description
ip ip-address The IP address of the router that will be tunneled to. limit limit-number (Optional) The maximum number of connections that can be made to this IP address. priority priority-number (Optional) The priority for this IP address (1 is the highest).
Defaults
Disabled
Command Modes
VPDN group configuration
Command History
12.0(5)T This command was introduced.
Usage Guidelines
Before you can use this command, you must enable one of the two request VPDN subgroups by using either the request dialin or request dialout command. A LAC configured to request dial-in can be configured with multiple initiate-to commands to tunnel to more than one IP address. An LNS configured to request dialout can only be configured with a single initiate-to command. If you enter a second initiate-to command, it will replace the original initiate-to command.
Examples
The following example configures VPDN group 1 to request an L2TP tunnel to the peer at IP address 10.3.2.1 for tunneling dialout calls from dialer pool 1. This group can tunnel a maximum of five simultaneous users and it has the second highest priority for requesting dialout calls.
Related Commands
request dialin Configures a VPDN group to request L2F or L2TP tunnels to a home gateway and creates a request-dialin VPDN subgroup. Enables an LNS to request VPDN dial-out calls by using L2TP. To define the IP addresses of the server, use the interface command in interface configuration mode. To disable this function, use the no form of this command.
Syntax Description
name-tag The logic name to identify the server configuration so that multiple entries of server configuration can be entered.
Defaults
Disabled
Command Modes
Interface configuration
Command History
11.3(7) This command was introduced.
Usage Guidelines
Each server can have multiple entries of IP addresses or aliases.
Related Commands
clear rlm group Clears all RLM group time stamps to zero. clear interface Resets the hardware logic on an interface. link (RLM) Specifies the link preference. protocol rlm port Reconfigures the port number for the basic RLM connection for the whole rlm-group. retry keepalive Allows consecutive keepalive failures a certain amount of time before the link is declared down. server (RLM) Defines the IP addresses of the server. show rlm group statistics Displays the network latency of the RLM group. show rlm group status Displays the status of the RLM group. show rlm group timer Displays the current RLM group timer values. shutdown (RLM) Shuts down all of the links under the RLM group. timer Overwrites the default setting of timeout values. To configure a BRI interface and enter interface configuration mode, use the interface bri command in global configuration mode. Cisco 7200 series and 7500 series routers Cisco 7200 series and 7500 series routers with subinterfaces
Syntax Description
Defaults
The default mode for subinterfaces is multipoint.
Command Modes
Command History
10.3 This command was introduced. 11.2F The capability to carry X.25 traffic on the D channel was added. 11.2P This command was modified to include slot/port syntax for the PA-8B-ST and PA-4B-U port adapters on Cisco 7200 series routers.
Usage Guidelines
Subinterfaces can be configured to support partially meshed Frame Relay networks. (Refer to the Frame Relay chapters in the Cisco IOS Wide-Area Networking Configuration Guide.)
Examples
The following example configures BRI 0 to call and receive calls from two sites, use Point-to-Point Protocol (PPP) encapsulation on outgoing calls, and use Challenge Handshake Authentication Protocol (CHAP) authentication on incoming calls:
Related Commands
Configures a serial interface or ISDN interface to call one or multiple sites or to receive calls from multiple sites. Controls access by configuring an interface to belong to a specific dialing group. encapsulation Sets the encapsulation method used by the interface. Defines the SPID number that has been assigned by the ISDN service provider for the B1 channel. Sets PPP BACP call parameters. Displays information about the BRI D channel or about one or more To define a dialer rotary group, use the interface dialer command in global configuration mode.
Syntax Description
number Number of the dialer rotary group. It can be number in the range 0 through 255.
Defaults
No dialer rotary groups are predefined.
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Usage Guidelines
Dialer rotary groups allow you to apply a single interface configuration to a set of physical interfaces. This allows a group of interfaces to be used as a pool of interfaces for calling many destinations. Once the interface configuration is propagated to a set of interfaces, those interfaces can be used to place calls using the standard DDR criteria. When multiple destinations are configured, any of these interfaces can be used for outgoing calls. Dialer rotary groups are useful in environments that require multiple calling destinations. Only the rotary group needs to be configured with the dialer map commands. The only configuration required for the interfaces is the dialer rotary-group command indicating that each interface is part of a dialer rotary group. Although a dialer rotary group is configured as an interface, it is not a physical interface. Instead, it represents a group of interfaces. Interface configuration commands entered after the interface dialer command will be applied to all physical interfaces assigned to specified rotary groups. Individual interfaces in a dialer rotary group do not have individual addresses. The dialer interface has a protocol address, and that address is used by all interfaces in the dialer rotary group.
Examples
The following example identifies interface dialer 1 as the dialer rotary group leader. Interface dialer 1 is not a physical interface, but represents a group of interfaces. The interface configuration commands that follow apply to all interfaces included in this group. To create a multilink bundle or enter multilink interface configuration mode, use the interface multilink command in global configuration mode. Use the no form of this command to remove a multilink bundle.
Syntax Description
group-number Number of the multilink bundle (a nonzero number).
Defaults
No interfaces are configured.
Command Modes
Global configuration
Command History
12.0(3)T This command was introduced.
Examples
The following example creates multilink bundle 1:
Related Commands
multilink-group Designates an interface as part of a multilink leased line bundle. ppp multilink fragmentation Enables or disables MLP fragmentation. Disabling allows multilink packets to be forwarded across platforms. To specify a serial interface created on a channelized E1 or channelized T1 controller (for ISDN PRI, channel-associated signalling, or robbed-bit signalling), use the interface serial command in global configuration mode. Cisco 7200 series and Cisco 7500 series routers Cisco AS5200 series and Cisco 4000 series access servers
Syntax Description
slot/port Slot number and port number where the channelized E1 or T1 controller is located. number timeslot For ISDN, the D channel time slot, which is :23 channel for channelized T1 and the :15 for channelized E1. PRI time slots are in the range 0 to 23 for channelized T1 and in the range 0 to 30 for channelized E1. For channel-associated signalling or robbed-bit signalling, the channel group number. The colon (:) is required. On a dual port card, it is possible to run channelized on one port and primary rate on the other port.
Defaults
You must explicitly specify a serial interface.
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Usage Guidelines
The D channel is always the :23 channel for T1 and the :15 for E1.
Examples
The following example configures channel groups on time slots 1 to 11 and ISDN PRI on time slots 12 to 24 of T1 controller 0. Then the examples configures the first two channel groups as serial interfaces 0:0 and 0:1. The following example configures ISDN PRI on T1 controller 4/1 and then configures the D channel on the resulting serial interface 4/1:23:
Related Commands
Configures a T1 or E1 controller and enters controller configuration mode. Displays the total number of calls and call durations on a T1 controller. show interfaces Displays statistics for all interfaces configured on the router or access server. To create a virtual template interface that can be configured and applied dynamically in creating virtual access interfaces, use the interface virtual-template command in global configuration mode.
Syntax Description
number Number used to identify the virtual template interface.
Defaults
Disabled. No virtual template number is defined.
Command Modes
Global configuration
Command History
11.2F This command was introduced.
Usage Guidelines
A virtual template interface is used to provide the configuration for dynamically created virtual access interfaces. It is created by users and can be saved in nonvolatile RAM (NVRAM). Once the virtual template interface is created, it can be configured in the same way as a serial interface. Virtual template interfaces can be created and applied by various applications such as Virtual Profiles, virtual private dialup networks (VPDN), PPP over ATM, protocol translation, and Multichassis Multilink PPP (MMP).
Examples
The following example creates and configures virtual template interface 1:
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
11.3 This command was introduced.
Usage Guidelines
Use the ip address negotiated interface command to enable a Cisco router to automatically negotiate its own registered WAN interface IP address from a central server (via PPP/IPCP) and to enable all remote hosts to access the global Internet using this single registered IP address.
Examples
The following example configures an asynchronous interface (interface async1) to obtain its IP address via PPP/IPCP address negotiation:
Related Commands
encapsulation Sets the encapsulation method used by the interface. ip address Sets a primary or secondary IP address for an interface. ip unnumbered Enables IP processing on an interface without assigning an explicit IP address to the interface. To enable an address pooling mechanism used to supply IP addresses to dialin asynchronous, synchronous, or ISDN point-to-point interfaces, use the ip address-pool command in global configuration mode. Use the no form of the command to disable IP address pooling globally on all interfaces with the default configuration.
Syntax Description
dhcp-proxy-client (Optional) Uses the router as the proxy-client between a third-party Dynamic Host Configuration Protocol (DHCP) server and peers connecting to the router. local (Optional) Uses the local address pool named default.
Defaults
IP address pooling is disabled.
Command Modes
Global configuration
Command History
11.0 This command was introduced.
Usage Guidelines
The global default mechanism applies to all interfaces that have been left in the default setting of the peer default ip address pool command. If any peer default ip address command other than peer default ip address pool (the default) is configured, then the interface uses that mechanism and not the global default mechanism. Thus all interfaces can be independently configured or left unconfigured so that the global default mechanism setting apply. This flexibility minimizes the configuration effort on the part of the administrator.
Examples
The following example specifies the DHCP proxy client mechanism as the global default mechanism for assigning peer IP addresses: The following example specifies a local IP address pool called default as the global default mechanism for all interfaces that have been left in their default setting:
Related Commands
encapsulation Sets the encapsulation method used by the interface. exec Allows an EXEC process on a line. Specifies which DHCP servers to use on a network, and specifies the IP address of one or more DHCP servers available on the network. Configures a local pool of IP addresses to be used when a remote peer connects to a point-to-point interface. 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. Starts an asynchronous connection using PPP. Displays the current DHCP settings on point-to-point interfaces. Displays statistics for any defined IP address pools. Starts a serial connection to a remote host using SLIP. To assign an IP address to the service provided on a TCP port, use the ip alias command in interface configuration mode. Use the no form of this command to remove the specified address for the router.
Syntax Description
ip-address Specifies the IP address for the service. tcp-port Specifies the number of the TCP port.
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Usage Guidelines
A user attempting to establish a connection is connected to the first free line in a rotary group using the Telnet protocol. The IP address must be on the same network or subnet as the router's main address, and must not be used by another host on that network or subnet. Connecting to the IP address has the same effect as connecting to the router's main address, using tcp-port as the TCP port. You can use the ip alias command to assign multiple IP addresses to the router. For example, in addition to the primary alias address, you can specify addresses that correspond to lines or rotary groups. Using the ip alias command in this way makes the process of connecting to a specific rotary group transparent to the user. When asynchronous mode is implemented, the Cisco IOS software creates the appropriate IP aliases, which map the asynchronous addresses for the lines to which they are connect. This process is automatic and does not require configuration.
Examples
The following example configures connections to IP address 172.30.42.42 to act identically to connections made to the server's primary IP address on TCP port 3001. In other words, a user is connected to the first free line on port 1 of the rotary group that uses the Telnet protocol. To specify which Dynamic Host Configuration Protocol (DHCP) servers to use on your network, or to specify the IP address of one or more DHCP servers available on the network, use the ip dhcp-server command in global configuration mode. Use the no form of the command to remove a DHCP server's IP address.
Syntax Description
ip-address (Optional) IP address of a DHCP server. name (Optional) Name of a DHCP server.
Defaults
The IP limited broadcast address of 255.255.255.255 is used for transactions if no DHCP server is specified. This allows automatic detection of DHCP servers.
Command Modes
Global configuration
Command History
11.0 This command was introduced.
Usage Guidelines
A DHCP server temporarily allocates network addresses to clients through the access server on an as-needed basis. While the client is active, the address is automatically renewed in a minimum of 20-minute increments. When the user terminates the session, the interface connection is terminated so that network resources can be quickly reused. You can specify up to ten servers on the network. In normal situations, if a user's SLIP/PPP session fails (for example if a modem line disconnects), the allocated address will be reserved temporarily to preserve the same IP address for the client when dialed back into the server. This way, the session that was accidentally terminated can often be resumed. To use the DHCP proxy-client feature, enable your access server to be a proxy-client on asynchronous interfaces by using the ip address-pool dhcp-proxy-client command. If you wish to specify which DHCP servers are used on your network, use the ip dhcp-server command to define up to ten specific DHCP servers.
framing {crc4 | no-crc4} [australia]
Release
Modification
framing esf
Command
Description
group-range
no group-range interface
Release
Modification
interface group-async 0
group range 2 7
Command
Description
initiate-to
no initiate-to [ip ip-address]
Release
Modification
vpdn-group 1
request dialout
protocol l2tp
pool-member 1
imitate-to ip 10.3.2.1 limit 5 priority 2
Command
Description
interface
no interface name-tag
Release
Modification
Command
Description
interface bri
interface bri number
interface bri slot/port
interface bri number.subinterface-number [multipoint | point-to-point]
interface bri slot/port.subinterface-number [multipoint | point-to-point]
interface bri number:0
interface bri slot/port:0
Release
Modification
interface bri 0
encapsulation ppp
no keepalive
dialer map ip 131.108.36.10 name EB1 234
dialer map ip 131.108 36.9 name EB2 456
dialer-group 1
isdn spid1 41346334600101 4633460
isdn spid2 41346334610101 4633461
isdn T200 1000
ppp authentication chap
interface bri0
isdn x25 dchannel
isdn x25 static-tei 8
!
interface bri0:0
ip address 10.1.1.2 255.255.255.0
x25 address 31107000000100
x25 htc 1
x25 suppress-calling-address
x25 facility windowsize 2 2
x25 facility packetsize 256 256
x25 facility throughput 9600 9600
x25 map ip 10.1.1.3 31107000000200
Command
Description
B channels.
interface dialer
Release
Modification
interface dialer 1
encapsulation ppp
authentication chap
dialer in-band
ip address 1.2.3.4
dialer map ip 1.2.2.5 name
YYY 14155553434
dialer map ip 1.3.2.6 name ZZZ
interface multilink
no interface multilink
Release
Modification
interface multilink 1
ip address 192.168.11.4 255.255.255.192
encapsulation ppp
ppp multilink
keepalive
Command
Description
interface serial
interface serial slot/port:timeslot
interface serial number:timeslot
Release
Modification
controller t1 0
channel-group 0 timeslot 1-6
channel-group 1 timeslot 7
channel-group 2 timeslot 8
channel-group 3 timeslot 9-11
pri-group timeslots 12-24
!
interface serial 0:0
ip address 131.108.13.2 255.255.255.0
encapsulation ppp
!
interface serial 0:1
ip address 131.108.13.3 255.255.255.0
encapsulation ppp
controller t1 4/1
framing crc4
linecode hdb3
pri-group timeslots 1-24
interface serial 4/1:23
ip address 131.108.13.1 255.255.255.0
encapsulation ppp
Command
Description
interface virtual-template
Release
Modification
interface virtual-template 1
ip unnumbered ethernet 0
ppp multilink
ppp authentication chap
ip address negotiated
ip address negotiated
no ip address negotiated
Release
Modification
interface async1
ip address negotiated
encapsulation ppp
Command
Description
ip address-pool
no ip address-pool
Release
Modification
ip address-pool dhcp-proxy-client
ip address-pool local
Command
Description
ip alias
no ip alias ip-address
Release
Modification
ip alias
172.30.42.42 3001
ip dhcp-server
no ip dhcp-server [ip-address | name]
Release
Modification
![]() |
Note To facilitate transmission, configure intermediary routers (or access servers with router functionality) to use an IP helper address whenever the DHCP server is not on the local LAN and the access server is using broadcasts to interact with the DHCP server. See the chapters about configuring IP addressing in the Cisco IOS IP and IP Routing Configuration Guide. |
The ip address-pool dhcp-proxy-client command initializes proxy-client status to all interfaces defined as asynchronous on the access server. To selectively disable proxy-client status on a single asynchronous interface, use the no peer default ip address interface command.
Examples
The following command specifies a DHCP server with the IP address of 129.12.13.81:
ip dhcp-server 129.12.13.81
Related Commands
Enables an address pooling mechanism used to supply IP addresses to dial-in asynchronous, synchronous, or ISDN point-to-point interfaces. ip helper-address Forwards UDP broadcasts, including BOOTP, received on an interface. 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. Displays the current DHCP settings on point-to-point interfaces.
Command
Description
To configure a local pool of IP addresses to be used when a remote peer connects to a point-to-point interface, use the ip local pool command in global configuration mode. Use the no form of this command to remove a range of addresses from a pool (longer form of the no command), or to delete an address pool (shorter form of the no command).
ip local pool {default | pool-name low-ip-address [high-ip-address]}
Syntax Description
default Defaults local address pool that is used if no other pool is named. pool-name Name of a specific local address pool. low-ip-address Lowest IP address in the pool. high-ip-address (Optional) Highest IP address in the pool. If this value is omitted only the low-ip-address IP address is included in the local pool.
Defaults
No address pools are configured.
Command Modes
Global configuration
Command History
11.0 This command was introduced. 11.3AA This command was enhanced to allow address ranges to be added and removed. 12.0 This command was migrated to Release 12.0.
Release
Modification
Usage Guidelines
Use the ip local pool command to create one or more local address pools from which IP addresses are assigned when a peer connects, and to add another range of addresses to an existing pool. The default address pool is then used on all point-to-point interfaces after the ip address-pool local global configuration command is issued. To use a specific, named address pool on an interface, use the peer default ip address pool interface configuration command.
These pools can also be used with the translate commands for one-step vty-async connections and in certain AAA/TACACS+ authorization functions. Refer to the chapter "Configuring Protocol Translation and Virtual Asynchronous Devices" in the Cisco IOS Dial Services Configuration Guide: Terminal Services and the "System Management" part of the Cisco IOS Configuration Fundamentals Configuration Guide for more information. Pools can be displayed with the show ip local pool command.
Examples
The following command creates a local IP address pool named quark, which contains all local IP addresses from 172.16.23.0 to 172.16.23.255:
ip local pool quark 172.16.23.0 172.16.23.255
The following example configures a pool of 1024 IP addresses:
#no ip local pool default #ip local pool default 1.1.1.0 1.1.4.255 #^Z show ip local pool Pool Begin End Free InUse default 1.1.1.0 1.1.4.255 1024 0
The following example configures multiple ranges of IP addresses into one pool:
no ip local pool default ip local pool default 9.1.1.0 9.1.9.255 ip local pool default 9.2.1.0 9.2.9.255 ^Z
show ip local pool Pool Begin End Free In use Cache Size default 9.1.1.0 9.1.9.255 2304 0 20 9.2.1.0 9.2.9.255 2304 0
Related Commands
Enables an address pooling mechanism used to supply IP addresses to dial-in asynchronous, synchronous, or ISDN point-to-point interfaces. Displays statistics for any defined IP address pools. 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.
Command
Description
To establish static routes and define the next hop for large-scale dialout, use the ip route command in global configuration mode. To remove static routes, use the no ip route command.
ip route network-number network-mask {IP address | interface} [distance] [name name]
Syntax Description
network-number IP address of the target network or subnet. network-mask Network mask that lets you mask network and subnetwork bits. IP address Internet address of the next hop that can be used to reach that network in standard IP address notation. Example: 1.1.1.1. interface Network interface to use. distance (Optional) An administrative distance, which is a rating of the trustworthiness of a routing information source, such as an individual router or a group of routers. name name (Optional) Name of the user profile.
Defaults
No static route is established.
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
A static route is appropriate when the communication server cannot dynamically build a route to the destination.
If you specify an administrative distance, you are flagging a static route that can be overridden by dynamic information. For example, IGRP-derived routes have a default administrative distance of 100. To have a static route that would be overridden by an IGRP dynamic route, specify an administrative distance greater than 100. Static routes have a default administrative distance of 1.
Static routes that point to an interface will be advertised using RIP, IGRP, and other dynamic routing protocols, regardless of whether redistribute static commands were specified for those routing protocols. These static routes will be advertised because static routes that point to an interface are considered to be connected in the routing table and hence lose their static nature. However, if you define a static route to an interface that is not in one of the networks defined in a network command, no dynamic routing protocols will advertise the route unless a redistribute static command is specified for these protocols.
The user profile name is passed to an AAA server as the next hop for large scale dialout, and is the name argument with the -out suffix appended. The suffix is automatically supplied and is required since dial in and user profile names must be unique.
Examples
In the following example, an administrative distance of 110 was chosen. In this case, packets for network 10.0.0.0 will be routed via to the communication server at 172.19.3.4 if dynamic information with administrative distance less than 110 is not available:
ip route 10.0.0.0 255.0.0.0 172.19.3.4 110
In the following example, packets for network 172.19.0.0 will be routed to the communication server at 172.19.6.6:
ip route 172.19.0.0 255.255.0.0 172.19.6.6
In the following example, the user profile named macarthur-out will be retrieved from the AAA:
ip route 10.0.0.0 255.255.255.255 Dialer0 name macarthur
Related Commands
Displays all static IP routes, or those installed using the AAA route download function.
Command
Description
To reserve a special queue for a set of Real-time Transport Protocol (RTP) packet flows belonging to a range of User Datagram Protocol (UDP) destination ports, use the ip rtp reserve command in interface configuration mode. Use the no form of the command to disable the special queue for real-time traffic.
ip rtp reserve lowest-udp-port range-of-ports [maximum-bandwidth]
Syntax Description
lowest-udp-port Lowest UDP port number to which the packets are sent. range-of-ports Number, which added to the lowest-UDP-port value, yields the highest UDP port value. maximum-bandwidth (Optional) Bandwidth, in kilobits per second, reserved for the RTP packets to be sent to the specified UDP ports.
Defaults
This function is disabled by default. No default values are provided for the arguments.
Command Modes
Interface configuration
Command History
11.3 This command was introduced.
Release
Modification
Usage Guidelines
If the bandwidth needed for RTP packet flows exceeds the maximum bandwidth specified, the reserved queue will degrade to a best-effort queue.
This command helps in improving the delay bounds of voice streams by giving them a higher priority.
Examples
The following example reserves a unique queue for traffic to destination UDP ports in the range 32768 to 32788 and reserves 1000 kbps bandwidth for that traffic:
ip rtp reserve 32768 20 1000
Related Commands
Enables MLP on an interface and, optionally, enables dynamic bandwidth allocation. Configures a maximum delay allowed for transmission of a packet fragment on a MLP bundle. Enables interleaving of RTP packets among the fragments of larger packets on a MLP bundle.
Command
Description
To enable asynchronous listening, which in turn allows TCP connections to TCP port 57, use the ip tcp async-mobility server command in global configuration mode. Use the no form of this command to turn listening off.
ip tcp async-mobility serverSyntax Description
This command has no arguments or keywords.
Defaults
Disabled. Asynchronous listening is turned off.
Command Modes
Global configuration
Command History
11.2 This command was introduced.
Release
Modification
Usage Guidelines
After asynchronous listening is turned on by the ip tcp async-mobility server command, use the tunnel command to establish a network layer connection to a remote host. Both commands must be used to enable asynchronous mobility.
Examples
The following example shows how to configure asynchronous mobility. The tunnel command is used to establish a network layer connection with an IBM host called mktg.
configure terminal Enter configuration commands, one per line. End with CNTL/Z. ip tcp async-mobility server exit %SYS-5-CONFIG_I: Configured from console by console tunnel ? WORD Address or hostname of a remote system tunnel mktg
Related Commands
Sets up a network layer connection to a router.
Command
Description
To suppress the display of Telnet connection messages, use the ip telnet quiet command in global configuration mode. To cancel this option, use the no form of this command.
ip telnet quietSyntax Description
This command has no arguments or keywords.
Defaults
Telnet connection message suppression is disabled by default.
Command Modes
Global configuration
Command History
12.1 This command was introduced.
Release
Modification
Usage Guidelines
The ip telnet quiet command does not suppress TCP or error messages. It is most useful to Internet service providers, to allow them to hide the onscreen messages displayed during connection, including Internet addresses, from subscription users.
Examples
The following example globally disables onscreen connect messages:
ip telnet quiet
The following example shows the login and logout messages displayed during login and logout when the ip telnet quiet command has not been configured to suppress Cisco IOS software messages:
Router# telnet Server3
Translating "Server3"...domain server (171.68.89.42) [OK]
Trying Server3--Server3.cisco.com (171.68.89.42)... Open
Kerberos: No default realm defined for Kerberos!
login:User2
Password:
Welcome to OpenVMS VAX version V6.1 on node CRAW
Last interactive login on Tuesday, 15-DEC-1998 11:01
Last non-interactive login on Sunday, 3-JAN-1999 22:32
Server3)logout
User2 logged out at 16-FEB-2000 09:38:27.85
[Connection to Server3 closed by foreign host]
Router#
The following example shows the limited messages displayed during login and logout when the ip telnet quiet command has been configured to suppress Cisco IOS software messages:
Router# telnet Server3
login:User2
Password:
Welcome to OpenVMS VAX version V6.1 on node CRAW
Last interactive login on Tuesday, 15-DEC-1998 11:01
Last non-interactive login on Sunday, 3-JAN-1999 22:32
Server3)logout
User2 logged out at 16-FEB-2000 09:38:27.85
Router#
Related Commands
busy-message Creates a "host-failed" message that displays when a connection fails. rlogin Logs in to a UNIX host using rlogin. service hide-telnet-address Hides addresses while trying to establish a Telnet session. Logs in to a host that supports Telnet.
Command
Description
To enable compression of Internetwork Packet Exchange (IPX) packet headers in a PPP session, use the ipx compression cipx command in interface configuration mode. Use the no form of this command to disable compression of IPX packet headers in a PPP session.
ipx compression cipx number-of-slots
Syntax Description
number-of-slots Number of stored IPX headers allowed. The range is from 10 to 256. The default is 16. A slot is similar to a table entry for a complete IPX header. When a packet is received, the receiver stores the complete IPX header in a slot and tells the destination which slot it used. As subsequent CIPX packets are sent, the receiver uses the slot number field to determine which complete IPX header to associate with the CIPX packet before passing the packet up to IPX.
Defaults
No compression of IPX packets during a PPP session.
Command Modes
Interface configuration
Command History
11.1 This command was introduced.
Release
Modification
Usage Guidelines
This interface configuration command enables IPX header compression on PPP links.
Examples
The following example enables IPX header compression for PPP:
encapsulation ppp ipx compression cipx 128
Related Commands
show ipx compression Displays the current status and statistics of IPX header compression during PPP sessions.
Command
Description
To enable a nonrouting Internetwork Packet Exchange (IPX) client to connect to an asynchronous interface, the interface must be associated with a loopback interface configured to run IPX. To permit such connections, use the ipx ppp-client command in interface configuration mode. Use the no form of this command to disable a nonrouting IPX client.
ipx ppp-client loopback number
Syntax Description
loopback Loopback interface configured with a unique IPX network number. number Number of the loopback interface.
Defaults
IPX client connections are not permitted over PPP.
Command Modes
Interface configuration
Command History
11.1 This command was introduced.
Release
Modification
Usage Guidelines
This command enables IPX clients to log in to 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.
You must first configure a loopback interface with a unique IPX network number. The loopback interface is then assigned to an asynchronous interface, which permits IPX clients to connect to the asynchronous interface.
Examples
The following example configures IPX to run over PPP on asynchronous interface 3:
ipx routing 0000.0c07.b509 interface loopback0 no ip address ipx network 544 ipx sap-interval 2000 interface ethernet0 ip address 172.21.14.64 ipx network AC150E00 ipx encapsulation SAP interface async 3 ip unnumbered ethernet0 encapsulation ppp async mode interactive async default ip address 172.18.1.128 ipx ppp-client loopback0 ipx sap-interval 0
Related Commands
interface loopback Creates a loopback interface. ipx network Enables IPX routing on a particular interface and optionally selects the type of encapsulation (framing).
Command
Description
To enable NetWare Asynchronous Services Interface (NASI) clients to connect to asynchronous devices attached to your router, use the ipx nasi-server enable command in global configuration mode. Use the no form of this command to prevent NASI clients from connecting through a router.
ipx nasi-server enableSyntax Description
This command has no arguments or keywords.
Defaults
NASI is not enabled.
Command Modes
Global configuration
Command History
11.1 This command was introduced.
Release
Modification
Usage Guidelines
When you issue this command, NASI clients can connect to any port on the router other than the console port to access network resources. When the user on the NASI client uses the Windows or DOS application to connect to the router, a list of available tty and vty lines appears, beginning with tty1. The user selects the desired outgoing tty or vty port.
You can configure TACACS+ security on the router so that after the user selects a tty or vty port, a username and password prompt appear for authentication, authorization, and accounting purposes.
Examples
The following example shows a minimum configuration to enable NASI client dial-in access with TACACS+ authentication:
ipx routing ipx internal-network ncs001 interface ethernet 0 ipx network 1 ipx nasi-server enable ! enable TACACS+ authentication for NASI clients using the list name swami aaa authentication nasi swami tacacs+ line 1 8 modem inout
Related Commands
aaa authentication nasi Specifies AAA authentication for NASI clients connecting through the access server. nasi authentication Enables AAA authentication for NASI clients connecting to a router. show ipx nasi connections Displays the status of NASI connections show ipx spx-protocol Displays the status of the SPX protocol stack and related counters.
Command
Description
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon May 8 13:15:29 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.